xen_blk timeout, hotplug

xen_blk timeout, hotplug

[Ryan Grimm]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 324 bytes --]

Hi,

With changeset 7237:76a7a7aa27e4, it appears as though something screwy is 
happening with the hotplug script upon domain creation.  default.hotplug 
is invoking xen-backend.agent a few times, before it times out.

Can someone with some knowledge of the script shed some light on what 
could be happening?

Thanks,
Ryan

[-- Attachment #2: debug info from /etc/hotplug.d/default/default.hotplug --]
[-- Type: TEXT/PLAIN, Size: 2188 bytes --]

Oct  6 16:22:31 localhost default.hotplug[8114]: arguments (xen-backend) env (SUBSYSTEM=xen-backend OLDPWD=/ XENBUS_TYPE=vif DEVPATH=/devices/xen-backend/vif-7-1 PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=add PWD=/etc/hotplug XENBUS_PATH=backend/vif/7/1 HOME=/ SHLVL=2 DEBUG=yes PHYSDEVBUS=xen-backend SEQNUM=994 _=/usr/bin/env)
Oct  6 16:22:31 localhost default.hotplug[8114]: invoke /etc/hotplug/xen-backend.agent ()
Oct  6 16:22:31 localhost default.hotplug[8126]: arguments (net) env (SUBSYSTEM=net OLDPWD=/ DEVPATH=/class/net/vif7.1 PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=add PWD=/etc/hotplug HOME=/ SHLVL=2 INTERFACE=vif7.1 DEBUG=yes SEQNUM=995 _=/usr/bin/env)
Oct  6 16:22:31 localhost default.hotplug[8126]: invoke /etc/hotplug/net.agent ()
Oct  6 16:22:31 localhost net.agent[8126]: invoke ifrename for vif7.1
Oct  6 16:22:31 localhost net.ifup[8143]: Invoking ifup vif7.1=hotplug
Oct  6 16:22:31 localhost default.hotplug[8152]: arguments (xen-backend) env (SUBSYSTEM=xen-backend OLDPWD=/ XENBUS_TYPE=vif DEVPATH=/devices/xen-backend/vif-7-1 script=/etc/xen/scripts/vif-bridge vif=vif7.1 PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=online mac=aa:00:00:53:93:f6 PWD=/etc/hotplug domain=ttylinux bridge=xen-br0 XENBUS_PATH=backend/vif/7/1 HOME=/ SHLVL=2 PHYSDEVDRIVER=vif DEBUG=yes PHYSDEVBUS=xen-backend SEQNUM=996 _=/usr/bin/env)
Oct  6 16:22:31 localhost default.hotplug[8152]: invoke /etc/hotplug/xen-backend.agent ()
Oct  6 16:22:31 localhost kernel: device vif7.1 entered promiscuous mode
Oct  6 16:22:31 localhost kernel: xen-br0: port 8(vif7.1) entering learning state
Oct  6 16:22:31 localhost kernel: xen-br0: topology change detected, propagating
Oct  6 16:22:31 localhost kernel: xen-br0: port 8(vif7.1) entering forwarding state
Oct  6 16:22:31 localhost default.hotplug[8108]: arguments (xen-backend) env (SUBSYSTEM=xen-backend OLDPWD=/ XENBUS_TYPE=vbd DEVPATH=/devices/xen-backend/vbd-7-2051 PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=add PWD=/etc/hotplug XENBUS_PATH=backend/vbd/7/2051 HOME=/ SHLVL=2 DEBUG=yes PHYSDEVBUS=xen-backend SEQNUM=993 _=/usr/bin/env)
Oct  6 16:22:31 localhost default.hotplug[8108]: invoke /etc/hotplug/xen-backend.agent ()

[-- Attachment #3: domain creation log --]
[-- Type: TEXT/PLAIN, Size: 833 bytes --]

xen_blk: Initialising virtual block device driver
xen_blk: Timeout connecting to device!
xen_net: Initialising virtual ethernet driver.
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 256 buckets, 4Kbytes
TCP established hash table entries: 4096 (order: 4, 65536 bytes)
TCP bind hash table entries: 4096 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "sda3" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)




[-- Attachment #4: Type: text/plain, Size: 138 bytes --]

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

Re: xen_blk timeout, hotplug

[Ryan Grimm]

I noticed that default.hotplug appears to invoke xen-backend.agent with no 
arguments ... the () below is blank

Oct  6 16:22:31 localhost default.hotplug[8114]: arguments (xen-backend) env (SUBSYSTEM=xen-backend OLDPWD=/ XENBUS_TYPE=vif DEVPATH=/devices/xen-backend/vif-7-1 PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=add PWD=/etc/hotplug XENBUS_PATH=backend/vif/7/1 HOME=/ SHLVL=2 DEBUG=yes PHYSDEVBUS=xen-backend SEQNUM=994 _=/usr/bin/env)
Oct  6 16:22:31 localhost default.hotplug[8114]: invoke /etc/hotplug/xen-backend.agent ()

Also, the xen-backend.agent script included in my dist directory comments 
out the following lines:

#! /bin/sh

#ACTION=add
#DEVPATH=/devices/xen-backend/vif-1-0
#PHYSDEVDRIVER=vif
#XENBUS_TYPE=vif

Is this the correct?

Ryan


On Thu, 6 Oct 2005, Ryan Grimm wrote:

> Hi,
>
> With changeset 7237:76a7a7aa27e4, it appears as though something screwy is 
> happening with the hotplug script upon domain creation.  default.hotplug is 
> invoking xen-backend.agent a few times, before it times out.
>
> Can someone with some knowledge of the script shed some light on what could 
> be happening?
>
> Thanks,
> Ryan

Re: xen_blk timeout, hotplug

[Jeremy Katz]

On Fri, 2005-10-07 at 09:58 -0500, Ryan Grimm wrote:
> I noticed that default.hotplug appears to invoke xen-backend.agent with no 
> arguments ... the () below is blank
[snip]
> Is this the correct?

This should be fine -- ACTION, XENBUS_TYPE, etc are all set as
environment variables for when hotplug is run

Jeremy

Re: xen_blk timeout, hotplug

[Keir Fraser]

On 7 Oct 2005, at 15:58, Ryan Grimm wrote:

> #ACTION=add
> #DEVPATH=/devices/xen-backend/vif-1-0
> #PHYSDEVDRIVER=vif
> #XENBUS_TYPE=vif
>
> Is this the correct?

Yes, arguments are passed to hotplug scripts in the environment rather 
than as positional parameters. Those commented-out lines are just a 
reference for the script writer of what interesting environment 
variables get passed up by the kernel.

  -- Keir