-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-10.1
-
None
-
Yes
-
None
-
rhel-virt-core-libvirt-2
-
None
-
False
-
False
-
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
None
Description of problem：
There is unexpected pci warning during v2v conversion
Version-Release number of selected component (if applicable):
virt-v2v-2.8.1-9.el10.x86_64
libguestfs-1.56.1-3.el10.x86_64
guestfs-tools-1.54.0-3.el10.x86_64
selinux-policy-42.1.6-1.el10.noarch
osinfo-db-20250606-1.el10.noarch
How reproducible:
100%
Steps:
1. Convert a guest from VMware by 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/vddk9.0.0 -io vddk-thumbprint=0D:86:09:22:3A:D5:2D:2E:54:E6:08:EC:C5:F0:25:7F:44:C2:87:E7 -ip /home/passwd Auto-esx8.0-win2025-with-multiple-nets-static-ips -on Auto-esx8.0-win2025-with-multiple-nets-static-ips-virt-v2v-2.7.1-15-set-static --mac 00:50:56:a0:c0:f2:ip:10.184.112.42,10.184.112.1,24,10.10.10.53,10.10.10.54 --mac 00:50:56:a0:22:ca:ip:192.168.0.10,,,8.8.8.8 --mac 00:50:56:a0:ac:b0:ip:192.168.0.1,192.168.1.1,22,8.8.9.9,9.9.8.8 -o null [ 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 Auto-esx8.0-win2025-with-multiple-nets-static-ips [ 1.7] Opening the source [ 42.3] Checking filesystem integrity before conversion [ 43.5] Detecting if this guest uses BIOS or UEFI to boot [ 44.0] Inspecting the source [ 51.0] Detecting the boot device [ 51.0] Checking for sufficient free disk space in the guest [ 51.0] Converting Windows Server 2025 Standard (win2k25) to run on KVM ** (process:781050): WARNING **: 23:57:57.891: Entity http://pcisig.com/pci/1af4/1012 referenced but not defined virt-v2v: This guest has virtio drivers installed. [ 87.8] Setting a random seed virt-v2v: warning: random seed could not be set for this type of guest [ 87.8] SELinux relabelling [ 88.0] Mapping filesystem data to avoid copying unused and blank areas [ 90.6] Checking filesystem integrity after conversion [ 91.7] Closing the overlay [ 92.0] Assigning disks to buses [ 92.0] Checking if the guest needs BIOS or UEFI to boot [ 92.0] Setting up the destination: -o null [ 93.1] Copying disk 1/4 █ 100% [****************************************] [ 391.9] Copying disk 2/4 █ 100% [****************************************] [ 392.7] Copying disk 3/4 █ 100% [****************************************] [ 393.7] Copying disk 4/4 █ 100% [****************************************] [ 394.8] Creating output metadata [ 394.8] Finishing off
Actual result:
As above description
Expect result:
Fix the bug
Additional info
Similar bug fixed on rhel9 https://issues.redhat.com/browse/RHEL-38636
