[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] xen-unstable on OL6 (RHEL6 clone) problems



On Thu, 10 Feb 2011, Dan Magenheimer wrote:
> > >> > Reading the wiki, isn't the change only required when using xl?
> > >> > Shouldn't xm and xend work just as it has always been?
> > >>
> > >> xm and xend are still available (for now), but using xl and libxl is
> > >> preferred.
> > >
> > > But the answer to Fajar's question is NO, correct?
> > 
> > I believe the answer to his question should have been yes (xend/xm are
> > still there and should work as before (for now)). You may have just
> > come across a bug that was tested. xm is not automatically tested by
> > the automated testing system (example here:
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/5680/)
> 
> OK, thanks.  Indeed, after setting up the bridging, I am continuing to
> have the same problem ("brctl show" complains repeatedly) on a machine
> with Xen installed, but the bridging works fine on the same OS (Oracle
> Linux 6) without Xen installed.
> 
> Will follow up with more info when available.
>  
> > > bridging stuff is irrelevant to xm vs xl and must be done
> > > even if you are using xm/xend on 4.1, correct?
> > >
> > 
> > The old xen bridge code is currently still in the tree, but it is not
> > the preferred use.
> 
> Is this commented out and easy to turn on?  Or maybe it's NOT
> commented out and is causing the breakage I am seeing?

The script is still installed but nobody is calling it.
If you are using xl you need to add

/etc/xen/scripts/network-bridge start

somewhere in your init scripts.

If you use xend you need to uncomment the line

# (network-script network-bridge)

in /etc/xen/xend-config.sxp.


It is worth mentioning this in the wiki so that people can still have
the old behaviour if they want to.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.