All of lore.kernel.org
 help / color / mirror / Atom feed
* RE: Hotplug scripts not working... xen/ia64 domU stopped working
@ 2005-11-30 14:26 Petersson, Mats
  2005-12-01  0:26 ` Hotplug scripts not working... xen/ia64 domU?stopped working Horms
  0 siblings, 1 reply; 29+ messages in thread
From: Petersson, Mats @ 2005-11-30 14:26 UTC (permalink / raw)
  To: Magenheimer, Dan (HP Labs Fort Collins), Ewan Mellor; +Cc: Xen Mailing List

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com 
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
> Magenheimer, Dan (HP Labs Fort Collins)
> Sent: 30 November 2005 14:18
> To: Ewan Mellor
> Cc: Xen Mailing List
> Subject: RE: [Xen-devel] Hotplug scripts not working... 
> xen/ia64 domU stopped working
> 
> > On Tue, Nov 29, 2005 at 08:43:30PM -0800, Magenheimer, Dan (HP Labs 
> > Fort Collins) wrote:
> > 
> > > Somewhere between cset 8006 and cset 8112, the virtual 
> block device 
> > > stopped working for Xen/ia64.  With cset 8112, I get:
> > > 
> > > Error: Device 769 (vbd) could not be connected. Hotplug 
> scripts not 
> > > working.
> > > 
> > > Any suggestions where to start looking or will I need to 
> do a binary 
> > > search?
> > 
> > Please use xen-bugtool (new in the latest changesets) to 
> collect your 
> > logs so that I can take a look.
> 
> Hmmmm... it appears xen-bugtool is born at 8073.  I can go 
> back to that but have already reproduced the problem at 8054.
> 
> HOWEVER... I am now having problems at 8006 which worked 
> yesterday.  I suspect that there are some Xen tools/files 
> that are not getting replaced.  (And xen-bugtool doesn't work 
> there as one would expect... it is still in place because of 
> the previous install of 8112 but gives a python error.)
> 
> Is there a way to do a "make clean" on all Xen files outside 
> of the xen-unstable.hg directory to ensure no "old" (or in my case
> newer) files/scripts from /etc, /bin/ etc are being 
> accidentally used?  I know others have experienced this kind 
> of problem and have "fixed" it by reinstalling their distro 
> from scratch.
[snip]

I'd like to see a "uninstall.sh". I did for a short while consider
writing one myself. I know that most people aren't going to uninstall
Xen - it's such a lovely product that no one in their right mind would
uninstall it, right? - but particularly for us developers, it would be
nice to have something that removes ALL remains of the Xen installation.
I had severe problems because I tried to install 64-bit Xen on top of a
32-bit installation and all sorts of bits and pieces got very confused.

I think it could actually be constructed based on the install directory
with some scripting - I'm not that good at writing shell-scripts, or I
would volunteer to do it myself. [I hacked something up where I just
took the names of directories listed under the install directory and
removed all contents of those directories, but that's only going to work
as long as the files are kept in the same place each time. Yet, it's
quicker to do that than to run a complete re-install...]

--
Mats

^ permalink raw reply	[flat|nested] 29+ messages in thread
* RE: Hotplug scripts not working... xen/ia64 domU stopped working
@ 2005-12-03 20:31 Magenheimer, Dan (HP Labs Fort Collins)
  0 siblings, 0 replies; 29+ messages in thread
From: Magenheimer, Dan (HP Labs Fort Collins) @ 2005-12-03 20:31 UTC (permalink / raw)
  To: Ewan Mellor; +Cc: Xen Mailing List

[-- Attachment #1: Type: text/plain, Size: 406 bytes --]

Well, unfortunately, the recent hotplug fixes didn't fix my
problem.  In fact they made it worse; the w! and logging
workarounds no longer work so I can't boot a domU at all.
I always get the same "Hotplug scripts not working" message.

However, now with tip (8213), I can send you xen-bugtool output
so have attached that and log output from /sbin/hotplug.

Any help would be appreciated!

Dan

[-- Attachment #2: hotplugprob.tar.bz2 --]
[-- Type: application/octet-stream, Size: 14482 bytes --]

[-- Attachment #3: 8213.log --]
[-- Type: application/octet-stream, Size: 9361 bytes --]


+ cd /etc/hotplug
+ . hotplug.functions
+ cd /etc/hotplug
+ . hotplug.functions
++ PATH=/bin:/sbin:/usr/sbin:/usr/bin
+++ uname -r
++ KERNEL=2.6.12.6-xen0
++ MODULE_DIR=/lib/modules/2.6.12.6-xen0
++ HOTPLUG_DIR=/etc/hotplug
++ '[' -t -o '!' -x /usr/bin/logger ']'
+++ type -p gawk
++ AWK=/bin/gawk
++ '[' /bin/gawk = '' ']'
++ MODPROBE=/sbin/modprobe -s
+ '[' '' '!=' '' ']'
+ '[' 1 -lt 1 -o vc = help -o vc = --help ']'
+ AGENT=/etc/hotplug/vc.agent
+ '[' -x /etc/hotplug/vc.agent ']'
+ mesg 'no runnable /etc/hotplug/vc.agent is installed'
+ /usr/bin/logger -t /sbin/hotplug 'no runnable /etc/hotplug/vc.agent is installed'
++ PATH=/bin:/sbin:/usr/sbin:/usr/bin
+++ uname -r
++ KERNEL=2.6.12.6-xen0
++ MODULE_DIR=/lib/modules/2.6.12.6-xen0
++ HOTPLUG_DIR=/etc/hotplug
++ '[' -t -o '!' -x /usr/bin/logger ']'
+++ type -p gawk
++ AWK=/bin/gawk
++ '[' /bin/gawk = '' ']'
++ MODPROBE=/sbin/modprobe -s
+ '[' '' '!=' '' ']'
+ '[' 1 -lt 1 -o vc = help -o vc = --help ']'
+ AGENT=/etc/hotplug/vc.agent
+ '[' -x /etc/hotplug/vc.agent ']'
+ mesg 'no runnable /etc/hotplug/vc.agent is installed'
+ /usr/bin/logger -t /sbin/hotplug 'no runnable /etc/hotplug/vc.agent is installed'
+ cd /etc/hotplug
+ . hotplug.functions
++ PATH=/bin:/sbin:/usr/sbin:/usr/bin
+++ uname -r
++ KERNEL=2.6.12.6-xen0
++ MODULE_DIR=/lib/modules/2.6.12.6-xen0
++ HOTPLUG_DIR=/etc/hotplug
++ '[' -t -o '!' -x /usr/bin/logger ']'
+++ type -p gawk
++ AWK=/bin/gawk
++ '[' /bin/gawk = '' ']'
++ MODPROBE=/sbin/modprobe -s
+ '[' '' '!=' '' ']'
+ '[' 1 -lt 1 -o vc = help -o vc = --help ']'
+ AGENT=/etc/hotplug/vc.agent
+ '[' -x /etc/hotplug/vc.agent ']'
+ mesg 'no runnable /etc/hotplug/vc.agent is installed'
+ /usr/bin/logger -t /sbin/hotplug 'no runnable /etc/hotplug/vc.agent is installed'
+ cd /etc/hotplug
+ . hotplug.functions
++ PATH=/bin:/sbin:/usr/sbin:/usr/bin
+++ uname -r
++ KERNEL=2.6.12.6-xen0
++ MODULE_DIR=/lib/modules/2.6.12.6-xen0
++ HOTPLUG_DIR=/etc/hotplug
++ '[' -t -o '!' -x /usr/bin/logger ']'
+++ type -p gawk
++ AWK=/bin/gawk
++ '[' /bin/gawk = '' ']'
++ MODPROBE=/sbin/modprobe -s
+ '[' '' '!=' '' ']'
+ '[' 1 -lt 1 -o vc = help -o vc = --help ']'
+ AGENT=/etc/hotplug/vc.agent
+ '[' -x /etc/hotplug/vc.agent ']'
+ mesg 'no runnable /etc/hotplug/vc.agent is installed'
+ /usr/bin/logger -t /sbin/hotplug 'no runnable /etc/hotplug/vc.agent is installed'
+ exit 1
+ exit 1
+ cd /etc/hotplug
+ . hotplug.functions
++ PATH=/bin:/sbin:/usr/sbin:/usr/bin
+++ uname -r
++ KERNEL=2.6.12.6-xen0
++ MODULE_DIR=/lib/modules/2.6.12.6-xen0
++ HOTPLUG_DIR=/etc/hotplug
++ '[' -t -o '!' -x /usr/bin/logger ']'
+++ type -p gawk
++ AWK=/bin/gawk
++ '[' /bin/gawk = '' ']'
++ MODPROBE=/sbin/modprobe -s
+ '[' '' '!=' '' ']'
+ '[' 1 -lt 1 -o vc = help -o vc = --help ']'
+ AGENT=/etc/hotplug/vc.agent
+ '[' -x /etc/hotplug/vc.agent ']'
+ mesg 'no runnable /etc/hotplug/vc.agent is installed'
+ /usr/bin/logger -t /sbin/hotplug 'no runnable /etc/hotplug/vc.agent is installed'
+ cd /etc/hotplug
+ . hotplug.functions
++ PATH=/bin:/sbin:/usr/sbin:/usr/bin
+++ uname -r
++ KERNEL=2.6.12.6-xen0
++ MODULE_DIR=/lib/modules/2.6.12.6-xen0
++ HOTPLUG_DIR=/etc/hotplug
++ '[' -t -o '!' -x /usr/bin/logger ']'
+++ type -p gawk
++ AWK=/bin/gawk
++ '[' /bin/gawk = '' ']'
++ MODPROBE=/sbin/modprobe -s
+ '[' '' '!=' '' ']'
+ '[' 1 -lt 1 -o vc = help -o vc = --help ']'
+ AGENT=/etc/hotplug/vc.agent
+ '[' -x /etc/hotplug/vc.agent ']'
+ mesg 'no runnable /etc/hotplug/vc.agent is installed'
+ /usr/bin/logger -t /sbin/hotplug 'no runnable /etc/hotplug/vc.agent is installed'
+ cd /etc/hotplug
+ . hotplug.functions
++ PATH=/bin:/sbin:/usr/sbin:/usr/bin
+++ uname -r
++ KERNEL=2.6.12.6-xen0
++ MODULE_DIR=/lib/modules/2.6.12.6-xen0
++ HOTPLUG_DIR=/etc/hotplug
++ '[' -t -o '!' -x /usr/bin/logger ']'
+++ type -p gawk
++ AWK=/bin/gawk
++ '[' /bin/gawk = '' ']'
++ MODPROBE=/sbin/modprobe -s
+ '[' '' '!=' '' ']'
+ '[' 1 -lt 1 -o vc = help -o vc = --help ']'
+ AGENT=/etc/hotplug/vc.agent
+ '[' -x /etc/hotplug/vc.agent ']'
+ mesg 'no runnable /etc/hotplug/vc.agent is installed'
+ /usr/bin/logger -t /sbin/hotplug 'no runnable /etc/hotplug/vc.agent is installed'
+ cd /etc/hotplug
+ . hotplug.functions
++ PATH=/bin:/sbin:/usr/sbin:/usr/bin
+++ uname -r
++ KERNEL=2.6.12.6-xen0
++ MODULE_DIR=/lib/modules/2.6.12.6-xen0
++ HOTPLUG_DIR=/etc/hotplug
++ '[' -t -o '!' -x /usr/bin/logger ']'
+++ type -p gawk
++ AWK=/bin/gawk
++ '[' /bin/gawk = '' ']'
++ MODPROBE=/sbin/modprobe -s
+ '[' '' '!=' '' ']'
+ '[' 1 -lt 1 -o vc = help -o vc = --help ']'
+ AGENT=/etc/hotplug/vc.agent
+ '[' -x /etc/hotplug/vc.agent ']'
+ mesg 'no runnable /etc/hotplug/vc.agent is installed'
+ /usr/bin/logger -t /sbin/hotplug 'no runnable /etc/hotplug/vc.agent is installed'
+ cd /etc/hotplug
+ . hotplug.functions
++ PATH=/bin:/sbin:/usr/sbin:/usr/bin
+++ uname -r
++ KERNEL=2.6.12.6-xen0
++ MODULE_DIR=/lib/modules/2.6.12.6-xen0
++ HOTPLUG_DIR=/etc/hotplug
++ '[' -t -o '!' -x /usr/bin/logger ']'
+++ type -p gawk
++ AWK=/bin/gawk
++ '[' /bin/gawk = '' ']'
++ MODPROBE=/sbin/modprobe -s
+ '[' '' '!=' '' ']'
+ '[' 1 -lt 1 -o vc = help -o vc = --help ']'
+ AGENT=/etc/hotplug/vc.agent
+ '[' -x /etc/hotplug/vc.agent ']'
+ mesg 'no runnable /etc/hotplug/vc.agent is installed'
+ /usr/bin/logger -t /sbin/hotplug 'no runnable /etc/hotplug/vc.agent is installed'
+ cd /etc/hotplug
+ . hotplug.functions
++ PATH=/bin:/sbin:/usr/sbin:/usr/bin
+++ uname -r
++ KERNEL=2.6.12.6-xen0
++ MODULE_DIR=/lib/modules/2.6.12.6-xen0
++ HOTPLUG_DIR=/etc/hotplug
++ '[' -t -o '!' -x /usr/bin/logger ']'
+++ type -p gawk
++ AWK=/bin/gawk
++ '[' /bin/gawk = '' ']'
++ MODPROBE=/sbin/modprobe -s
+ '[' '' '!=' '' ']'
+ '[' 1 -lt 1 -o vc = help -o vc = --help ']'
+ AGENT=/etc/hotplug/vc.agent
+ '[' -x /etc/hotplug/vc.agent ']'
+ mesg 'no runnable /etc/hotplug/vc.agent is installed'
+ /usr/bin/logger -t /sbin/hotplug 'no runnable /etc/hotplug/vc.agent is installed'
+ exit 1
+ cd /etc/hotplug
+ . hotplug.functions
++ PATH=/bin:/sbin:/usr/sbin:/usr/bin
+++ uname -r
++ KERNEL=2.6.12.6-xen0
++ MODULE_DIR=/lib/modules/2.6.12.6-xen0
++ HOTPLUG_DIR=/etc/hotplug
++ '[' -t -o '!' -x /usr/bin/logger ']'
+++ type -p gawk
++ AWK=/bin/gawk
++ '[' /bin/gawk = '' ']'
++ MODPROBE=/sbin/modprobe -s
+ '[' '' '!=' '' ']'
+ '[' 1 -lt 1 -o vc = help -o vc = --help ']'
+ AGENT=/etc/hotplug/vc.agent
+ '[' -x /etc/hotplug/vc.agent ']'
+ mesg 'no runnable /etc/hotplug/vc.agent is installed'
+ /usr/bin/logger -t /sbin/hotplug 'no runnable /etc/hotplug/vc.agent is installed'
+ cd /etc/hotplug
+ . hotplug.functions
++ PATH=/bin:/sbin:/usr/sbin:/usr/bin
+++ uname -r
++ KERNEL=2.6.12.6-xen0
++ MODULE_DIR=/lib/modules/2.6.12.6-xen0
++ HOTPLUG_DIR=/etc/hotplug
++ '[' -t -o '!' -x /usr/bin/logger ']'
+++ type -p gawk
++ AWK=/bin/gawk
++ '[' /bin/gawk = '' ']'
++ MODPROBE=/sbin/modprobe -s
+ '[' '' '!=' '' ']'
+ '[' 1 -lt 1 -o vc = help -o vc = --help ']'
+ AGENT=/etc/hotplug/vc.agent
+ '[' -x /etc/hotplug/vc.agent ']'
+ mesg 'no runnable /etc/hotplug/vc.agent is installed'
+ /usr/bin/logger -t /sbin/hotplug 'no runnable /etc/hotplug/vc.agent is installed'
+ exit 1
+ exit 1
+ exit 1
+ exit 1
+ exit 1
+ exit 1
+ exit 1
+ exit 1
+ exit 1
+ cd /etc/hotplug
+ . hotplug.functions
++ PATH=/bin:/sbin:/usr/sbin:/usr/bin
+++ uname -r
++ KERNEL=2.6.12.6-xen0
++ MODULE_DIR=/lib/modules/2.6.12.6-xen0
++ HOTPLUG_DIR=/etc/hotplug
++ '[' -t -o '!' -x /usr/bin/logger ']'
+++ type -p gawk
++ AWK=/bin/gawk
++ '[' /bin/gawk = '' ']'
++ MODPROBE=/sbin/modprobe -s
+ '[' '' '!=' '' ']'
+ '[' 1 -lt 1 -o xen-backend = help -o xen-backend = --help ']'
+ AGENT=/etc/hotplug/xen-backend.agent
+ '[' -x /etc/hotplug/xen-backend.agent ']'
+ shift
+ '[' '' '!=' '' ']'
+ exec /etc/hotplug/xen-backend.agent
+ PATH=/etc/xen/scripts:/bin:/sbin:/usr/sbin:/usr/bin
+ /etc/xen/scripts/block add
++ dirname /etc/xen/scripts/block
+ dir=/etc/xen/scripts
+ . /etc/xen/scripts/block-common.sh
+++ dirname /etc/xen/scripts/block
++ dir=/etc/xen/scripts
++ . /etc/xen/scripts/xen-hotplug-common.sh
++++ dirname /etc/xen/scripts/block
+++ dir=/etc/xen/scripts
+++ . /etc/xen/scripts/xen-script-common.sh
++++ set -e
+++ exec
+ cd /etc/hotplug
+ . hotplug.functions
++ PATH=/bin:/sbin:/usr/sbin:/usr/bin
+++ uname -r
++ KERNEL=2.6.12.6-xen0
++ MODULE_DIR=/lib/modules/2.6.12.6-xen0
++ HOTPLUG_DIR=/etc/hotplug
++ '[' -t -o '!' -x /usr/bin/logger ']'
+++ type -p gawk
++ AWK=/bin/gawk
++ '[' /bin/gawk = '' ']'
++ MODPROBE=/sbin/modprobe -s
+ '[' '' '!=' '' ']'
+ '[' 1 -lt 1 -o xen-backend = help -o xen-backend = --help ']'
+ AGENT=/etc/hotplug/xen-backend.agent
+ '[' -x /etc/hotplug/xen-backend.agent ']'
+ shift
+ '[' '' '!=' '' ']'
+ exec /etc/hotplug/xen-backend.agent
+ PATH=/etc/xen/scripts:/bin:/sbin:/usr/sbin:/usr/bin
+ /etc/xen/scripts/block remove
++ dirname /etc/xen/scripts/block
+ dir=/etc/xen/scripts
+ . /etc/xen/scripts/block-common.sh
+++ dirname /etc/xen/scripts/block
++ dir=/etc/xen/scripts
++ . /etc/xen/scripts/xen-hotplug-common.sh
++++ dirname /etc/xen/scripts/block
+++ dir=/etc/xen/scripts
+++ . /etc/xen/scripts/xen-script-common.sh
++++ set -e
+++ exec
++ xenstore-read backend/vbd/1/769/frontend
+ xenstore-rm -t /local/domain/1/device/vbd/769
xenstore-rm: could not remove path /local/domain/1/device/vbd/769
+ true
+ xenstore-rm -t backend/vbd/1/769
+ xenstore-rm -t error/backend/vbd/1/769
xenstore-rm: could not remove path error/backend/vbd/1/769
+ true

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

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

^ permalink raw reply	[flat|nested] 29+ messages in thread
* RE: Hotplug scripts not working... xen/ia64 domU stopped working
@ 2005-12-02 20:40 Magenheimer, Dan (HP Labs Fort Collins)
  2005-12-02 21:22 ` David F Barrera
  0 siblings, 1 reply; 29+ messages in thread
From: Magenheimer, Dan (HP Labs Fort Collins) @ 2005-12-02 20:40 UTC (permalink / raw)
  To: Ewan Mellor; +Cc: Xen Mailing List

> Anyway, I'd be inclined to try the new changesets (not yet 
> pushed to the public
> tree) and see if that improves things. 

Same problem and same workaround on tip (8169).  Please
email when your new changesets get pushed and I will
try them.

> > My /etc/xen/xmdefconfig is very short:
> > kernel = "/tmp/xenlinux"
> > memory = 256
> > nics=0
> > disk = ['phy:loop0,hda1,w']  # <-change to w!
> > 
> > and after a fresh boot, I am simply doing:
> > 
> > # lomount -t ext2 -diskimage /var/xen/hda /mnt
> > # xend start
> > # xm create
> > 
> > I can see how it could be interpreted that loop0 is
> > being used both by domain0 and the newly created domain,
> > but isn't this a common use model?
> 
> Only if you want to corrupt your filesystem!  Writing to that 
> file via /mnt
> in dom0 and via /dev/hda1 in the guest ought to corrupt your 
> fs nicely.

Not as long as the image is only used from domU, correct?

What is the proper use model?  As I noted previously,
disk = ['file:/var/xen/hda,hda1,w'] results in a Linux
error message ("UDF-fs: No VRS found"... and, no, I do
not have any CD's in /etc/fstab!).  Am I spelling
this xmdefconfig entry incorrectly?  Or is there
a better way to use a disk-in-a-file as root disk for
a guest domain?

Thanks,
Dan

^ permalink raw reply	[flat|nested] 29+ messages in thread
* RE: Hotplug scripts not working... xen/ia64 domU stopped working
@ 2005-12-02 17:41 Magenheimer, Dan (HP Labs Fort Collins)
  2005-12-02 20:17 ` Ewan Mellor
  0 siblings, 1 reply; 29+ messages in thread
From: Magenheimer, Dan (HP Labs Fort Collins) @ 2005-12-02 17:41 UTC (permalink / raw)
  To: Ewan Mellor; +Cc: Xen Mailing List

Problem identified but it's a weird one!  I turned on logging
in /etc/xen/scripts/block and /etc/hotplug/xen-backend.agent
using Adam's cool trick of redirecting stderr output (exec 2>>file),
and discovered I *was* getting a message that domain0 already
was using the loopback device.

So I again tried turning on w! in /etc/xen/xmdefconfig
and this time it worked!

However, when I turned off logging, the w! no longer makes
the problem go away, and there is a long pause before the
"Error: Device 769... Hotplug scripts not working" message.
(Logging need only be enabled in xen-backend.agent to
make the problem again go away.)

Some weird timing problem?

My /etc/xen/xmdefconfig is very short:
kernel = "/tmp/xenlinux"
memory = 256
nics=0
disk = ['phy:loop0,hda1,w']  # <-change to w!

and after a fresh boot, I am simply doing:

# lomount -t ext2 -diskimage /var/xen/hda /mnt
# xend start
# xm create

I can see how it could be interpreted that loop0 is
being used both by domain0 and the newly created domain,
but isn't this a common use model?

Dan

P.S. When I change my /etc/xen/xmdefconfig to
disk = ['file:/var/xen/hda,hda1,w']
mounting the root disk fails with:
UDF-fs: No VRS found

> -----Original Message-----
> From: Ewan Mellor [mailto:ewan@xensource.com] 
> Sent: Thursday, December 01, 2005 5:51 PM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: Xen Mailing List
> Subject: Re: [Xen-devel] Hotplug scripts not working... 
> xen/ia64 domU stopped working
> 
> On Thu, Dec 01, 2005 at 04:39:03PM -0800, Magenheimer, Dan 
> (HP Labs Fort Collins) wrote:
> 
> > 
> > > > By "put logging into" do you mean adding a '-x' at the end
> > > > of the first (bin/sh) line?  If so, where is the logging going?
> > > > (not to the console nor to /var/log/xend.log...)  Sorry...
> > > > it's been awhile since I've done script debugging and it's
> > > > definitely a lot different than hypervisor debugging :-}
> > > 
> > > Doing that writes to stderr, which unfortunately is going 
> > > straight down
> > > /dev/null, because this is being run by the kernel's hotplug 
> > > infrastruture.
> > > 
> > > You can either use echo "Message" >~/my-log to write to a log 
> > > file of your own,
> > > or log err "Message" to write to syslog (once you have included
> > > xen-hotplug-common.h).
> > 
> > Any suggestions as to where in the file would be illuminating?
> 
> Just keep shuffling them forward until they stop working ;-)  
> I really have no
> idea -- I'd just binary chop until I found out where the problem was. 
> 
> > And where is "syslog"? (not in /var/log... it's a RHEL3 system)
> 
> /var/log/messages is normal for Redhat, I think.  This is 
> usually configurable
> with /etc/syslog.conf or /etc/syslog-ng.conf, but hardly 
> anyone changes from the
> default!
> 
> > I can confirm now that cset 8048 works and 8049 does not.
> > Using 'w!' does not make any difference.  I don't see any
> > changes in the changeset that look particularly interesting
> > from an ia64 perspective.  Do you see anything new that might
> > reach into the hypervisor that didn't before?  Or perhaps
> > something new with evtchn (which has some differences on ia64)?
> 
> Are you using really long file names for these 
> loopback-mounted disks?  Someone
> reported a failure with filenames greater than 64 chars 
> today.  There's
> nothing IA64-specific that I'm aware of.
> 
> Ewan.
> 

^ permalink raw reply	[flat|nested] 29+ messages in thread
* RE: Hotplug scripts not working... xen/ia64 domU stopped working
@ 2005-12-02  0:54 Magenheimer, Dan (HP Labs Fort Collins)
  0 siblings, 0 replies; 29+ messages in thread
From: Magenheimer, Dan (HP Labs Fort Collins) @ 2005-12-02  0:54 UTC (permalink / raw)
  To: Ewan Mellor; +Cc: Xen Mailing List

> > Confirmed that cset 8048 works, so the problem starts between
> > cset 8049 and 8054. 
> 
> Well it can only be 8049 then.  I'd back that out for now 
> until we figure out
> what the problem is.  That cset is flawed anyway -- there's 
> new changes in that
> area on the way -- but all the problems that we've seen 
> before should still
> be logging things.  We'll revisit this one when those new 
> changes come in.

When I apply (-R) "hg diff -r 8048 -r 8049" to tip (8154),
a number of hunks fail (block, block-common.sh, and DevController)
so this is easier said than done, especially for a shell/python
novice :-(

Do you see any easy way to turn off the intent of the patch
so I can test-disable it on ia64?  I'm about 100 csets behind
now (against xen-unstable) and I'll bet there are other
problem csets waiting to be found.

Thanks,
Dan

^ permalink raw reply	[flat|nested] 29+ messages in thread
* RE: Hotplug scripts not working... xen/ia64 domU stopped working
@ 2005-12-02  0:39 Magenheimer, Dan (HP Labs Fort Collins)
  2005-12-02  0:51 ` Ewan Mellor
  0 siblings, 1 reply; 29+ messages in thread
From: Magenheimer, Dan (HP Labs Fort Collins) @ 2005-12-02  0:39 UTC (permalink / raw)
  To: Ewan Mellor; +Cc: Xen Mailing List


> > By "put logging into" do you mean adding a '-x' at the end
> > of the first (bin/sh) line?  If so, where is the logging going?
> > (not to the console nor to /var/log/xend.log...)  Sorry...
> > it's been awhile since I've done script debugging and it's
> > definitely a lot different than hypervisor debugging :-}
> 
> Doing that writes to stderr, which unfortunately is going 
> straight down
> /dev/null, because this is being run by the kernel's hotplug 
> infrastruture.
> 
> You can either use echo "Message" >~/my-log to write to a log 
> file of your own,
> or log err "Message" to write to syslog (once you have included
> xen-hotplug-common.h).

