DIEDERIT@ing.boehringer-ingelheim.com
2005-Nov-22 14:59 UTC
[Xen-devel] Problem with vif - help!!!!
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'' This is my config file. When I replace nics=0 with nics=1 i get the following error: Error: Device 0 (vif) could not be connected. Backend device not found I need nics=1 because i need to connect to my nfs server where my domU is located. With nics=0 it won''t also work beacuase "no eth0 could be found" Thomas Diederich ************************************************** * Boehringer Ingelheim Pharma GmbH & Co.KG * A Informationsverarbeitung / Diplomant Systemtechnik * * Mail: diederit@ing.boehringer-Ingelheim.com <mailto:diederit@ing.boehringer-Ingelheim.com> * Phone: +49 (0)6132/77-98151 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, Nov 22, 2005 at 03:59:13PM +0100, DIEDERIT@ing.boehringer-ingelheim.com 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'' > > This is my config file. > When I replace nics=0 with nics=1 i get the following error: > > Error: Device 0 (vif) could not be connected. Backend device not found > > I need nics=1 because i need to connect to my nfs server where my domU is > located.Do you get any useful information in /var/log/{debug,messages,syslog}? Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 11/22/05, DIEDERIT@ing.boehringer-ingelheim.com > This is my config file.> When I replace nics=0 with nics=1 i get the following error: > > Error: Device 0 (vif) could not be connected. Backend device not found > > I need nics=1 because i need to connect to my nfs server where my domU is > located. > > With nics=0 it won''t also work beacuase "no eth0 could be found" > > Thomas Diederich > > ************************************************** > * Boehringer Ingelheim Pharma GmbH & Co.KG > * A Informationsverarbeitung / Diplomant Systemtechnik > * > * Mail: diederit@ing.boehringer-Ingelheim.com > * Phone: +49 (0)6132/77-98151 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > >Are you using bridged network? Could you add "set -x" to begining of /etc/xen/scripts/vif-{bridge,route,nat} and set log_priority on udev to debug? ("udevcontrol log_priority=debug" does that in runtime, or you can set that on udev.conf and restart udevd) After that you will have on /var/log/debug a very usefull log of hotplug script responsible for setting up vif. -- Murillo Fernandes Bernardes _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tuesday 22 November 2005 15:59, DIEDERIT@ing.boehringer-ingelheim.com 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. Cheers Mike ---------------------------------------------------------------------------------------- Michael Mey Thinking Objects Software GmbH | mailto: michael.mey@to.com Lilienthalstrasse 2/1 | phone: +49 711 88770-147 70825 Stuttgart-Korntal, Germany | fax: +49 711 88770-449 ---------------------------------------------------------------------------------------- _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, Nov 22, 2005 at 04:36:30PM +0100, Michael Mey wrote:> On Tuesday 22 November 2005 15:59, DIEDERIT@ing.boehringer-ingelheim.com > 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@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, Nov 24, 2005 at 09:30:54AM +0100, DIEDERIT@ing.boehringer-ingelheim.com wrote:> These are parts of my messages > > > Nov 22 15:54:55 ingpcxen002 kernel: nfs_fhget: iget failed > Nov 22 15:54:55 ingpcxen002 kernel: NFS: Buggy server - nlink == 0! > Nov 22 15:54:55 ingpcxen002 kernel: nfs_fhget: iget failed > Nov 22 15:54:55 ingpcxen002 kernel: NFS: Buggy server - nlink == 0! > Nov 22 15:54:55 ingpcxen002 kernel: nfs_fhget: iget failed > Nov 22 15:54:55 ingpcxen002 kernel: NFS: Buggy server - nlink == 0! > Nov 22 15:54:55 ingpcxen002 kernel: nfs_fhget: iget failed > Nov 22 15:54:55 ingpcxen002 kernel: NFS: Buggy server - nlink == 0! > Nov 22 15:54:55 ingpcxen002 kernel: nfs_fhget: iget failed > Nov 22 15:55:56 ingpcxen002 logger: /etc/xen/scripts/vif-bridge: Could not > find bridge, and none was specifiedIt''s this message that is the smoking gun. The vif-bridge script cannot find a bridge to attach to. Have you altered the basic configuration (/etc/xen/xend-config.sxp)? Do you have brctl installed (though I thought we''d fixed that test recently)? What version of Xen are you using? What happens when you run /etc/xen/scripts/network-bridge start manually? Do you get anything in /var/log/messages then? What do you get when you type "brctl show" afterwards? Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel