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

Re: [Xen-users] Hotplug scripts not working


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: agent 8131 <agent.8131@xxxxxxxxxxxx>
  • Date: Wed, 01 Jun 2011 12:36:08 -0700
  • Delivery-date: Wed, 01 Jun 2011 12:38:44 -0700
  • Domainkey-signature: a=rsa-sha1; c=simple; d=infotage.net; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=WsO p7EGkcimGtfjGmg/4TShi/V92IyXRzgJSjKUq6z7v/jG7JXJYfLd4JVeTnsmpJ+r ctnKLc2c6O59tdCtmmKCRzKvVDI00JIWU+g8j/j6OvutHSfmpsT+64/poxtSxn45 gMfftCfvpCOnOQpBpxPrBmwnqTcTKW7RgKNBahB0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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@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


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


 


Rackspace

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