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
2016-09-18 09:44:02 UTC
Created attachment 1202144[details]
floppy-guest-on-vmware
Description of problem:
There is virt-v2v: warning: /files/boot/grub2/device.map/hd0 references unknown showing when convert a guest which has vda disk type by virt-p2v
Version-Release number of selected component (if applicable):
virt-v2v-1.32.7-3.el7.x86_64
libguestfs-1.32.7-3.el7.x86_64
qemu-kvm-1.5.3-122.el7.x86_64
libvirt-2.0.0-8.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Prepare a guest which has vda disk type
<disk type='volume' device='disk'>
<driver name='qemu' type='raw' cache='none'/>
<source pool='default' volume='esx6.0-rhel7.2-x86_64-sda'/>
<backingStore/>
<target dev='vda' bus='virtio'/>
<boot order='2'/>
<alias name='virtio-disk0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</disk>
2.Boot this guest into p2v client and input info of v2v conversion server
3.Convert this guest to glance after inputting conversion info, but there is virt-v2v: warning: /files/boot/grub2/device.map/hd0 references unknown showing during conversion
Actual results:
As above description
Expected results:
Because v2v convsersion will not pop up warning about references unknown device "vda" if convert a guest from libvirtxml,should no virt-v2v: warning: /files/boot/grub2/device.map/hd0 references unknown when convert a guest which has vda disk type by virt-p2v
Comment 3Richard W.M. Jones
2016-09-19 10:13:21 UTC
This is an artifact of the way that we test virt-p2v conversions using
a source virtual machine instead of a source physical machine.
Virt-p2v generates the following XML fragment for the disk:
<disk type="network" device="disk">
<driver name="qemu" type="raw"/>
<source protocol="nbd">
<host name="localhost" port="42144"/>
</source>
<target dev="vda"/>
</disk>
The <target> element should be:
<target dev="vda" bus="virtio"/>
but because the bus is missing, the block device mapping code doesn't
recognize that the source is Source_virtio_blk and so does not set
up the block mapping table correctly.
However this would never occur in real virt-p2v scenarios where the source
must be a physical machine (virtio-blk could never be present as a physical
device).
So this is NOTABUG - you can simply ignore the warning as long as it does
not happen when converting a physical machine.
Created attachment 1202144 [details] floppy-guest-on-vmware Description of problem: There is virt-v2v: warning: /files/boot/grub2/device.map/hd0 references unknown showing when convert a guest which has vda disk type by virt-p2v Version-Release number of selected component (if applicable): virt-v2v-1.32.7-3.el7.x86_64 libguestfs-1.32.7-3.el7.x86_64 qemu-kvm-1.5.3-122.el7.x86_64 libvirt-2.0.0-8.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.Prepare a guest which has vda disk type <disk type='volume' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source pool='default' volume='esx6.0-rhel7.2-x86_64-sda'/> <backingStore/> <target dev='vda' bus='virtio'/> <boot order='2'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> 2.Boot this guest into p2v client and input info of v2v conversion server 3.Convert this guest to glance after inputting conversion info, but there is virt-v2v: warning: /files/boot/grub2/device.map/hd0 references unknown showing during conversion Actual results: As above description Expected results: Because v2v convsersion will not pop up warning about references unknown device "vda" if convert a guest from libvirtxml,should no virt-v2v: warning: /files/boot/grub2/device.map/hd0 references unknown when convert a guest which has vda disk type by virt-p2v