Public bug reported:
On Ubuntu 10.04, I was recently unable to start two virtual machine.
Both produced the same error. The error reported by virt-manager was
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 588, in run_domain
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup
self._backend.create()
File "/usr/lib/python2.6/dist-packages/libvirt.py", line 300, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: monitor socket did not show up.: Connection refused
and the error reported by virsh was
error: Failed to start domain WindowsVista-IE7
error: monitor socket did not show up.: Connection refused
It turned out that the reason the virtual machines would not start is
that the sources for their virtual cdrom drives were unavailable. One VM
had an iso file as the source, but I had deleted the iso file. The other
had my physical cdrom drive as the source, but I did not have a disk in
it. After disconnecting these unavailable sources the VMs started
successfully.
It would have been nice if virt-manager and virsh had reported that some
configured disks were unavailable instead of reporting a generic message
that the connection to the VM "did not show up".
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
Uninformative libvirt error message when a virtual disk source is unavailable
https://bugs.launchpad.net/bugs/613969
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
