Red Hat Bugzilla – Bug 448239
Cannot start last VM in list
Last modified: 2009-01-23 10:45:20 EST
Description of problem:
In virt-manager I cannot start the last VM in the list. Always get this error:
...QEMU quit during console startup bind() failed.
Version-Release number of selected component (if applicable):
# yum list virt-manager qemu
Loaded plugins: fastestmirror, refresh-packagekit
Loading mirror speeds from cached hostfile
* updates: www.gtlib.gatech.edu
* adobe-linux-i386: linuxdownload.adobe.com
* fedora: www.gtlib.gatech.edu
qemu.i386 0.9.1-5.fc9 installed
virt-manager.i386 0.5.4-3.fc9 installed
Steps to Reproduce:
1. startup virt-manager
2. try to start last VM in list
VM does not start and shows error
Can you please post ~/.virt-manager/virt-manager.log, and a 'virsh dumpxml' of
the offending VM? Thanks.
Created attachment 306777 [details]
TEST1 is the VM that was startable and now no longer will start.
I've tried undefining and redefining it as well, still will not start, same
Created attachment 306779 [details]
virsh dumpxml TEST1
Okay, I'm not sure what caused this problem to take place, but it isn't virt-manager's fault.
That 'bind' error is what you get when 2 vms try to use the same vnc port. This means you either have misconfigured vms, or something went wrong at the libvirt level. If you have multiple VMs configured to use the same vnc port, I'd recommend changing them. If not, this is probably the result of a libvirt crash or some other bug long fixed.
If you can still reproduce this issue, reopen this bug, and post:
virt-manager and libvirt version
virsh list --all
virsh dumpxml for all vms
ps axwww | grep qemu
Closing as WORKSFORME.