Re: [libvirt] [BUG] second libvirtd breaks the first
On Thu, May 15, 2008 at 01:47:05PM +0200, Stefan de Konink wrote:
By accident I ran a second instance of libvirtd. This second instance
did
not terminate the first instance nor did it detect there was already a
running instance. By killing the second instance the first did not work
anymore.
I imagine that the second instance is unlink()ing the UNIX domain socket of
the first instance. It should really check the PID file and refuse to start
up if another instance is already running.
Next to this, why does libvirtd terminate its iSCSI connections upon
stop?
I saw it cannot gracefully 'reuse' existing sessions, but it is absurd
that restarting libvirtd would kill all running VMs on a host using iSCSI,
or not able to get a storage pool up because it is already logged in to
it.
We ought to be able to make it reuse an existing session if that session
matches one of the defined libvirt pools. We shouuld also make the auto
shutdown behaviour configurable per storage pool. Currently we only
configure auto-startup.
Regards,
Dan.
--
|: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|