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.
** Changed in: libvirt (Ubuntu)
Status: Triaged => Fix Released
--
You received
** Changed in: libvirt (Ubuntu)
Status: New = Triaged
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Low
--
starting a VM with an SDL display hangs virtmanager and virsh
https://bugs.launchpad.net/bugs/457092
You received this bug notification because you are a member of
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.
** Attachment added: testlive.xml
http://launchpadlibrarian.net/34137331/testlive.xml
--
starting a VM with an SDL display hangs
** Changed in: libvirt (Ubuntu)
Status: Incomplete = New
** Changed in: libvirt (Ubuntu)
Assignee: Jamie Strandboge (jdstrand) = (unassigned)
--
starting a VM with an SDL display hangs virtmanager and virsh
https://bugs.launchpad.net/bugs/457092
You received this bug notification
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34095967/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/34095969/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/34095970/ProcStatus.txt
--
starting a
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
** Changed in: libvirt (Ubuntu)
Status: New =
