-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.5
-
None
-
rhel-sst-virtualization
-
ssg_virtualization
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
Virt-v2v tries to use osinfo-db data provided by virtio-win to install the right drivers.
This information is found in:
./os/microsoft.com/win-7.d/virtio-win-pre-installable-drivers-win-7.xml ./os/microsoft.com/win-8.1.d/virtio-win-pre-installable-drivers-win-8.1.xml ./os/microsoft.com/win-8.d/virtio-win-pre-installable-drivers-win-8.xml ./os/microsoft.com/win-10.d/virtio-win-pre-installable-drivers-win-10.xml ./os/microsoft.com/win-11.d/virtio-win-pre-installable-drivers-win-11.xml
Virt-v2v uses the osinfo "short ID" to do this matching:
$ osinfo-query os | grep win ... win10 | Microsoft Windows 10 | 10.0 | http://microsoft.com/win/10 win11 | Microsoft Windows 11 | 11.0 | http://microsoft.com/win/11 win2k16 | Microsoft Windows Server 2016 | 10.0 | http://microsoft.com/win/2k16 win2k19 | Microsoft Windows Server 2019 | 10.0 | http://microsoft.com/win/2k19 win2k22 | Microsoft Windows Server 2022 | 10.0 | http://microsoft.com/win/2k22 ... etc ...
When virt-v2v can't find the osinfo for a matching operating system, like win2k22, it falls back to heuristic detection of drivers. The heuristic detection is somewhat error-prone.
I believe there's a problem that virtio-win osinfo data doesn't provide short ID references for server versions of Windows:
$ find -name '*virtio*' | xargs grep win2k22 (no output)
This RFE is to work out how to provide this information (which I will investigate further).
