On Fri, Mar 09, 2007 at 04:20:58PM +0000, Mark McLoughlin wrote:
On Fri, 2007-03-09 at 14:32 +0000, Daniel P. Berrange wrote:
> On Fri, Mar 09, 2007 at 02:27:02PM +0000, Mark McLoughlin wrote:
> > On Fri, 2007-03-09 at 03:03 +0000, Daniel P. Berrange wrote:
> > > For the reverse Xen will tell us what bridge device a
> > > guest is using, and we can reverse lookup the corresponding network
> >
> > I'm not sure why you want this?
>
> Without this you be sending in
>
> <interface type='network'>
> <source network='foo'>
> </interface>
>
> And be getting back
>
> <interface type='bridge'>
> <source bridge='virbr0'>
> </interface>
>
> As far as is possible the XML used to create a VM should be identical
> to that you get back from libvirt once it is running.
Absolutely, very good point.
There's a few places where we return the current running state rather
than the initial configuration we provided, but this would be a
particularly bad case.
It's a bit fugly, though - should libvirt do ListDomains(),
GetBridgName() and match the bridge name, or should we have
virNetworkLookupByBridge() and make qemud do the lookup itself?
I was actually thinking virNetworkLookupByBridge could be a very handy
API to have
Dan.
--
|=- 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 -=|