Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionmxie@redhat.com
2023-04-28 09:13:45 UTC
Created attachment 1960701[details]
guest-has-no-disk-on-rhv.png
Description of problem:
Windows guest has no disk after converting to RHV with option '--block-driver virtio-scsi' by v2v
Version-Release number of selected component (if applicable):
virt-v2v-2.3.4-1.el9.x86_64
libguestfs-1.50.1-3.el9.x86_64
guestfs-tools-1.50.1-2.el9.x86_64
nbdkit-server-1.34.1-1.el9.x86_64
libvirt-libs-9.2.0-1.el9.x86_64
qemu-img-8.0.0-1.el9.x86_64
virtio-win-1.9.33-0.el9_2.noarch
How reproducible:
100%
Steps to Reproduce:
1.Convert a windows guest from VMware to rhv with option ' --block-driver virtio-scsi ' by v2v
# virt-v2v -ic esx://root.212.36/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.0 -io vddk-thumbprint=11:97:52:B3:B6:5D:C4:DD:05:D9:D0:43:31:0E:98:CB:73:6E:D6:45 -ip /home/esxpwd esx8.0-win2022-x86_64 -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data -op /home/rhvpasswd --block-driver virtio-scsi
[ 0.0] Setting up the source: -i libvirt -ic esx://root.212.36/?no_verify=1 -it vddk esx8.0-win2022-x86_64
[ 1.4] Opening the source
[ 6.8] Inspecting the source
[ 13.6] Checking for sufficient free disk space in the guest
[ 13.6] Converting Windows Server 2022 Standard to run on KVM
virt-v2v: This guest has virtio drivers installed.
[ 32.9] Mapping filesystem data to avoid copying unused and blank areas
[ 34.8] Closing the overlay
[ 35.1] Assigning disks to buses
[ 35.1] Checking if the guest needs BIOS or UEFI to boot
[ 35.1] Setting up the destination: -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data
[ 46.4] Copying disk 1/1
█ 100% [****************************************]
[ 335.3] Creating output metadata
[ 355.1] Finishing off
2.Found the guest has no disk after v2v conversion, pls refer to screenshot ''
Actual results:
As above description
Expected results:
Make v2v conversion fail with correct error if rhv target does not support virtio-scsi
Additional info:
1. Windows guest has disk after converting to libvirt with --block-driver virtio-scsi by v2v
# virt-v2v -ic esx://root.212.36/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.0 -io vddk-thumbprint=11:97:52:B3:B6:5D:C4:DD:05:D9:D0:43:31:0E:98:CB:73:6E:D6:45 -ip /home/esxpwd esx8.0-win2022-x86_64 --block-driver virtio-scsi
[ 0.0] Setting up the source: -i libvirt -ic esx://root.212.36/?no_verify=1 -it vddk esx8.0-win2022-x86_64
[ 1.4] Opening the source
[ 7.3] Inspecting the source
[ 13.6] Checking for sufficient free disk space in the guest
[ 13.6] Converting Windows Server 2022 Standard to run on KVM
virt-v2v: This guest has virtio drivers installed.
[ 26.8] Mapping filesystem data to avoid copying unused and blank areas
[ 28.2] Closing the overlay
[ 28.5] Assigning disks to buses
[ 28.5] Checking if the guest needs BIOS or UEFI to boot
[ 28.5] Setting up the destination: -o libvirt
[ 29.9] Copying disk 1/1
█ 100% [****************************************]
[ 289.6] Creating output metadata
[ 289.6] Finishing off
# virsh dumpxml esx8.0-win2022-x86_64 |grep scsi -A 2 -B 3
<disk type='volume' device='disk'>
<driver name='qemu' type='raw'/>
<source pool='default' volume='esx8.0-win2022-x86_64-sda'/>
<target dev='sda' bus='scsi'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
--
<address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
</controller>
<controller type='pci' index='0' model='pcie-root'/>
<controller type='scsi' index='0' model='virtio-scsi'>
<address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
</controller>
Comment 2Richard W.M. Jones
2023-04-28 09:21:46 UTC
We should probably remove this option downstream ... It's only going
to cause trouble and support calls.
Comment 3Richard W.M. Jones
2023-04-28 14:05:53 UTC
Test the bug with virt-v2v-2.3.4-2.el9.x86_64
Steps:
1.Check option '--block-driver' in virt-v2v man page and help info
# man virt-v2v |grep 'block-driver'
nothing
# virt-v2v --help |grep 'block-driver'
nothing
2.Convert a windows guest from VMware to rhv with option '--block-driver' by v2v
# virt-v2v -ic esx://root.212.36/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.0 -io vddk-thumbprint=11:97:52:B3:B6:5D:C4:DD:05:D9:D0:43:31:0E:98:CB:73:6E:D6:45 -ip /home/esxpwd esx8.0-win2022-x86_64 -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data -op /home/rhvpasswd --block-driver virtio-scsi
virt-v2v: unrecognized option '--block-driver'
Try ‘virt-v2v --help’ or consult virt-v2v(1) for more information.
Result:
Option '--block-driver' has been removed from virt-v2v
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (virt-v2v bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:6376