All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Berthault <Philippe.Berthault@Bull.net>
To: Xen-Devel <Xen-Devel@lists.xensource.com>,
	Xen-Users <Xen-Users@lists.xensource.com>
Subject: Error: Device 0 (vif) could not be connected. (Xen 3.0.1 regression)
Date: Tue, 07 Feb 2006 17:10:01 +0100	[thread overview]
Message-ID: <43E8C659.9070704@Bull.net> (raw)

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.

             reply	other threads:[~2006-02-07 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 16:10 Philippe Berthault [this message]
2006-02-08 17:21 ` Error: Device 0 (vif) could not be connected. (Xen 3.0.1 regression) Ewan Mellor
2006-02-08 17:36 ` [Xen-devel] " Rob Gardner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43E8C659.9070704@Bull.net \
    --to=philippe.berthault@bull.net \
    --cc=Xen-Devel@lists.xensource.com \
    --cc=Xen-Users@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.