Description virt-v2v: warning: display <graphics type='sdl'> was ignored when converting rhel5 guest with sdl graphics Version: virt-v2v-1.27.60-1.1.el7.x86_64 libguestfs-1.27.60-1.1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.Prepare a rhel5 xen guest with sdl graphics. # virsh dumpxml rhel6.5-test <graphics type='sdl' display='localhost:10.0' xauth='/root/.Xauthority'/> 2.Use virt-v2v to convert the guest,warning info shows:virt-v2v: warning: display <graphics type='sdl'> was ignored # virt-v2v -ic xen+ssh://10.66.106.64 -os default rhel6.5-test -on sdl-test -of qcow2 [ 0.0] Opening the source -i libvirt -ic xen+ssh://10.66.106.64 rhel6.5-test virt-v2v: warning: display <graphics type='sdl'> was ignored [ 16.0] Creating an overlay to protect the source from being modified [ 31.0] Opening the overlay [ 57.0] Initializing the target -o libvirt -os default [ 57.0] Inspecting the overlay [ 67.0] Checking for sufficient free disk space in the guest [ 67.0] Estimating space required on target for each disk [ 67.0] Converting Red Hat Enterprise Linux Server release 6.5 (Santiago) to run on KVM This guest has virtio drivers installed. [ 146.0] Mapping filesystem data to avoid copying unused and blank areas [ 147.0] Closing the overlay [ 147.0] Copying disk 1/1 to /var/lib/libvirt/images/sdl-test-sda (qcow2) (100.00/100%) [ 288.0] Creating output metadata 3.After conversion,check guest graphics,it defaults to vnc. Actual results： Confusing warning info shows:virt-v2v: warning: display <graphics type='sdl'> was ignored Expected results: No such warning info shows. Additional info:
Old virt-v2v was a bit confused as to how it handled <graphics type='sdl'> . If it saw it in the input, it would parse it (and not give a warning), but none of the output drivers would use it -- either it would be ignored or replaced with spice. New virt-v2v explicitly warns you that SDL is not going to be handled. I think I will make the warning clearer to fix this bug. The basic problem however is that SDL is not handled by the old or new virt-v2v. And indeed cannot be handled because management layers like OpenStack and RHEV don't work in a way that SDL could work. SDL is only relevant if you run qemu directly on your local machine.
Upstream fix: https://github.com/libguestfs/libguestfs/commit/626d85d80be994065951b5f17706ca33ca5fc152 This changes the warning to: virt-v2v: warning: virt-v2v does not support local displays, so <graphics type='sdl'> in the input libvirt XML was ignored which is hopefully clearer.
Tested with: libguestfs-1.27.61-1.1.el7.x86_64 virt-v2v-1.27.61-1.1.el7.x86_64 # virt-v2v -ic xen+ssh://10.66.106.64 -os default rhel6.5-test -on sdl-test -of qcow2 [ 0.0] Opening the source -i libvirt -ic xen+ssh://10.66.106.64 rhel6.5-test virt-v2v: warning: virt-v2v does not support local displays, so <graphics type='sdl'> in the input libvirt XML was ignored [ 16.0] Creating an overlay to protect the source from being modified [ 54.0] Opening the overlay [ 123.0] Initializing the target -o libvirt -os default [ 125.0] Inspecting the overlay [ 156.0] Checking for sufficient free disk space in the guest [ 156.0] Estimating space required on target for each disk [ 156.0] Converting Red Hat Enterprise Linux Server release 6.5 (Santiago) to run on KVM This guest has virtio drivers installed. [ 234.0] Mapping filesystem data to avoid copying unused and blank areas [ 235.0] Closing the overlay [ 236.0] Copying disk 1/1 to /var/lib/libvirt/images/sdl-test-sda (qcow2) (100.00/100%) [ 318.0] Creating output metadata Pool default refreshed Domain sdl-test defined from /tmp/v2vlibvirt64f57b.xml [ 320.0] Finishing off The warning info shows as: virt-v2v: warning: virt-v2v does not support local displays, so <graphics type='sdl'> in the input libvirt XML was ignored After conversion,the graphics become vnc. Refer to the above comments,move the bug to VERIFIED.
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, 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://rhn.redhat.com/errata/RHBA-2015-0303.html