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] Device 0 (vif) could nto be connected: backend devicenot

To: <pak333@xxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Device 0 (vif) could nto be connected: backend devicenot found
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 28 Apr 2006 09:21:49 +0100
Delivery-date: Fri, 28 Apr 2006 01:22:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZqc6j3vxRg1MTrSMeLSjp8AyYXvAAJmosA
Thread-topic: [Xen-devel] Device 0 (vif) could nto be connected: backend devicenot found
> I have seen many posts regarding this but have not found the 
> solution.  So please can someone shed some light on this Thanks
> - padma
> 
> I get this error when I do try to create a domU guest (xen 
> 3.0.0, 2.6.12.6).
> The vif is set to
> vif = [ ' mac=aa:00:00:00:11, bridge=xenbr0' ]  and a "brctl 
> show" shows (brctl is in /usr/local/sbin)
> xenbr0    8000,fefffffff  interfaces vif0.0 peth0

3.0.2-2 seems to be a lot more robust working with the various
udev/hotplug versions in different distros. Please can you try
upgrading. You should also look in /var/log/xend-hotplug.log

Ian
 
> Xend.log shows:
>  ERROR (SrvBase:87) Request wait_for_devices failed.  
> Traceback (most recent call last):
>     File "/usr/lib/python/xen/web/SrvBase.py", line 85, in perform
>       return op_method(op, req)
>     File "/usr/lib/python/xen/xend/server/SrvDomain.py", line 
> 72, in op_wait_for _devices
>       return self.dom.waitForDevices()
>     File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 
> 1343, in waitForDevi ces
>       self.waitForDevices_(c)
>     File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 
> 971, in waitForDevic es_
>       return self.getDeviceController(deviceClass).waitForDevices()
>     File "/usr/lib/python/xen/xend/server/DevController.py", 
> line 135, in waitFo rDevices
>       return map(self.waitForDevice, self.deviceIDs())
>     File "/usr/lib/python/xen/xend/server/DevController.py", 
> line 151, in waitFo rDevice
>       raise VmError("Device %s (%s) could not be connected. "
>   VmError: Device 0 (vif) could not be connected. Backend 
> device not found.
> 
> 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 

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

<Prev in Thread] Current Thread [Next in Thread>
  • RE: [Xen-devel] Device 0 (vif) could nto be connected: backend devicenot found, Ian Pratt <=