starting a VM with an SDL display hangs virtmanager and virsh

[P]

setup a VM with virtmanager then ran it OK (using vnc)
stop the VM
remove the display in the VM config
add an SDL display to the config
start the VM

==> virtmanager hangs
==> virsh connects but hangs
==> libvirt takes 100% cpu
$ ps -ef | grep libvirt
root 3651 1 16 12:14 ? 00:07:32 /usr/sbin/libvirtd -d

$ ps -eLf | grep virt
root 3651 1 3651 0 6 12:14 ? 00:00:00 /usr/sbin/libvirtd -d
root 3651 1 3829 19 6 12:14 ? 00:09:20 /usr/sbin/libvirtd -d
root 3651 1 3830 0 6 12:14 ? 00:00:00 /usr/sbin/libvirtd -d
root 3651 1 3831 0 6 12:14 ? 00:00:00 /usr/sbin/libvirtd -d
root 3651 1 3832 0 6 12:14 ? 00:00:00 /usr/sbin/libvirtd -d
root 3651 1 3833 0 6 12:14 ? 00:00:00 /usr/sbin/libvirtd -d
nobody 3798 1 3798 0 1 12:14 ? 00:00:00 dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file= --listen-address 192.168.122.1 --except-interface lo --dhcp-range 192.168.122.2,192.168.122.254
pascal 7097 1 7097 0 1 12:52 ? 00:00:01 python /usr/share/virt-manager/virt-manager.py
pascal 7796 5345 7796 0 1 13:02 pts/2 00:00:00 grep --color=auto virt

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/sbin/libvirtd
Package: libvirt-bin 0.6.1-0ubuntu5.1
ProcAttrCurrent: unconfined
ProcEnviron: PATH=(custom, no user)
SourcePackage: libvirt
Uname: Linux 2.6.28-11-generic i686

[Jamie Strandboge (jdstrand)]

This works fine for me in karmic when replacing the vnc xml with the following:
<graphics type='sdl' display=':0.0'/>

Then defining the machine accordingly. Can you please attach the xml of the domain by performing:
$ virsh dumpxml <domain>

[P (p92)]

strangely when using virt-manager to update the display resource the parameter display=':0.0' is missing.

I have also indicated the result of virsh version.

[Stefan Bader (smb)]

Reading the comments this sounds like it might have been an issue in the Jaunty/9.04 version of virt-manager but fixed in Karmic/9.10. Jaunty would be no longer supported, so I close this as fix-released.