Error: Device 0 (vif) could not be connected. (Xen 3.0.1 regression)

Error: Device 0 (vif) could not be connected. (Xen 3.0.1 regression)

[Philippe Berthault]

I've compiled and installed the latest Xen release (3.0.1) on my PC.

The previous Xen release, I've used, built on unstable Xen sources on
december 2005, worked very well and with this previous unstable release,
I was able to boot a Linux Knoppix in a Xen domain without any problem.

But with the latest Xen release 3.0.1, the Knoppix boot in a user domain
fails with the following message :
Error: Device 0 (vif) could not be connected. Backend device not found.

My understanding is that the problem comes from Domain-0.
Thanks for your help.

Here an extract of the xend.log file:

2006-02-07 16:38:45 xend] DEBUG (DevController:133) Waiting for devices vif.
[2006-02-07 16:38:45 xend] DEBUG (DevController:139) Waiting for 0.
[2006-02-07 16:38:45 xend] DEBUG (DevController:409) 
hotplugStatusCallback /local/domain/0/backend/vif/4/0/hotplug-status.
[2006-02-07 16:38:45 xend] DEBUG (DevController:409) 
hotplugStatusCallback /local/domain/0/backend/vif/4/0/hotplug-status.
[2006-02-07 16:38:45 xend] DEBUG (DevController:426) 
hotplugStatusCallback 3.
[2006-02-07 16:38:45 xend] 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 1349, in 
waitForDevices
    self.waitForDevices_(c)
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 977, in 
waitForDevices_
    return self.getDeviceController(deviceClass).waitForDevices()
  File "/usr/lib/python/xen/xend/server/DevController.py", line 135, in 
waitForDevices
    return map(self.waitForDevice, self.deviceIDs())
  File "/usr/lib/python/xen/xend/server/DevController.py", line 151, in 
waitForDevice
    raise VmError("Device %s (%s) could not be connected. "
VmError: Device 0 (vif) could not be connected. Backend device not found.

Re: Error: Device 0 (vif) could not be connected. (Xen 3.0.1 regression)

[Ewan Mellor]

On Tue, Feb 07, 2006 at 05:10:01PM +0100, Philippe Berthault wrote:

> I've compiled and installed the latest Xen release (3.0.1) on my PC.
> 
> The previous Xen release, I've used, built on unstable Xen sources on
> december 2005, worked very well and with this previous unstable release,
> I was able to boot a Linux Knoppix in a Xen domain without any problem.
> 
> But with the latest Xen release 3.0.1, the Knoppix boot in a user domain
> fails with the following message :
> Error: Device 0 (vif) could not be connected. Backend device not found.

Could you please use xen-bugtool to attach your logs to a bug, so that I
can take a look?

Thanks,

Ewan.

Re: [Xen-devel] Error: Device 0 (vif) could not be connected. (Xen 3.0.1 regression)

[Rob Gardner]

Philippe Berthault wrote:

>
> But with the latest Xen release 3.0.1, the Knoppix boot in a user domain
> fails with the following message :
> Error: Device 0 (vif) could not be connected. Backend device not found.
>

I ran into a very similar sounding problem recently. It turned out that 
the xen tools could not find the bridge utilities. The latest version of 
brctl that I had installed got put into a a directory that wasn't in 
xm's path. So I just copied 'brctl' into /usr/local/sbin or something 
like that. Not sure if your problem is the same, but it's worth checking.

Rob Gardner