[libvirt] Can't get connection to libvirt if one of the guests' monitor is occupied by other app
Daniel P. Berrange
berrange at redhat.com
Thu Mar 31 10:13:16 UTC 2011
On Wed, Mar 30, 2011 at 03:38:19PM +0800, Osier Yang wrote:
> Hi,
>
> As $subject, e.g. the monitor is being used by netcat.
>
> Is it expected? Should we only skip to reconnect the domain monitor
> which is being locked by other app with a timeout specified on
> "qemuMonitorOpenUnix" (it blocks when trying to connect to the unix
> socket)? so that it can get a connection, and could manage
> other domains.
>
> How to produce:
>
> 1) # service libvirtd stop
> 2) # nc -U /var/lib/libvirt/qemu/$guest.monitor
> 3) # virsh (hangs forever if nc process is not killed)
This is user error. Allowing the user to connect to the QEMU
monitor for any libvirt managed QEMU instances is *not*
supported while libvirtd is running. They must remove their
'nc' process before starting libvirtd again.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
More information about the libvir-list
mailing list