-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.5
-
None
-
No
-
Low
-
rhel-sst-virtualization
-
ssg_virtualization
-
None
-
False
-
-
None
-
None
-
None
-
None
-
-
x86_64
-
None
Description of problem:
VMware VMCI Host device can't be uninstalled in win2022-non-uefi and win10 non-uefi x64 guests after v2v conversion
Version-Release number of selected component (if applicable):
virt-v2v-2.5.6-7.el9_5.x86_64
libguestfs-1.50.2-1.el9.x86_64
guestfs-tools-1.51.6-5.el9.x86_64
nbdkit-1.38.3-1.el9.x86_64
libnbd-1.20.2-2.el9.x86_64
libvirt-libs-10.5.0-7.el9_5.x86_64
qemu-img-9.0.0-10.el9_5.x86_64
virtio-win-1.9.43-0.el9_5.noarch
How reproducible:
100%
Steps:
1.Found VMware VMCI Host device exists in win2016-non-efi, win2019-non-uefi and win2022-non-uefi guest on VMware
2. Convert win2016-non-efi, win2019-non-uefi and win2022-non-uefi guest from VMware to local libvirt by v2v
3. Found VMware VMCI Host device can be uninstalled in win2016-non-efi and win2019-non-uefi guests after conversion, but VMware VMCI Host device can't be uninstalled in win2022-non-uefi guest after conversion, details pls refer to screenshots and v2v debug log
Actual results:
As above description
Expected result:
VMware VMCI Host device can be uninstalled in win2022-non-uefi guest after v2v conversion
Additional info: