On Mon, 2007-01-15 at 20:06 +0000, Mark McLoughlin wrote:
* Since virConnect is supposed to be a connection to a specific hypervisor, does it make sense to create networks (which should be hypervisor agnostic) through virConnect?
Okay, here's a suggestion - a virConnectPtr is a connection to a specific hypervisor *and* the virtual network supervisor on that same physical machine or user session. What I like about this is that if a domain's description mentions a virtual network, that name is scoped within the network supervisor associated with the hypervisor on which the guest is being created. Attached is a kind of a hacky patch to do something like that - if e.g. you connect to xend, you also get a "network-only" connection to qemud for managing networks. Cheers, Mark.