Any suggestions as to where in the file would be illuminating?
And where is "syslog"? (not in /var/log... it's a RHEL3 system)
 
> > Status: cset 8006 and cset 8029 both work fine.  Cset 8054 fails
> > with the "Hotplug scripts not working" message.  This narrows
> > the field considerably.  Cset 8043 and 8049 look suspicious.
> > For 8043, I thought maybe there is a dependency on the newly
> > added arch_memory_op call, but flagged that for ia64 and it
> > doesn't appear to be the case.  Cset 8049: This isn't intended
> > to stop use of a disk-in-a-file via the loopback driver, is it?
> 
> No, it's intended to protect you from mounting the same file 
> twice in this way,
> but not to stop you from doing it the once.  If this check 
> was failing, you
> would get a different error message anyway.  You might try 
> using 'w!' as the
> mode in your vbd config file rather than 'w'.  This will 
> bypass the checks,
> which at least would point the figure at that particular 
> chunk of code.

I can confirm now that cset 8048 works and 8049 does not.
Using 'w!' does not make any difference.  I don't see any
changes in the changeset that look particularly interesting
from an ia64 perspective.  Do you see anything new that might
reach into the hypervisor that didn't before?  Or perhaps
something new with evtchn (which has some differences on ia64)?

Any help/suggestions would be appreciated as we'd really like
to get Xen/ia64 working again before 3.0.

Thanks,
Dan

^ permalink raw reply	[flat|nested] 29+ messages in thread
* RE: Hotplug scripts not working... xen/ia64 domU stopped working
@ 2005-12-01 21:54 Magenheimer, Dan (HP Labs Fort Collins)
  2005-12-01 23:31 ` Ewan Mellor
  0 siblings, 1 reply; 29+ messages in thread
From: Magenheimer, Dan (HP Labs Fort Collins) @ 2005-12-01 21:54 UTC (permalink / raw)
  To: Ewan Mellor; +Cc: Xen Mailing List

> The xend.log and /etc/xen/xmdefconfig are the same as the last.
> I'm building 8048 now (takes about an hour). 

Confirmed that cset 8048 works, so the problem starts between
cset 8049 and 8054. 

^ permalink raw reply	[flat|nested] 29+ messages in thread
* RE: Hotplug scripts not working... xen/ia64 domU stopped working
@ 2005-12-01 20:49 Magenheimer, Dan (HP Labs Fort Collins)
  2005-12-01 23:38 ` Ewan Mellor
  0 siblings, 1 reply; 29+ messages in thread
From: Magenheimer, Dan (HP Labs Fort Collins) @ 2005-12-01 20:49 UTC (permalink / raw)
  To: Ewan Mellor; +Cc: Xen Mailing List

Sorry for the delay.  I reinstalled from scratch and started
searching from the last working version.  (See status below.)

> > I don't have a /var/log/debug or /var/log/syslog and 
> /var/log/messages
> > is unrevealing.  Do you mean xend.log and xend-debug.log?  If so,
> > attached (along with my very simple xmdefconfig).
> 
> No, I really meant /var/log/messages -- the hotplug scripts 
> log there, and you
> usually see hotplug or udev events going through there too.

Definitely no hotplug or udev events going into /var/log/messages.
 
> If you're not seeing any hotplug script logging at all you 
> are going to have to
> trace the hotplug event until you find out where it 
> disappears.  Start with
> cat /proc/sys/kernel/hotplug.  If that's udevsend and 
> udevinfo -V reports 
> greater than 059 then you are using udev, so check that
> /etc/udev/rules.d/xen-backend.rules is in place, otherwise 
> you are using 

cat /proc/sys/kernel/hotplug shows /sbin/hotplug

> hotplug, so put logging into /sbin/hotplug (usually a script)
> and /etc/hotplug/xen-backend.agent.  Either way, you'll need 
> logging in
> /etc/xen/scripts/block.

By "put logging into" do you mean adding a '-x' at the end
of the first (bin/sh) line?  If so, where is the logging going?
(not to the console nor to /var/log/xend.log...)  Sorry...
it's been awhile since I've done script debugging and it's
definitely a lot different than hypervisor debugging :-}

