[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Hotplug scripts not working

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.

When I run my code separately it runs ok, write_dev "$dev" returns the correct 
path. The Xen scripts should be able to go from there but they don't.
Last resort I've even created a minimalistic, hard coded block script 
containing this:

> case $t in
>        debug)
>            write_dev /dev/md/blockdevice
>            exit 0
>        ;;

... which dies the same way. Not returning anything I'm echoing in the script 
nor returning anything from bash -x.

I'm still missing out on something but I just can't put my finger on it.

Kind regards,
Tom De Vylder

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.