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

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

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

from [pak333] [Permanent Link][Original]
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: [Xen-users] Error: Device 0 (vif) could not be connected. Backend device not found.
From: pak333@xxxxxxxxxxx
Date: Mon, 19 Jun 2006 06:06:48 +0000
Delivery-date: Sun, 18 Jun 2006 23:07:18 -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
 
I am having the same problem, however on RHEL 2.6.16.
I have tried setting up the bridge manually but it does not work.
Can someone give some clues on what we should do to solve this problem in RHEL
 
Thanks
P. Krishna
-------------- Original message --------------
From: Jens Nachtigall <nachtigall@xxxxxx>

> 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 X en3 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
& gt; > /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/hotplu g-stat us 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/vml inuz-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/s wap.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} [20 06-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/d evice/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
> & gt; xend.Xen dDomainInfo] 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/hotp lug-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.xensourc e.com/xen-users
--- Begin Message ---
To: Jens Nachtigall <nachtigall@xxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Error: Device 0 (vif) could not be connected. Backend device not found.
From: pak333@xxxxxxxxxxx
Date: Mon, 19 Jun 2006 04:30:34 +0000 
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

--- End Message ---
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Re: [Xen-users] Error: Device 0 (vif) could not be connected. Backend device not found., pak333 <=
Previous by Date:  [Xen-users] OOM killer problem, Satoshi Uchida
Next by Date:  [Xen-devel] Xen BVT scheduler, Apparao, Padmashree K
Previous by Thread:  [Xen-users] OOM killer problem, Satoshi Uchida
Next by Thread:  [Xen-devel] Xen BVT scheduler, Apparao, Padmashree K
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

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