Hide Forgot
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
Created attachment 1202145 [details] virt-p2v-vda-log
Pls ignore the attachment"floppy-guest-on-vmware"
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.