[Libvir] Restarting of libvirt_qemud daemon

Daniel P. Berrange berrange at redhat.com
Fri Mar 9 03:25:44 UTC 2007

Thinking about later RPM upgrades I think we need to think about whether it
will be possible to restart the libvirt_qemud while guests & networks are
running. There's a couple of issues:

 - We do waitpid() to cleanup qemu & dnsmasq processes when we stop domains
   & networks, or to detect when they crash. For the former, we could may
   they daemons to avoid waitpid() cleanup, but we'd still need waitpid to
   be able to detect shutdowns. There is also the issue of enumerating
   running instances.

 - We always try to re-create a bridge device at startup, even if it already
   exists. Likewise we always try to add the IPtables rules & start dnsmasq.
   We can easily detect if the bridge already exists. I think we can probably
   double check iptables rulles too., The tricky one is figuring out whether
   a dnsmasq instance is still running.

Dealing with theses not only helps planned restarts, but will also make it
possible start up the daemon again after a crash without having to kill off
all guests & networks manually. So I think it is worth investigating what
we can do to enable restarts. It might be worth waiting until we sort out
whether we'll merge libvirt_qemud with the generic libvirtd remote daemon
though so we don't have to do the work twice over.

|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

More information about the libvir-list mailing list