On Fri, Aug 10, 2007 at 05:06:30PM +0100, Daniel P. Berrange wrote:
> On Fri, Aug 10, 2007 at 12:03:10PM -0400, Daniel Veillard wrote:
> > On Fri, Aug 10, 2007 at 04:36:25PM +0100, Daniel P. Berrange wrote:
> > > The virtual networks stuff was never added to the xm driver for Xen 3.0.3
> > > or ear
Daniel P. Berrange wrote:
The virtual networks stuff was never added to the xm driver for Xen 3.0.3
or earlier. This means that if adding a virtual network the bridge device
won't get defined in the config. This patch addreses this, and also fixes
a tiny mem leak in the equivalent code in the xen
On Fri, Aug 10, 2007 at 12:03:10PM -0400, Daniel Veillard wrote:
> On Fri, Aug 10, 2007 at 04:36:25PM +0100, Daniel P. Berrange wrote:
> > The virtual networks stuff was never added to the xm driver for Xen 3.0.3
> > or earlier. This means that if adding a virtual network the bridge device
> > won'
On Fri, Aug 10, 2007 at 04:36:25PM +0100, Daniel P. Berrange wrote:
> The virtual networks stuff was never added to the xm driver for Xen 3.0.3
> or earlier. This means that if adding a virtual network the bridge device
> won't get defined in the config. This patch addreses this, and also fixes
> a
The virtual networks stuff was never added to the xm driver for Xen 3.0.3
or earlier. This means that if adding a virtual network the bridge device
won't get defined in the config. This patch addreses this, and also fixes
a tiny mem leak in the equivalent code in the xend driver.
Dan.
--
|=- Red
