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-users

[Xen-users] Error: Device 0 (vif) could not be connected. Backend device

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Error: Device 0 (vif) could not be connected. Backend device not found. when using network-route
From: "Timo Czerny" <timo@xxxxxxxxxxx>
Date: Sun, 14 Jan 2007 04:37:42 +0100
Delivery-date: Sat, 13 Jan 2007 19:36:38 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Opera Mail/9.10 (Linux)

Hi list,

I'm using prepackaged Xen on Suse 10.1 as dom0 and one domU which is ubuntu dapper. The setup worked very good for a while using network-bride setup, bringing the domU to the internet via NAT. Now my provider gave me a 2nd IP Adress and i want to abandon briging complete and route the new IP adress to the domU. I changed xend-config.sxp to use network-route and vif-route scripts, and adjusted the domU to this:

kernel = "/xen/ubuntu/vmlinuz"
memory = 256
name = "ubuntu"
vif = [ 'ip=1.2.3.4' ]
ip="1.2.3.4"
disk = [ 'file:/xen/ubuntu/root,hda1,w', 'file:/xen/ubuntu/swap,hda2,w' ]
root = "/dev/hda1 ro"

Now when tryiung to bring up the domU i get:

# xm create ubuntu
Using config file "/etc/xen/vm/ubuntu".
Error: Device 0 (vif) could not be connected. Backend device not found.

This is xend.log:
<startup msgs here>
[2007-01-14 04:22:04 xend.XendDomainInfo] DEBUG (XendDomainInfo:881) XendDomainInfo.handleShutdownWatch [2007-01-14 04:22:04 xend] DEBUG (DevController:132) Waiting for devices vif.
[2007-01-14 04:22:04 xend] DEBUG (DevController:138) Waiting for 0.
[2007-01-14 04:22:04 xend] DEBUG (DevController:403) hotplugStatusCallback /local/domain/0/backend/vif/11/0/hotplug-status. [2007-01-14 04:22:05 xend] DEBUG (DevController:403) hotplugStatusCallback /local/domain/0/backend/vif/11/0/hotplug-status. [2007-01-14 04:22:05 xend] DEBUG (DevController:417) hotplugStatusCallback 2. [2007-01-14 04:22:05 xend.XendDomainInfo] DEBUG (XendDomainInfo:1356) XendDomainInfo.destroy: domid=11 [2007-01-14 04:22:05 xend.XendDomainInfo] DEBUG (XendDomainInfo:1364) XendDomainInfo.destroyDomain(11)

Excerpt from /var/log/messages:
Jan 14 04:22:04 Altair logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/11/770
Jan 14 04:22:04 Altair ifup:     vif11.0
Jan 14 04:22:04 Altair ifup: No configuration found for vif11.0 Jan 14 04:22:05 Altair logger: /etc/xen/scripts/vif-route: online XENBUS_PATH=backend/vif/11/0 Jan 14 04:22:05 Altair logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/11/769 Jan 14 04:22:05 Altair logger: /etc/xen/scripts/block: Writing backend/vbd/11/770/node /dev/loop0 to xenstore. Jan 14 04:22:05 Altair logger: /etc/xen/scripts/block: Writing backend/vbd/11/770/physical-device 7:0 to xenstore. Jan 14 04:22:05 Altair logger: /etc/xen/scripts/vif-route: Writing backend/vif/11/0/hotplug-status error to xenstore. Jan 14 04:22:05 Altair logger: /etc/xen/scripts/block: Writing backend/vbd/11/770/hotplug-status connected to xenstore.
Jan 14 04:22:05 Altair logger: /etc/xen/scripts/vif-route:
Jan 14 04:22:05 Altair logger: /etc/xen/scripts/block: Writing backend/vbd/11/769/node /dev/loop1 to xenstore. Jan 14 04:22:05 Altair logger: /etc/xen/scripts/vif-route: Writing backend/vif/11/0/hotplug-status error to xenstore. Jan 14 04:22:05 Altair logger: /etc/xen/scripts/block: Writing backend/vbd/11/769/physical-device 7:1 to xenstore. Jan 14 04:22:05 Altair logger: /etc/xen/scripts/vif-route: /etc/xen/scripts/vif-route failed; error detected. Jan 14 04:22:05 Altair logger: /etc/xen/scripts/vif-route: offline XENBUS_PATH=backend/vif/11/0 Jan 14 04:22:05 Altair logger: /etc/xen/scripts/block: Writing backend/vbd/11/769/hotplug-status connected to xenstore. Jan 14 04:22:05 Altair logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/11/770
Jan 14 04:22:05 Altair ifdown:     vif11.0
Jan 14 04:22:05 Altair ifdown: Interface not available and no configuration found. Jan 14 04:22:06 Altair logger: /etc/xen/scripts/vif-route: Writing backend/vif/11/0/hotplug-status error to xenstore. Jan 14 04:22:06 Altair logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/11/769 Jan 14 04:22:06 Altair logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/11/770
Jan 14 04:22:06 Altair logger: /etc/xen/scripts/vif-route:
Jan 14 04:22:06 Altair logger: /etc/xen/scripts/vif-route: Writing backend/vif/11/0/hotplug-status error to xenstore. Jan 14 04:22:06 Altair logger: /etc/xen/scripts/vif-route: /etc/xen/scripts/vif-route failed; error detected. Jan 14 04:22:06 Altair logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vif/11/0 Jan 14 04:22:06 Altair logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/11/769

As mentioned, brige setup with NAT works fine on the box with same domU.
Any help is very appreciated

Greetz
Timo

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

<Prev in Thread] Current Thread [Next in Thread>