On Wed, Jan 14, 2009 at 12:44:50PM +, Daniel P. Berrange wrote:
> On Wed, Jan 14, 2009 at 08:55:46AM +, Mark McLoughlin wrote:
> > On Tue, 2009-01-13 at 20:49 +, Daniel P. Berrange wrote:
> > > Currently when we shutdown the virtual networks are all shutdown too.
> > > This is less tha
On Wed, Jan 14, 2009 at 08:55:46AM +, Mark McLoughlin wrote:
> On Tue, 2009-01-13 at 20:49 +, Daniel P. Berrange wrote:
> > Currently when we shutdown the virtual networks are all shutdown too.
> > This is less than useful if we're letting guest VMs hang around post
> > shutdown of libvirt
On Wed, Jan 14, 2009 at 08:55:46AM +, Mark McLoughlin wrote:
> On Tue, 2009-01-13 at 20:49 +, Daniel P. Berrange wrote:
> > Currently when we shutdown the virtual networks are all shutdown too.
> > +errno = EINVAL;
> > +return -1;
> > +}
> > +
> > +memset(&ifr, 0, s
On Tue, 2009-01-13 at 20:49 +, Daniel P. Berrange wrote:
> Currently when we shutdown the virtual networks are all shutdown too.
> This is less than useful if we're letting guest VMs hang around post
> shutdown of libvirtd, because it means we're tearing their network
> connection out from und
Currently when we shutdown the virtual networks are all shutdown too.
This is less than useful if we're letting guest VMs hang around post
shutdown of libvirtd, because it means we're tearing their network
connection out from under them. This patch fixes that allowing networks
to survive restarts,