Status: cset 8006 and cset 8029 both work fine.  Cset 8054 fails
with the "Hotplug scripts not working" message.  This narrows
the field considerably.  Cset 8043 and 8049 look suspicious.
For 8043, I thought maybe there is a dependency on the newly
added arch_memory_op call, but flagged that for ia64 and it
doesn't appear to be the case.  Cset 8049: This isn't intended
to stop use of a disk-in-a-file via the loopback driver, is it?

The xend.log and /etc/xen/xmdefconfig are the same as the last.
I'm building 8048 now (takes about an hour).

Thanks for all the help.  I'm getting closer...
Dan

^ permalink raw reply	[flat|nested] 29+ messages in thread
* RE: Hotplug scripts not working... xen/ia64 domU stopped working
@ 2005-11-30 21:13 Magenheimer, Dan (HP Labs Fort Collins)
  2005-12-01  1:01 ` Ewan Mellor
  0 siblings, 1 reply; 29+ messages in thread
From: Magenheimer, Dan (HP Labs Fort Collins) @ 2005-11-30 21:13 UTC (permalink / raw)
  To: Ewan Mellor; +Cc: Xen Mailing List

[-- Attachment #1: Type: text/plain, Size: 1884 bytes --]

 > > > Switched back to cset 8122, ran make uninstall, make 
> install-tools,
> > > and copied proper dom0, domU, and xen images back into 
> place, booted
> > > xen/dom0 and tried to run domU.  Failed with the same 
> hotplug message.
> > > Then ran xen-bugtool and got:
> > > 
> > > Traceback (most recent call last):
> > >   File "/usr/sbin/xen-bugtool", line 17, in ?
> > >     sys.exit(bugtool.main())
> > >   File "/usr/lib/python/xen/util/bugtool.py", line 73, in main
> > >     bugball.append(string_iterator('physinfo',
> > > prettyDict(xc,physinfo())))
> > > xen.lowlevel.xc.error: (38, 'Function not implemented')
> > > 
> > > Since I've never run xen-bugtool before, I don't know if this
> > > is a side effect of leftover dregs from other installs.  Also,
> > > not sure if this (even with error) is supposed to put results
> > > in a file somewhere?
> > 
> > The physinfo call has been around forever.  I'd say that 
> your kernel and tools
> > are disagreeing on the size of a structure or something like that.

Could be.  I'll take a look to see if what data structures changed.

> Actually, is physinfo even implemented on ia64?  (Does xm info work?)

No apparently not.  It's never been needed before now.  It can probably
be easily implemented.

Are you suspecting this is a related to my problem (e.g. the
hotplug issue) or just needed for xen-bugtool and xm info?
 
> Regarding the hotplug failure, please send your
> /var/log/{debug,messages,syslog} and I'll take a look.

I don't have a /var/log/debug or /var/log/syslog and /var/log/messages
is unrevealing.  Do you mean xend.log and xend-debug.log?  If so,
attached (along with my very simple xmdefconfig).

By the way, I've never had to deal with any of the hotplug stuff
on Xen/ia64... did some new requirement get added in the last few
days (post-8006)?

Dan

[-- Attachment #2: xmdefconfig --]
[-- Type: application/octet-stream, Size: 133 bytes --]

kernel = "/tmp/xenlinux"
memory = 256
nics=0
disk = ['phy:loop0,hda1,w']
#disk = ['file:/var/xen/sda,hda1,w']
#root = "/dev/hda1 ro"

[-- Attachment #3: xend-debug.log --]
[-- Type: application/octet-stream, Size: 396 bytes --]


Link veth0 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports.  If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.


[-- Attachment #4: xend.log --]
[-- Type: application/octet-stream, Size: 6183 bytes --]


[2005-11-30 14:00:58 xend] INFO (SrvDaemon:268) Xend Daemon started
[2005-11-30 14:00:58 xend] INFO (SrvDaemon:272) Xend changeset: Tue Nov 29 09:59:03 2005 +0100 8112:ccf76e51e7e6.
[2005-11-30 14:00:58 xend.XendDomainInfo] DEBUG (XendDomainInfo:199) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 98409341685L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 524288, 'maxmem_kb': 524288, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 1, 'blocked': 0})
[2005-11-30 14:00:58 xend.XendDomainInfo] INFO (XendDomainInfo:211) Recreating domain 0, UUID 00000000-00000000-00000000-00000000.
[2005-11-30 14:00:58 xend.XendDomainInfo] WARNING (XendDomainInfo:233) No vm path in store for existing domain 0
[2005-11-30 14:00:58 xend.XendDomainInfo] DEBUG (XendDomainInfo:602) Storing VM details: {'ssidref': '0', 'uuid': '00000000-00000000-00000000-00000000', 'on_reboot': 'restart', 'on_poweroff': 'destroy', 'name': 'Domain-0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '512', 'on_crash': 'restart', 'maxmem': '512'}
[2005-11-30 14:00:58 xend.XendDomainInfo] DEBUG (XendDomainInfo:627) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '524288', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-00000000-00000000-00000000', 'domid': '0'}
[2005-11-30 14:00:58 xend] DEBUG (XendDomain:144) number of vcpus to use is 0
[2005-11-30 14:00:58 xend] INFO (SrvServer:112) unix path=/var/lib/xend/xend-socket
[2005-11-30 14:02:15 xend.XendDomainInfo] DEBUG (XendDomainInfo:177) XendDomainInfo.create(['vm', ['name', 'foo'], ['memory', '256'], ['image', ['linux', ['kernel', '/tmp/xenlinux'], ['vcpus', '1'], ['vcpus', '1'], ['boot', 'c'], ['display', 'localhost:10.0']]], ['device', ['vbd', ['uname', 'phy:loop0'], ['dev', 'hda1'], ['mode', 'w']]]])
[2005-11-30 14:02:15 xend.XendDomainInfo] DEBUG (XendDomainInfo:282) parseConfig: config is ['vm', ['name', 'foo'], ['memory', '256'], ['image', ['linux', ['kernel', '/tmp/xenlinux'], ['vcpus', '1'], ['vcpus', '1'], ['boot', 'c'], ['display', 'localhost:10.0']]], ['device', ['vbd', ['uname', 'phy:loop0'], ['dev', 'hda1'], ['mode', 'w']]]]
[2005-11-30 14:02:15 xend.XendDomainInfo] DEBUG (XendDomainInfo:336) parseConfig: result is {'ssidref': None, 'uuid': None, 'on_crash': None, 'on_reboot': None, 'image': ['linux', ['kernel', '/tmp/xenlinux'], ['vcpus', '1'], ['vcpus', '1'], ['boot', 'c'], ['display', 'localhost:10.0']], 'on_poweroff': None, 'name': 'foo', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'vcpu_avail': None, 'memory': 256, 'device': [('vbd', ['vbd', ['uname', 'phy:loop0'], ['dev', 'hda1'], ['mode', 'w']])], 'bootloader': None, 'cpu': None, 'maxmem': None}
[2005-11-30 14:02:15 xend.XendDomainInfo] DEBUG (XendDomainInfo:1064) XendDomainInfo.construct: None 0
[2005-11-30 14:02:15 xend.XendDomainInfo] DEBUG (XendDomainInfo:1096) XendDomainInfo.initDomain: 1 1.0
[2005-11-30 14:02:15 xend] INFO (image:132) buildDomain os=linux dom=1 vcpus=1
[2005-11-30 14:02:15 xend] DEBUG (image:170) dom            = 1
[2005-11-30 14:02:15 xend] DEBUG (image:171) image          = /tmp/xenlinux
[2005-11-30 14:02:15 xend] DEBUG (image:172) store_evtchn   = 1
[2005-11-30 14:02:15 xend] DEBUG (image:173) console_evtchn = 2
[2005-11-30 14:02:15 xend] DEBUG (image:174) cmdline        = 
[2005-11-30 14:02:15 xend] DEBUG (image:175) ramdisk        = 
[2005-11-30 14:02:15 xend] DEBUG (image:176) vcpus          = 1
[2005-11-30 14:02:16 xend] DEBUG (DevController:101) DevController: writing {'virtual-device': '769', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/769'} to /local/domain/1/device/vbd/769.
[2005-11-30 14:02:16 xend] DEBUG (DevController:103) DevController: writing {'domain': 'foo', 'frontend': '/local/domain/1/device/vbd/769', 'dev': 'hda1', 'state': '1', 'params': 'loop0', 'mode': 'w', 'frontend-id': '1', 'type': 'phy'} to /local/domain/0/backend/vbd/1/769.
[2005-11-30 14:02:16 xend.XendDomainInfo] DEBUG (XendDomainInfo:602) Storing VM details: {'ssidref': '0', 'uuid': '936bbc85-1bdf2b28-19798f38-c57fd514', 'on_reboot': 'restart', 'image': '(linux (kernel /tmp/xenlinux) (vcpus 1) (vcpus 1) (boot c) (display localhost:10.0))', 'on_poweroff': 'destroy', 'name': 'foo', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': 'restart', 'start_time': '1133384536.07', 'maxmem': '256'}
[2005-11-30 14:02:16 xend.XendDomainInfo] DEBUG (XendDomainInfo:627) Storing domain details: {'console/ring-ref': '1917', 'console/port': '2', 'name': 'foo', 'console/limit': '1048576', 'vm': '/vm/936bbc85-1bdf2b28-19798f38-c57fd514', 'domid': '1', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '1918', 'store/port': '1'}
[2005-11-30 14:02:16 xend] DEBUG (DevController:119) Waiting for devices vif.
[2005-11-30 14:02:16 xend] DEBUG (DevController:119) Waiting for devices usb.
[2005-11-30 14:02:16 xend] DEBUG (DevController:119) Waiting for devices vbd.
[2005-11-30 14:02:16 xend] DEBUG (DevController:125) Waiting for 769.
[2005-11-30 14:02:16 xend] DEBUG (DevController:398) hotplugStatusCallback /local/domain/0/backend/vbd/1/769/hotplug-status.
[2005-11-30 14:02:26 xend] ERROR (SrvBase:87) Request wait_for_devices failed.
Traceback (most recent call last):
  File "/usr/lib/python/xen/web/SrvBase.py", line 85, in perform
    return op_method(op, req)
  File "/usr/lib/python/xen/xend/server/SrvDomain.py", line 68, in op_wait_for_devices
    return self.dom.waitForDevices()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1264, in waitForDevices
    self.waitForDevices_(c)
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 912, in waitForDevices_
    return self.getDeviceController(deviceClass).waitForDevices()
  File "/usr/lib/python/xen/xend/server/DevController.py", line 121, in waitForDevices
    return map(self.waitForDevice, self.deviceIDs())
  File "/usr/lib/python/xen/xend/server/DevController.py", line 131, in waitForDevice
    raise VmError("Device %s (%s) could not be connected. "
VmError: Device 769 (vbd) could not be connected. Hotplug scripts not working.

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

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

^ permalink raw reply	[flat|nested] 29+ messages in thread
* RE: Hotplug scripts not working... xen/ia64 domU stopped working
@ 2005-11-30 16:56 Magenheimer, Dan (HP Labs Fort Collins)
  2005-11-30 18:10 ` Himanshu Raj
  0 siblings, 1 reply; 29+ messages in thread
From: Magenheimer, Dan (HP Labs Fort Collins) @ 2005-11-30 16:56 UTC (permalink / raw)
  To: Ryan Harper; +Cc: Xen Mailing List, Ewan Mellor

Sorry, manual typo.  (No cut/paste in ultravnc and samba
was not responding after a couple tries so I just manually
typed the error message.) 

> -----Original Message-----
> From: Ryan Harper [mailto:ryanh@us.ibm.com] 
> Sent: Wednesday, November 30, 2005 9:54 AM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: Ewan Mellor; Xen Mailing List
> Subject: Re: [Xen-devel] Hotplug scripts not working... 
> xen/ia64 domU stopped working
> 
> * Magenheimer, Dan (HP Labs Fort Collins) 
> <dan.magenheimer@hp.com> [2005-11-30 10:49]:
> >     sys.exit(bugtool.main())
> >   File "/usr/lib/python/xen/util/bugtool.py", line 73, in main
> >     bugball.append(string_iterator('physinfo',
> > prettyDict(xc,physinfo())))
>                ^
> The comma looks like a typo, but in the latest changeset, 
> line 73 in my
> tree looks like this:
> 
>    bugball.append(string_iterator('physinfo',  
> prettyDict(xc.physinfo())))
> 
> Not sure where that comma came from.
> 
> 
> -- 
> Ryan Harper
> Software Engineer; Linux Technology Center
> IBM Corp., Austin, Tx
> (512) 838-9253   T/L: 678-9253
> ryanh@us.ibm.com
> 

^ permalink raw reply	[flat|nested] 29+ messages in thread
* RE: Hotplug scripts not working... xen/ia64 domU stopped working
@ 2005-11-30 16:48 Magenheimer, Dan (HP Labs Fort Collins)
  2005-11-30 16:53 ` Ryan Harper
  2005-11-30 17:16 ` Ewan Mellor
  0 siblings, 2 replies; 29+ messages in thread
From: Magenheimer, Dan (HP Labs Fort Collins) @ 2005-11-30 16:48 UTC (permalink / raw)
  To: Ewan Mellor; +Cc: Xen Mailing List

Switched back to cset 8122, ran make uninstall, make install-tools,
and copied proper dom0, domU, and xen images back into place, booted
xen/dom0 and tried to run domU.  Failed with the same hotplug message.
Then ran xen-bugtool and got:

Traceback (most recent call last):
  File "/usr/sbin/xen-bugtool", line 17, in ?
    sys.exit(bugtool.main())
  File "/usr/lib/python/xen/util/bugtool.py", line 73, in main
    bugball.append(string_iterator('physinfo',
prettyDict(xc,physinfo())))
xen.lowlevel.xc.error: (38, 'Function not implemented')

Since I've never run xen-bugtool before, I don't know if this
is a side effect of leftover dregs from other installs.  Also,
not sure if this (even with error) is supposed to put results
in a file somewhere?

Thanks,
Dan

> -----Original Message-----
> From: Ewan Mellor [mailto:ewan@xensource.com] 
> Sent: Wednesday, November 30, 2005 4:53 AM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: Xen Mailing List
> Subject: Re: [Xen-devel] Hotplug scripts not working... 
> xen/ia64 domU stopped working
> 
> On Tue, Nov 29, 2005 at 08:43:30PM -0800, Magenheimer, Dan 
> (HP Labs Fort Collins) wrote:
> 
> > Somewhere between cset 8006 and cset 8112, the virtual block
> > device stopped working for Xen/ia64.  With cset 8112, I get:
> > 
> > Error: Device 769 (vbd) could not be connected. Hotplug scripts not
> > working.
> > 
> > Any suggestions where to start looking or will I need to do a binary
> > search?
> 
> Please use xen-bugtool (new in the latest changesets) to 
> collect your logs so
> that I can take a look.
> 
> Cheers,
> 
> Ewan.
> 

^ permalink raw reply	[flat|nested] 29+ messages in thread
* RE: Hotplug scripts not working... xen/ia64 domU stopped working
@ 2005-11-30 14:17 Magenheimer, Dan (HP Labs Fort Collins)
  0 siblings, 0 replies; 29+ messages in thread
From: Magenheimer, Dan (HP Labs Fort Collins) @ 2005-11-30 14:17 UTC (permalink / raw)
  To: Ewan Mellor; +Cc: Xen Mailing List

