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>

Re: [Xen-users] newbie xen problens with vbd

from [Tim Post] [Permanent Link][Original]
To: JC Júnior <junior.listas@xxxxxxxxx>
Subject: Re: [Xen-users] newbie xen problens with vbd
From: Tim Post <tim.post@xxxxxxxxxxxxxxx>
Date: Tue, 20 Feb 2007 14:00:02 +0800
Cc: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 19 Feb 2007 21:59:43 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45DA8AA5.4030702@xxxxxxxxx>
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>
Organization: Net Kinetics
References: <45DA8AA5.4030702@xxxxxxxxx>
Reply-to: tim.post@xxxxxxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
Make sure the symbolic link "/bin/sh" points to bash, not dash.

ln -s -f /bin/bash /bin/sh will  most likely cure your problem.

Dash is not 'smart' enough to handle the abbreviated (advanced) code in
the hotplug scripts. It's rather sparse when it comes to built in regex
like you would find in bash.

Moreover, both shells change depending on their invocation, so the 'sh'
call from the hotplug scripts really should be left in tact. 

Best,
--Tim

On Tue, 2007-02-20 at 02:44 -0300, JC Júnior wrote:
> hi all; first of all, sorry for long message...
> 
>     I'm new in xen and using debian sarge as dom0 with xen 3.0.3  ( 
> 3.0.4 does not work perfectly ), everything works nice ( make world, 
> make install ),  I created successfully one debian sarge domU ( like 
> howtoforge howto ), an set a config file:
> #----debian_base-----------------------------------
> kernel = "/boot/vmlinuz-2.6-xen"
> name = "debianbase"
> memory = 64
> cpu=0
> disk = [ "file:/vserver/debian.base/debian.base.img,sda2,w" ]
> root = "/dev/sda2 ro"
> vif = [ '' ]  #its only for test
> #--------------------------------------------------------------
> 
> and when i type:  xm create -c debian_base shows:
> 
> Using config file "debian_base".
> Error: Device 2050 (vbd) could not be connected. Backend device not found.
> 
> After this, the domU stops...
> I have a look in log files and  I did not find nothing that made very 
> sensible for me, but here go some snippets:
> 
> # /var/log/messages
> Feb 20 02:33:49 localhost kernel: device vif9.0 entered promiscuous mode
> Feb 20 02:33:49 localhost kernel: ADDRCONF(NETDEV_UP): vif9.0: link is 
> not ready
> Feb 20 02:33:50 localhost kernel: xenbr0: port 3(vif9.0) entering 
> disabled state
> Feb 20 02:33:50 localhost kernel: device vif9.0 left promiscuous mode
> Feb 20 02:33:50 localhost kernel: xenbr0: port 3(vif9.0) entering 
> disabled state
> 
> #/var/log/syslog
> Feb 20 02:33:49 localhost kernel: device vif9.0 entered promiscuous mode
> Feb 20 02:33:49 localhost kernel: ADDRCONF(NETDEV_UP): vif9.0: link is 
> not ready
> Feb 20 02:33:49 localhost logger: /etc/xen/scripts/vif-bridge: 
> Successful vif-bridge online for vif9.0, bridge xenbr0.
> Feb 20 02:33:49 localhost logger: /etc/xen/scripts/vif-bridge: Writing 
> backend/vif/9/0/hotplug-status connected to xenstore.
> Feb 20 02:33:50 localhost logger: /etc/xen/scripts/block: add 
> XENBUS_PATH=backend/vbd/9/2050
> Feb 20 02:33:50 localhost logger: /etc/xen/scripts/block: Writing 
> backend/vbd/9/2050/hotplug-status error to xenstore.
> Feb 20 02:33:50 localhost logger: /etc/xen/scripts/block: 
> /vserver/debian.base/debian.base.img does not exist.
> Feb 20 02:33:50 localhost kernel: xenbr0: port 3(vif9.0) entering 
> disabled state
> Feb 20 02:33:50 localhost kernel: device vif9.0 left promiscuous mode
> Feb 20 02:33:50 localhost kernel: xenbr0: port 3(vif9.0) entering 
> disabled state
> Feb 20 02:33:50 localhost logger: /etc/xen/scripts/vif-bridge: offline 
> XENBUS_PATH=backend/vif/9/0
> Feb 20 02:33:50 localhost logger: /etc/xen/scripts/vif-bridge: brctl 
> delif xenbr0 vif9.0 failed
> Feb 20 02:33:50 localhost logger: /etc/xen/scripts/vif-bridge: ifconfig 
> vif9.0 down failed
> Feb 20 02:33:50 localhost logger: /etc/xen/scripts/vif-bridge: 
> Successful vif-bridge offline for vif9.0, bridge xenbr0.
> Feb 20 02:33:50 localhost logger: /etc/xen/scripts/xen-hotplug-cleanup: 
> XENBUS_PATH=backend/vif/9/0
> Feb 20 02:33:50 localhost logger: /etc/xen/scripts/block: remove 
> XENBUS_PATH=backend/vbd/9/2050
> Feb 20 02:33:50 localhost logger: /etc/xen/scripts/block: Writing 
> backend/vbd/9/2050/hotplug-status error to xenstore.
> Feb 20 02:33:50 localhost logger: /etc/xen/scripts/block: xenstore-read 
> backend/vbd/9/2050/node failed.
> Feb 20 02:33:50 localhost logger: /etc/xen/scripts/block: Writing 
> backend/vbd/9/2050/hotplug-status error to xenstore.
> Feb 20 02:33:50 localhost logger: /etc/xen/scripts/block: 
> /etc/xen/scripts/block failed; error detected.
> Feb 20 02:33:50 localhost logger: /etc/xen/scripts/xen-hotplug-cleanup: 
> XENBUS_PATH=backend/vbd/9/2050
> 
> #/var/log/xen/xen-hotplug.log
> Nothing to flush.
> xenstore-read: couldn't read path backend/vbd/9/2050/node
> 
> #/var/log/xen/xend.log
> [2007-02-20 02:33:49 xend 7876] DEBUG (DevController:143) Waiting for 
> devices vif.
> [2007-02-20 02:33:49 xend 7876] DEBUG (DevController:149) Waiting for 0.
> [2007-02-20 02:33:49 xend 4572] DEBUG (DevController:464) 
> hotplugStatusCallback /local/domain/0/backend/vif/9/0/hotplug-status.
> [2007-02-20 02:33:49 xend 4572] DEBUG (DevController:464) 
> hotplugStatusCallback /local/domain/0/backend/vif/9/0/hotplug-status.
> [2007-02-20 02:33:49 xend 4572] DEBUG (DevController:478) 
> hotplugStatusCallback 1.
> [2007-02-20 02:33:50 xend 7876] DEBUG (DevController:143) Waiting for 
> devices usb.
> [2007-02-20 02:33:50 xend 7876] DEBUG (DevController:143) Waiting for 
> devices vbd.
> [2007-02-20 02:33:50 xend 7876] DEBUG (DevController:149) Waiting for 2050.
> [2007-02-20 02:33:50 xend 4572] DEBUG (DevController:464) 
> hotplugStatusCallback /local/domain/0/backend/vbd/9/2050/hotplug-status.
> [2007-02-20 02:33:50 xend 4572] DEBUG (DevController:464) 
> hotplugStatusCallback /local/domain/0/backend/v[2007-02-20 02:33:49 xend 
> 7876] DEBUG (DevController:143) Waiting for devices vif.
> [2007-02-20 02:33:49 xend 7876] DEBUG (DevController:149) Waiting for 0.
> [2007-02-20 02:33:49 xend 4572] DEBUG (DevController:464) 
> hotplugStatusCallback /local/domain/0/backend/vif/9/0/hotplug-status.
> [2007-02-20 02:33:49 xend 4572] DEBUG (DevController:464) 
> hotplugStatusCallback /local/domain/0/backend/vif/9/0/hotplug-status.
> [2007-02-20 02:33:49 xend 4572] DEBUG (DevController:478) 
> hotplugStatusCallback 1.
> [2007-02-20 02:33:50 xend 7876] DEBUG (DevController:143) Waiting for 
> devices usb.
> [2007-02-20 02:33:50 xend 7876] DEBUG (DevController:143) Waiting for 
> devices vbd.
> [2007-02-20 02:33:50 xend 7876] DEBUG (DevController:149) Waiting for 2050.
> [2007-02-20 02:33:50 xend 4572] DEBUG (DevController:464) 
> hotplugStatusCallback /local/domain/0/backend/vbd/9/2050/hotplug-status.
> [2007-02-20 02:33:50 xend 4572] DEBUG (DevController:464) 
> hotplugStatusCallback /local/domain/0/backend/vbd/9/2050/hotplug-status.
> [2007-02-20 02:33:50 xend 4572] DEBUG (DevController:478) 
> hotplugStatusCallback 2.
> [2007-02-20 02:33:50 xend.XendDomainInfo 8000] DEBUG 
> (XendDomainInfo:1449) XendDomainInfo.destroy: domid=9
> bd/9/2050/hotplug-status.
> [2007-02-20 02:33:50 xend 4572] DEBUG (DevController:478) 
> hotplugStatusCallback 2.
> [2007-02-20 02:33:50 xend.XendDomainInfo 8000] DEBUG 
> (XendDomainInfo:1449) XendDomainInfo.destroy: domid=9
> 
> #/var/log/xen/xend-debug.log
> 
> dont show anything ---
> 
> 
> I found lots information about on google, but nothing helped, somebody 
> can help me??
> 
> JC
> 
> 
> ps. sorry my bad english
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


_______________________________________________
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] newbie xen problens with vbd, JC Júnior
Next by Date:  Re: [Xen-users] domUdos not start, Tim Post
Previous by Thread:  [Xen-users] newbie xen problens with vbd, JC Júnior
Next by Thread:  Re: [Xen-users] newbie xen problens with vbd, John
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

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