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 Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
--- On Tue, 5/31/11, Tom De Vylder <tom@penumbra.be> wrote:> From: Tom De Vylder <tom@penumbra.be> > Subject: [Xen-users] Hotplug scripts not working > To: xen-users@lists.xensource.com > 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. -- Mark _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 01 Jun 2011, at 03:19, Mark Pryor wrote:> --- On Tue, 5/31/11, Tom De Vylder <tom@penumbra.be> wrote: > >> From: Tom De Vylder <tom@penumbra.be> >> Subject: [Xen-users] Hotplug scripts not working >> To: xen-users@lists.xensource.com >> 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@lists.xensource.com http://lists.xensource.com/xen-users
This might help: http://hightechsorcery.com/2011/03/getting-xen-4-0-1-working-in-debian-6-0/ On 06/01/2011 02:05 AM, Tom De Vylder wrote:> On 01 Jun 2011, at 03:19, Mark Pryor wrote: > >> --- On Tue, 5/31/11, Tom De Vylder<tom@penumbra.be> wrote: >> >>> From: Tom De Vylder<tom@penumbra.be> >>> Subject: [Xen-users] Hotplug scripts not working >>> To: xen-users@lists.xensource.com >>> 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@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Seemingly Similar Threads
- Task blocked for more than 120 seconds.
- DRBD VBD script not working in squeeze ?
- Xen 4.0 - prerequisites for succesfull live migration?
- Custom block script started twice for root block but only stopped once
- Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1