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

Re: [Xen-users] Hotplug scripts not working

To: Mark Pryor <tlviewer@xxxxxxxxx>
Subject: Re: [Xen-users] Hotplug scripts not working
From: Tom De Vylder <tom@xxxxxxxxxxx>
Date: Wed, 1 Jun 2011 11:05:56 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 01 Jun 2011 02:07:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <667987.18368.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <667987.18368.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 01 Jun 2011, at 03:19, Mark Pryor wrote:

> --- On Tue, 5/31/11, Tom De Vylder <tom@xxxxxxxxxxx> wrote:
> 
>> From: Tom De Vylder <tom@xxxxxxxxxxx>
>> Subject: [Xen-users] Hotplug scripts not working
>> To: xen-users@xxxxxxxxxxxxxxxxxxx
>> Date: Tuesday, May 31, 2011, 5:44 AM
>> Hi all,
>> 
>> I'd like to know if it's possible to have more verbose
>> output when running a block-prefix script. Other than
>> xend.log.
>> To be more specific I'd like to use bash -x to see why I'm
>> running into the following error:
>> 
>>> # xm create -c host.cfg
>>> Using config file "host.cfg".
>>> aa:bb:cc:dd:ee:ff
>>> Error: Device 51712 (vbd) could not be connected.
>> Hotplug scripts not working.
>> 
>> However xm seems to disregard any output from the
>> block-prefix script.
>> xend.log hangs a few minutes on the following lines:
>> 
>>> [2011-05-31 14:28:41 1894] DEBUG (XendDomainInfo:1286)
>> XendDomainInfo.destroyDevice: deviceClass = vbd, device =
>> vbd/51712
>>> [2011-05-31 14:28:41 1894] DEBUG (DevController:628)
>> hotplugStatusCallback
>> /local/domain/0/backend/vbd/55/51712/hotplug-status.
>>> [2011-05-31 14:28:41 1894] DEBUG (DevController:628)
>> hotplugStatusCallback
>> /local/domain/0/backend/vbd/55/51712/hotplug-status.
>> 
>> 
>> ... and then dies, removes the vif devices and spawns the
>> "hotplug scripts not working" errors.
>> 
> 
> Main reason for the above error on xen 4.0+ is missing the 1 or 2 drivers 
> from below:
> ls /dev/xen
>     evtchn
>     gntdev
> 
> If you built from source (please post `xm info`) the configs are
> 
> CONFIG_XEN_DEV_EVTCHN=y
> CONFIG_XEN_GNTDEV=y
> 
> also double check that below is populated
>   /proc/xen
> 
> if its not, there is no xenfs mount -- another common error.

Should be ok:

# ls -l /dev/xen
evtchn
gntdev

# lsmod | grep -i xen
xen_evtchn              4339  6 
xenfs                   9600  1

I've forgot to mention it's a clean debian 6 install with xen4 and already a 
few domU's running.



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

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