[Pkg-libvirt-maintainers] Bug#657120: Bug#657120: libvirt-bin: Should bring down virtual networks upon stop when no VM still there

[Guido Günther]

severity 657120 wishlist
thanks

On Tue, Jan 24, 2012 at 12:23:03PM +0100, Olivier Berger wrote:
> On Tue, 24 Jan 2012 12:12:53 +0100, Guido Günther <agx at sigxcpu.org> wrote:
> > On Tue, Jan 24, 2012 at 11:26:12AM +0100, Olivier Berger wrote:
> > > On Tue, 24 Jan 2012 10:59:33 +0100, Guido Günther <agx at sigxcpu.org> wrote:
> > > > 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.
> > Are you sure you tested the Debian (in contrast to the Ubuntu)
> > package?
> 
> Yes sir.
> 
> > We don't start any networks automatically. So there's no virbr0 by
> > default. It only does so if you set the network to _autostart_.
> 
> Ok, so let's add a condition : if libvirt is configured so as to start
> the network with autostart, then it should have a symetrical autostop
> feature, for when no VM is left.

The network is autostarted _unconditionally_. It doesn't matter if there
are VMs or not. Libvirt does more than starting and stopping of
machines.  It manages network interfaces, storage, etc. So the feature
you're asking for is configurable auto-destroy of networks, storage
pools and vms when the daemon is stopped if I understand correctly.
That's a valid request and I'd recommend to discuss this with upstream.
Cheers,
 -- Guido

> 
> How does it sound ?