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

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

SOLVED: Re: [Xen-users] Error: Device 0 (vif) could not be connected. Ba

from [Jens Nachtigall] [Permanent Link][Original]
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: SOLVED: Re: [Xen-users] Error: Device 0 (vif) could not be connected. Backend device not found.
From: Jens Nachtigall <nachtigall@xxxxxx>
Date: Sun, 18 Jun 2006 20:49:00 +0200
Delivery-date: Sun, 18 Jun 2006 11:51:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200606182029.30582.nachtigall@xxxxxx>
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>
References: <200606182029.30582.nachtigall@xxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.1 
I found this at http://julien.danjou.info/xen.html

Set up the bridge
=-=-=-=-=-=-=-=-=-=-=-=-
 By default the Debian Xen package does not modify your network configuration. 
You will have to add a bridge to your /etc/network/interfaces file.
auto br-xen
iface br-xen inet static
      address 192.168.12.25
      netmask 255.255.255.0
      gateway 192.168.12.1
      bridge_ports eth0
      # optional
      bridge_maxwait 0

Doing an "ifup br-xen" it I can boot my xen image. Strange seems to be a bug 
that this is not handled automatically by xen-tools.

Am Sonntag, 18. Juni 2006 20:29 schrieb Jens Nachtigall:
> Hi all,
>
> I setup Xen3 for the first time using debian etch packages as described at
> http://www.debian-administration.org/articles/396 . That is I used the
> Debian xen-create-image to set up a Xen image.
>
> This all went fine, without errors (I can also mount and chroot into the
> image without problems). But when I run
>
> # xm create gerd.cfg -c
> Using config file "/etc/xen/gerd.cfg".
> Error: Device 0 (vif) could not be connected. Backend device not found.
>
>
> I do not know what causes this. After some fiddling and searching it
> seems to me like a problem in /etc/xen/scripts/vif-bridge
> But I miss the knowhow to tell what exactly goes wrong.
>
> Here is the from daemon.log when I run "xm create gerd.cfg -c" :
>
> /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/4/2049
> /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/4/2050
> /etc/xen/scripts/vif-bridge: online XENBUS_PATH=backend/vif/4/0
> /etc/xen/scripts/vif-bridge: Writing backend/vif/4/0/hotplug-status error
> to xenstore. /etc/xen/scripts/vif-bridge: Could not find bridge, and none
> was specified /etc/xen/scripts/vif-bridge: offline
> XENBUS_PATH=backend/vif/4/0
> /etc/xen/scripts/vif-bridge: Writing backend/vif/4/0/hotplug-status error
> to xenstore. /etc/xen/scripts/vif-bridge: Could not find bridge, and none
> was specified /etc/xen/scripts/xen-hotplug-cleanup:
> XENBUS_PATH=backend/vif/4/0
> /etc/xen/scripts/block: Writing backend/vbd/4/2049/node /dev/loop1 to
> xenstore. /etc/xen/scripts/block: Writing
> backend/vbd/4/2049/physical-device 7:1 to xenstore. /etc/xen/scripts/block:
> Writing backend/vbd/4/2049/hotplug-status connected to xenstore.
> /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/4/2049
> /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/4/2049
> /etc/xen/scripts/block: Writing backend/vbd/4/2050/node /dev/loop1 to
> xenstore. /etc/xen/scripts/block: Writing
> backend/vbd/4/2050/physical-device 7:1 to xenstore. /etc/xen/scripts/block:
> Writing backend/vbd/4/2050/hotplug-status connected to xenstore.
> /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/4/2050
> /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/4/2050
>
> Here is what xend.log says when I run "xm create gerd.cfg -c" :
>
> [2006-06-18 20:25:39 xend.XendDomainInfo] DEBUG (XendDomainInfo:178)
> XendDomainInfo.create(['vm', ['name', 'gerd'], ['memory', 196], ['vcpus',
> 1], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.16-2-xen-686'],
> ['ramdisk', '/boot/initrd.img-2.6.16-2-xen-686'], ['root', '/dev/sda1
> ro']]], ['device', ['vbd', ['uname',
> 'file:/home/xen/domains/gerd/disk.img'], ['dev', 'sda1'], ['mode', 'w']]],
> ['device', ['vbd', ['uname', 'file:/home/xen/domains/gerd/swap.img'],
> ['dev', 'sda2'], ['mode', 'w']]], ['device', ['vif', ['ip',
> '192.168.10.70']]]]) [2006-06-18 20:25:39 xend.XendDomainInfo] DEBUG
> (XendDomainInfo:284) parseConfig: config is ['vm', ['name', 'gerd'],
> ['memory', 196], ['vcpus', 1], ['image', ['linux', ['kernel',
> '/boot/vmlinuz-2.6.16-2-xen-686'], ['ramdisk',
> '/boot/initrd.img-2.6.16-2-xen-686'], ['root', '/dev/sda1 ro']]],
> ['device', ['vbd', ['uname', 'file:/home/xen/domains/gerd/disk.img'],
> ['dev', 'sda1'], ['mode', 'w']]], ['device', ['vbd', ['uname',
> 'file:/home/xen/domains/gerd/swap.img'], ['dev', 'sda2'], ['mode', 'w']]],
> ['device', ['vif', ['ip', '192.168.10.70']]]] [2006-06-18 20:25:39
> xend.XendDomainInfo] DEBUG (XendDomainInfo:380) parseConfig: result is
> {'ssidref': None, 'uuid': None, 'on_crash': None, 'on_reboot': None,
> 'image': ['linux', ['kernel', '/boot/vmlinuz-2.6.16-2-xen-686'],
> ['ramdisk', '/boot/initrd.img-2.6.16-2-xen-686'], ['root', '/dev/sda1
> ro']], 'on_poweroff': None, 'cpus': None, 'name': 'gerd', 'backend': [],
> 'vcpus': 1, 'cpu_weight': None, 'vcpu_avail': None, 'memory': 196,
> 'device': [('vbd', ['vbd', ['uname',
> 'file:/home/xen/domains/gerd/disk.img'], ['dev', 'sda1'], ['mode', 'w']]),
> ('vbd', ['vbd', ['uname', 'file:/home/xen/domains/gerd/swap.img'], ['dev',
> 'sda2'], ['mode', 'w']]), ('vif', ['vif', ['ip', '192.168.10.70']])],
> 'bootloader': None, 'cpu': None, 'maxmem': None} [2006-06-18 20:25:39
> xend.XendDomainInfo] DEBUG (XendDomainInfo:1164) XendDomainInfo.construct:
> None 0 [2006-06-18 20:25:39 xend.XendDomainInfo] DEBUG
> (XendDomainInfo:1196) XendDomainInfo.initDomain: 5 1.0 [2006-06-18 20:25:39
> xend] DEBUG (balloon:126) Balloon: free 197; need 197; done. [2006-06-18
> 20:25:39 xend] INFO (image:135) buildDomain os=linux dom=5 vcpus=1
> [2006-06-18 20:25:39 xend] DEBUG (image:173) dom            = 5
> [2006-06-18 20:25:39 xend] DEBUG (image:174) image          =
> /boot/vmlinuz-2.6.16-2-xen-686 [2006-06-18 20:25:39 xend] DEBUG (image:175)
> store_evtchn   = 1
> [2006-06-18 20:25:39 xend] DEBUG (image:176) console_evtchn = 2
> [2006-06-18 20:25:39 xend] DEBUG (image:177) cmdline        = 
> root=/dev/sda1 ro [2006-06-18 20:25:39 xend] DEBUG (image:178) ramdisk     
>   = /boot/initrd.img-2.6.16-2-xen-686 [2006-06-18 20:25:39 xend] DEBUG
> (image:179) vcpus          = 1
> [2006-06-18 20:25:39 xend] DEBUG (image:180) features       =
> [2006-06-18 20:25:39 xend] DEBUG (blkif:24) exception looking up device
> number for sda1: [Errno 2] No such file or directory: '/dev/sda1'
> [2006-06-18 20:25:39 xend] DEBUG (DevController:103) DevController: writing
> {'virtual-device': '2049', 'backend-id': '0', 'state': '1', 'backend':
> '/local/domain/0/backend/vbd/5/2049'} to /local/domain/5/device/vbd/2049.
> [2006-06-18 20:25:39 xend] DEBUG (DevController:105) DevController: writing
> {'domain': 'gerd', 'frontend': '/local/domain/5/device/vbd/2049', 'dev':
> 'sda1', 'state': '1', 'params': '/home/xen/domains/gerd/disk.img', 'mode':
> 'w', 'frontend-id': '5', 'type': 'file'} to
> /local/domain/0/backend/vbd/5/2049. [2006-06-18 20:25:39 xend] DEBUG
> (blkif:24) exception looking up device number for sda2: [Errno 2] No such
> file or directory: '/dev/sda2' [2006-06-18 20:25:39 xend] DEBUG
> (DevController:103) DevController: writing {'virtual-device': '2050',
> 'backend-id': '0', 'state': '1', 'backend':
> '/local/domain/0/backend/vbd/5/2050'} to /local/domain/5/device/vbd/2050.
> [2006-06-18 20:25:39 xend] DEBUG (DevController:105) DevController: writing
> {'domain': 'gerd', 'frontend': '/local/domain/5/device/vbd/2050', 'dev':
> 'sda2', 'state': '1', 'params': '/home/xen/domains/gerd/swap.img', 'mode':
> 'w', 'frontend-id': '5', 'type': 'file'} to
> /local/domain/0/backend/vbd/5/2050. [2006-06-18 20:25:39 xend] DEBUG
> (DevController:103) DevController: writing {'backend-id': '0', 'mac':
> '00:16:3e:1d:35:5a', 'handle': '0', 'state': '1', 'backend':
> '/local/domain/0/backend/vif/5/0'} to /local/domain/5/device/vif/0.
> [2006-06-18 20:25:39 xend] DEBUG (DevController:105) DevController: writing
> {'domain': 'gerd', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge',
> 'ip': '192.168.10.70', 'state': '1', 'frontend':
> '/local/domain/5/device/vif/0', 'mac': '00:16:3e:1d:35:5a', 'frontend-id':
> '5'} to /local/domain/0/backend/vif/5/0. [2006-06-18 20:25:39
> xend.XendDomainInfo] DEBUG (XendDomainInfo:671) Storing VM details:
> {'ssidref': '0', 'uuid': '324c5b66-049e-b6c0-28d7-35a3b4a94817',
> 'on_reboot': 'restart', 'start_time': '1150655139.67', 'on_poweroff':
> 'destroy', 'name': 'gerd', 'vcpus': '1', 'vcpu_avail': '1', 'memory':
> '196', 'on_crash': 'restart', 'image': "(linux (kernel
> /boot/vmlinuz-2.6.16-2-xen-686) (ramdisk /boot/initrd.img-2.6.16-2-xen-686)
> (root '/dev/sda1 ro'))", 'maxmem': '196'} [2006-06-18 20:25:39
> xend.XendDomainInfo] DEBUG (XendDomainInfo:696) Storing domain details:
> {'console/ring-ref': '197261', 'console/port': '2', 'name': 'gerd',
> 'console/limit': '1048576', 'vm':
> '/vm/324c5b66-049e-b6c0-28d7-35a3b4a94817', 'domid': '5',
> 'cpu/0/availability': 'online', 'memory/target': '200704',
> 'store/ring-ref': '197262', 'store/port': '1'} [2006-06-18 20:25:39
> xend.XendDomainInfo] DEBUG (XendDomainInfo:877)
> XendDomainInfo.handleShutdownWatch [2006-06-18 20:25:39 xend] DEBUG
> (DevController:132) Waiting for devices vif. [2006-06-18 20:25:39 xend]
> DEBUG (DevController:138) Waiting for 0. [2006-06-18 20:25:39 xend] DEBUG
> (DevController:403) hotplugStatusCallback
> /local/domain/0/backend/vif/5/0/hotplug-status. [2006-06-18 20:25:39 xend]
> DEBUG (DevController:403) hotplugStatusCallback
> /local/domain/0/backend/vif/5/0/hotplug-status. [2006-06-18 20:25:39 xend]
> DEBUG (DevController:417) hotplugStatusCallback 2. [2006-06-18 20:25:39
> xend.XendDomainInfo] DEBUG (XendDomainInfo:1327) XendDomainInfo.destroy:
> domid=5 [2006-06-18 20:25:39 xend.XendDomainInfo] DEBUG
> (XendDomainInfo:1335) XendDomainInfo.destroyDomain(5)
>
>
> Sorry, but that is a bit too much for a Xen beginner ;-) Your help is very
> much appreciated.
>
> Jens
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

-- 
     jabber-chat: nachtigall@xxxxxxxxxxx


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Xen-users] Error: Device 0 (vif) could not be connected. Backend device not found., Jens Nachtigall
Next by Date:  Re: [Xen-users] Xen running Windows, Jonathan Ervine
Previous by Thread:  [Xen-users] Error: Device 0 (vif) could not be connected. Backend device not found., Jens Nachtigall
Next by Thread:  Re: [Xen-users] Error: Device 0 (vif) could not be connected. Backend device not found., pak333
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy