RE: [Xen-devel] Hotplug scripts not working... xen/ia64 domU stoppedworking

["Dave Thompson \(davetho\)" <davetho@xxxxxxxxx>]

> -----Original Message-----
> From: Ewan Mellor [mailto:ewan@xxxxxxxxxxxxx] 
> Sent: Tuesday, December 06, 2005 5:25 AM
> To: Dave Thompson (davetho)
> Cc: Xen Mailing List
> Subject: Re: [Xen-devel] Hotplug scripts not working... 
> xen/ia64 domU stoppedworking
> 
> On Mon, Dec 05, 2005 at 03:03:54PM -0500, Dave Thompson 
> (davetho) wrote:
> 
> >  
> > 
> > > -----Original Message-----
> > > From: Ewan Mellor [mailto:ewan@xxxxxxxxxxxxx]
> > > Sent: Monday, December 05, 2005 12:12 PM
> > > To: Dave Thompson (davetho)
> > > Cc: Xen Mailing List
> > > Subject: Re: [Xen-devel] Hotplug scripts not working... 
> > > xen/ia64 domU stoppedworking
> > > 
> > > On Mon, Dec 05, 2005 at 11:59:58AM -0500, Dave Thompson
> > > (davetho) wrote:
> > > 
> > > > I believe I am hitting this same problem.  I am running 
> the latest 
> > > > from xen-3.0-testing.hg and get the same "Hotplug scripts
> > > not working"
> > > > message when I attempt to start a linux domU guest 
> domain.  I've 
> > > > attached some info in hopes that this might help in solving
> > > the problem.
> > > > If there is anything else I can provide, please let me know.
> > > 
> > > Could you put "set -x" at the top of 
> > > /etc/xen/scripts/xen-hotplug-common.sh
> > > and then send /var/log/xen-hotplug.log again?
> > 
> > Ok.  I re-ran with the "set -x" in the 
> xen-hotplug-common.sh script.  
> > I noticed this time I got a different error:
> > 
> > Error: Device 0 (vif) could not be connected. Hotplug scripts not 
> > working.
> > 
> > However, I've attached the resulting xen-hotplug.log.
> 
> The log you've sent is for a successful run of the scripts 
> setting up the vbd.  This is a little odd, because the Xend 
> log you sent showed the vif succeeding and the vbd failing, 
> so you've managed to have at least one successful run of 
> each.  Could you run it a few times, and see if it's 
> intermittent?

I tried it a few times more and was finally able to capture the vbd
failure.  So it does seem to be somewhat intermittent.  But it does
always seem to fail with either the vif or vbd.

> For each of the devices, vif and vbd, you 
> should see at least one line each of 
> 
> +++ logger -p daemon.debug -- /etc/xen/scripts/block: add 
> +++ XENBUS_PATH=backend/vbd/2/2049
> 
> in your xen-hotplug.log.  If you aren't seeing one each of 
> those then your hotplug system is failing before the scripts 
> even get a chance to run (or your drivers are failing).

In the case where the vif failed, I only see the add for the vbd in the
xen-hotplug.log,  there isn't an add of the vif.  However, in the case
where the vbd failed, I don't see the add line for either.  I've
attached the xen-hotplug.log for the vbd failure case.
 
> It would be good to confirm whether the hotplug events are even 
> getting through, so that we don't end up looking in 
> completely the wrong place.  Start with "cat 
> /proc/sys/kernel/hotplug".  If that's udevsend and udevinfo 
> -V reports greater than 059 then you are using udev, so use 
> udevmonitor to watch the udev events going past.

# cat /proc/sys/kernel/hotplug
/sbin/udevsend
# udevinfo -V
udevinfo, version 068

Here is the output from udevmonitor during the xm create when the vif
failed:

UEVENT[1133877953] add@/devices/xen-backend/vbd-4-2049
UEVENT[1133877953] add@/devices/xen-backend/vif-4-0
UEVENT[1133877953] add@/class/net/vif4.0
UEVENT[1133877953] online@/devices/xen-backend/vif-4-0
UDEV  [1133877956] add@/devices/xen-backend/vbd-4-2049

Here is the output when the vbd failed:

UEVENT[1133880108] add@/devices/xen-backend/vbd-5-2049
UEVENT[1133880108] add@/devices/xen-backend/vif-5-0
UEVENT[1133880108] add@/class/net/vif5.0
UEVENT[1133880108] online@/devices/xen-backend/vif-5-0
UDEV  [1133880111] add@/devices/xen-backend/vif-5-0
UDEV  [1133880111] online@/devices/xen-backend/vif-5-0
UDEV  [1133880116] add@/class/net/vif5.0

> You should see an "add" event for both vif and vbd, plus an
> "online" event for the vif.  Otherwise you are using hotplug, so put 
> 
> set -x
> exec 2>>/var/log/xen-hotplug.log
> 
> at the top of /sbin/hotplug (usually a script) and 
> /etc/hotplug/xen-backend.agent.

I didn't do this since I seem to be using udev.
 
> Cheers,
> 
> Ewan.
>

Attachment: xen-hotplug.log
Description: xen-hotplug.log

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