xen kernel with dom0 in Fedora 10?

Mark McLoughlin markmc at redhat.com
Mon Oct 6 08:10:47 UTC 2008


On Fri, 2008-10-03 at 20:40 +0100, Daniel P. Berrange wrote:
> On Fri, Oct 03, 2008 at 02:46:59PM -0400, Jeremy Katz wrote:
> > On Fri, 2008-10-03 at 14:41 -0400, James Ralston wrote:
> > > To claim "out of the box" support for KVM bridge networking,
> > > virt-manager has to be able to do all of this automatically.  That
> > > means that either virt-manager itself needs to know how to turn a
> > > physical device into a bridged device, or anaconda needs to do this at
> > > system install time.  (E.g., any physical device configured with a
> > > fixed IP address is automatically created as a bridge.)
> > 
> > anaconda is certainly not going to do this.  Changing a device to be
> > bridged has some interesting consequences in a lot of networking
> > environments.  Not to mention that anaconda is getting out of the
> > business of the network setup as everything should be being handled by
> > NetworkManager
> 
> I wouldn't expect anaconda todo this either - there's simply too many
> complications with bridging to expect any tool to automatically get it
> right. Ultimately networkmanager needs a capability optionally enable
> sharing of a physical device between host & guest. It is getting much
> closer to being ready for this type of capability with its recent
> releases.

Yeah, here's the feature request:

  http://bugzilla.gnome.org/show_bug.cgi?id=543232

Talking to dcbw, the thing he seemed most concerned about was how this
"physical interface sharing" could be confused with NetworkManager's new
"connection sharing" feature.

Since the latter concept isn't really exposed in the UI now - i.e. you
just do "Create New Wireless Network" and traffic on that network will
be automatically forwarded/NAT-ed via the default route - then I don't
think that's such an issue any more.

Cheers,
Mark.




More information about the devel mailing list