On Tue, 24 Jan 2012 10:59:33 +0100, Guido Günther <a...@sigxcpu.org> wrote: > > > > When one issues /etc/init.d/libvirt-bin stop, and no VMs are still running, > > it should bring down the virtual networks. > > > > AFAICT, virbr0 is still there, though. > > > > See https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/345485 for some > > details on this issue on Ubuntu side. > > > > AFAIU, the conclusion in that LP bug was that nothing should be down WRT > > networks when VMs are running. > > > > But I think that one could expect that libvirt actually *knows* if VMs are > > still running, and may then be able to do things if no VM it started are > > still running. > > > > Is there something that can be done to have libvirt not mess too much with > > the host when it is no longer needed ? > Libvirt doesn't bring down vms when it stops nor storage pools nor > networks. Why should it?
Because it started a network even though no VM was ever started, AFAICT. I have a virbr0 bridge started automatically even if I haven't used a VM since my machine's boot... and if I stop libvirt-bin, it stays there. Shouldn't it do things in a symetric way as for the start operations ? Hope this is a sound rationale. Best regards, -- Olivier BERGER http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