> On Tue, Nov 29, 2005 at 08:43:30PM -0800, Magenheimer, Dan 
> (HP Labs Fort Collins) wrote:
> 
> > Somewhere between cset 8006 and cset 8112, the virtual block
> > device stopped working for Xen/ia64.  With cset 8112, I get:
> > 
> > Error: Device 769 (vbd) could not be connected. Hotplug scripts not
> > working.
> > 
> > Any suggestions where to start looking or will I need to do a binary
> > search?
> 
> Please use xen-bugtool (new in the latest changesets) to 
> collect your logs so
> that I can take a look.

Hmmmm... it appears xen-bugtool is born at 8073.  I can go
back to that but have already reproduced the problem at 8054.

HOWEVER... I am now having problems at 8006 which worked
yesterday.  I suspect that there are some Xen tools/files that
are not getting replaced.  (And xen-bugtool doesn't work there
as one would expect... it is still in place because of the
previous install of 8112 but gives a python error.)

Is there a way to do a "make clean" on all Xen files outside
of the xen-unstable.hg directory to ensure no "old" (or in my case
newer) files/scripts from /etc, /bin/ etc are being accidentally
used?  I know others have experienced this kind of problem and
have "fixed" it by reinstalling their distro from scratch.
I had a disk trashed while I was on holiday and after reinstalling
RH3 from scratch, 8006 worked.  But after going to 8112 (hotplug
error), then 8054 (hotplug error), then 8029 (can't mount
root disk), 8006 didn't work (can't mount root disk).  It
would be a pain if I have to reinstall RH3 again from scratch.

Alternately, perhaps I am using the wrong make command?  I am
doing a "make" in the xen-unstable directory, then 
using "make install-tools" (as root)... and of course ensuring
my xen, dom0, and domU images are in the right place.  Perhaps
install-tools is not always overwriting every tool so I am
getting a strange mix of versions (thus the make clean question
above)?

Thanks,
Dan

^ permalink raw reply	[flat|nested] 29+ messages in thread
* RE: Hotplug scripts not working... xen/ia64 domU stopped working
@ 2005-11-30  5:50 Magenheimer, Dan (HP Labs Fort Collins)
  0 siblings, 0 replies; 29+ messages in thread
From: Magenheimer, Dan (HP Labs Fort Collins) @ 2005-11-30  5:50 UTC (permalink / raw)
  To: Xen Mailing List

First binary search step: cset 8054 fails the same way (for Xen/ia64).

> -----Original Message-----
> From: Magenheimer, Dan (HP Labs Fort Collins) 
> Sent: Tuesday, November 29, 2005 9:44 PM
> To: Xen Mailing List
> Subject: Hotplug scripts not working... xen/ia64 domU stopped working
> 
> Somewhere between cset 8006 and cset 8112, the virtual block
> device stopped working for Xen/ia64.  With cset 8112, I get:
> 
> Error: Device 769 (vbd) could not be connected. Hotplug 
> scripts not working.
> 
> Any suggestions where to start looking or will I need to do a binary
> search?
> 
> Thanks,
> Dan
> 

^ permalink raw reply	[flat|nested] 29+ messages in thread
* Hotplug scripts not working... xen/ia64 domU stopped working
@ 2005-11-30  4:43 Magenheimer, Dan (HP Labs Fort Collins)
  2005-11-30 11:52 ` Ewan Mellor
  0 siblings, 1 reply; 29+ messages in thread
From: Magenheimer, Dan (HP Labs Fort Collins) @ 2005-11-30  4:43 UTC (permalink / raw)
  To: Xen Mailing List

Somewhere between cset 8006 and cset 8112, the virtual block
device stopped working for Xen/ia64.  With cset 8112, I get:

Error: Device 769 (vbd) could not be connected. Hotplug scripts not
working.

Any suggestions where to start looking or will I need to do a binary
search?

Thanks,
Dan

^ permalink raw reply	[flat|nested] 29+ messages in thread
end of thread, other threads:[~2005-12-03 20:31 UTC | newest]

Thread overview: 29+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-11-30 14:26 Hotplug scripts not working... xen/ia64 domU stopped working Petersson, Mats
2005-12-01  0:26 ` Hotplug scripts not working... xen/ia64 domU?stopped working Horms
  -- strict thread matches above, loose matches on Subject: below --
2005-12-03 20:31 Hotplug scripts not working... xen/ia64 domU stopped working Magenheimer, Dan (HP Labs Fort Collins)
2005-12-02 20:40 Magenheimer, Dan (HP Labs Fort Collins)
2005-12-02 21:22 ` David F Barrera
2005-12-02 17:41 Magenheimer, Dan (HP Labs Fort Collins)
2005-12-02 20:17 ` Ewan Mellor
2005-12-02  0:54 Magenheimer, Dan (HP Labs Fort Collins)
2005-12-02  0:39 Magenheimer, Dan (HP Labs Fort Collins)
2005-12-02  0:51 ` Ewan Mellor
2005-12-01 21:54 Magenheimer, Dan (HP Labs Fort Collins)
2005-12-01 23:31 ` Ewan Mellor
2005-12-01 20:49 Magenheimer, Dan (HP Labs Fort Collins)
2005-12-01 23:38 ` Ewan Mellor
2005-12-02  0:53   ` Adam Heath
2005-12-02  1:44     ` Ewan Mellor
2005-12-02  2:16       ` Adam Heath
2005-11-30 21:13 Magenheimer, Dan (HP Labs Fort Collins)
2005-12-01  1:01 ` Ewan Mellor
2005-11-30 16:56 Magenheimer, Dan (HP Labs Fort Collins)
2005-11-30 18:10 ` Himanshu Raj
2005-11-30 16:48 Magenheimer, Dan (HP Labs Fort Collins)
2005-11-30 16:53 ` Ryan Harper
2005-11-30 17:16 ` Ewan Mellor
2005-11-30 17:22   ` Ewan Mellor
2005-11-30 14:17 Magenheimer, Dan (HP Labs Fort Collins)
2005-11-30  5:50 Magenheimer, Dan (HP Labs Fort Collins)
2005-11-30  4:43 Magenheimer, Dan (HP Labs Fort Collins)
2005-11-30 11:52 ` Ewan Mellor

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.