-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
rhel-10.2
-
None
-
None
-
None
-
rhel-virt-tools
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
None
Description of problem：
New options smp and memsize don't work during v2v conversion
Version-Release number of selected component (if applicable):
virt-v2v-2.9.9-1.el10.x86_64
libguestfs-1.57.5-1.el10.x86_64
guestfs-tools-1.54.0-6.el10.x86_64
nbdkit-1.45.7-1.el10.x86_64
libnbd-1.23.7-1.el10.x86_64
libvirt-11.8.0-1.el10.x86_64
qemu-kvm-10.1.0-2.el10.x86_64
How reproducible:
100%
Steps:
1.Convert a guest from VMware by virt-v2v ans set vcpu and memory size with options smp and memsize during conversion
# virt-v2v -ic vpx://root@10.73.213.134/data/cluster/10.73.212.36/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk9.0.0 -io vddk-thumbprint=C3:83:1D:C0:6D:4C:47:83:5A:B9:6E:0E:FA:5A:15:22:B4:75:D5:7E -ip /home/passwd esx8.0-rhel9.7-x86_64-efi --smp 8 --memsize 4096 [ 0.0] Setting up the source: -i libvirt -ic vpx://root@10.73.213.134/data/cluster/10.73.212.36/?no_verify=1 -it vddk esx8.0-rhel9.7-x86_64-efi [ 1.7] Opening the source [ 30.8] Checking filesystem integrity before conversion [ 39.0] Detecting if this guest uses BIOS or UEFI to boot [ 39.1] Inspecting the source [ 43.0] Detecting the boot device [ 43.1] Checking for sufficient free disk space in the guest [ 43.1] Converting Red Hat Enterprise Linux 9.7 Beta (Plow) (rhel9.7) to run on KVM ** (process:514575): WARNING **: 03:39:35.148: Entity http://pcisig.com/pci/1af4/1012 referenced but not defined virt-v2v: This guest has virtio drivers installed. [ 73.6] Setting a random seed [ 73.6] SELinux relabelling [ 76.1] Mapping filesystem data to avoid copying unused and blank areas [ 76.6] Checking filesystem integrity after conversion [ 77.7] Closing the overlay [ 78.0] Assigning disks to buses [ 78.0] Checking if the guest needs BIOS or UEFI to boot virt-v2v: This guest requires UEFI on the target to boot. [ 78.0] Setting up the destination: -o libvirt [ 80.2] Copying disk 1/1 █ 100% [****************************************] [ 203.2] Creating output metadata [ 203.2] Finishing off
2. Check vcpu number and memory size of the guest after v2v conversion, found the cpu and memory size have no change
# virsh dumpxml esx8.0-rhel9.7-x86_64-efi |grep memory -A 2 <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>1</vcpu>
Actual result:
As above description
Expect result:
Fix the bug
Additional info
