-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.6
-
None
-
No
-
Low
-
rhel-sst-virtualization
-
ssg_virtualization
-
None
-
False
-
-
None
-
None
-
None
-
None
-
-
x86_64
-
None
Description of problem：
Some driver installation info is incorrect in firstboot log after v2v converting windows guests
Version-Release number of selected component (if applicable):
virt-v2v-2.6.0-1.el9.x86_64
libguestfs-1.54.0-1.el9.x86_64
guestfs-tools-1.52.2-1.el9.x86_64
nbdkit-1.38.5-1.el9.x86_64
libnbd-1.20.3-1.el9.x86_64
virtio-win-1.9.43-0.el9_5.noarch
libguestfs-winsupport-9.3-1.el9_3.x86_64
qemu-img-9.1.0-1.el9.x86_64
libvirt-libs-10.8.0-2.el9.x86_64
How reproducible:
100%
Steps:
1. Convert a windows guest from VMware to local libvirt by virt-v2v
# virt-v2v -ic vpx://non-admin%40vsphere.local@10.73.212.129/data/10.73.212.36/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.3 -io vddk-thumbprint=CB:9F:B1:9D:33:49:6C:60:AD:3C:A5:16:77:91:5F:CD:1B:24:B1:43 -ip /home/passwd esx8.0-win2016-x86_64-efi --mac 00:50:56:af:ed:b1:ip:10.184.112.42,10.184.112.1,24,10.10.10.53,10.10.10.54 --mac 00:50:56:af:ed:b1:network:default [ 0.0] Setting up the source: -i libvirt -ic vpx://non-admin%40vsphere.local@10.73.212.129/data/10.73.212.36/?no_verify=1 -it vddk esx8.0-win2016-x86_64-efi [ 10.3] Opening the source [ 21.3] Inspecting the source [ 39.5] Checking for sufficient free disk space in the guest [ 39.5] Converting Windows Server 2016 Standard (win2k16) to run on KVM virt-v2v: This guest has virtio drivers installed. [ 58.0] Setting a random seed virt-v2v: warning: random seed could not be set for this type of guest [ 58.0] SELinux relabelling [ 58.2] Mapping filesystem data to avoid copying unused and blank areas [ 62.1] Closing the overlay [ 62.4] Assigning disks to buses [ 62.4] Checking if the guest needs BIOS or UEFI to boot virt-v2v: This guest requires UEFI on the target to boot. [ 62.4] Setting up the destination: -o libvirt [ 76.0] Copying disk 1/9 █ 100% [****************************************] [ 860.2] Copying disk 2/9 █ 100% [****************************************] [ 862.8] Copying disk 3/9 █ 100% [****************************************] [ 936.3] Copying disk 4/9 █ 100% [****************************************] [ 937.9] Copying disk 5/9 █ 100% [****************************************] [ 939.5] Copying disk 6/9 █ 100% [****************************************] [ 940.4] Copying disk 7/9 █ 100% [****************************************] [1083.2] Copying disk 8/9 █ 100% [****************************************] [1084.6] Copying disk 9/9 █ 100% [****************************************] [1086.3] Creating output metadata [1086.3] Finishing off
2.Check the guest after v2v conversion, found some driver installation info is incorrect in firstboot log, for example, firstboot log shows that fail to install netkvm(network driver), pvpanic(QEMU PVPanic), vioser(virtio serial), viostor(virtio storage), but these drivers have successfully installed for the devices, details please refer to screenshots 'driver-info-of-firstboot-log-and-device-manager-screenshots'
Actual results:
As above description
Expected result:
Driver installation info shows correct in firstboot log after v2v converting windows guests
Additional info:
This bug isn't a regression issue because I have also encounter the bug on rhel9.5
