WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Problem with vif - help!!!!

On Tue, Nov 22, 2005 at 04:36:30PM +0100, Michael Mey wrote:

> On Tuesday 22 November 2005 15:59, DIEDERIT@xxxxxxxxxxxxxxxxxxxxxxxxxxxx 
> wrote:
> > Heya
> >
> > #Kernel
> >
> > #kernel="/boot/vmlinuz-2.6.11.12-xenU"
> > kernel="/boot/vmlinuz-2.6.12-xenU"
> >
> > #System
> > memory=392
> > name="RHEL4"
> > nics=0
> > #disk=['phy:/dev/VGVMSXEN/lvol0,hda1, w']
> > #disk=['148.191.190.7:/xen,hda1,w']
> > #disk=['phy:/xen,hda1, w']
> > #root="/dev/hda1"
> >
> > #runlevel
> > extra="3"
> >
> > #nfs
> > root="/dev/nfs"
> > nfs_server='148.191.190.7'
> > nfs_root='/xen'
> >
> 
> Hi,
> 
> I can't find something like 
> 
> vif = [ 'bridge=xenbr0' ]
> 
> in your configfile. This example is for usage of bridged networking.
> Maybe your backend-device couldn't be found because you haven't defined it 
> here?
> Just a clue, maybe it helps.

The vif-bridge script can now discover the bridge name for itself, so you
shouldn't need this, as long as your setup is fairly standard.

Ewan.

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