Re: "Hotplug scripts not working" again

[Eric Haszlakiewicz <erh%nimenees.com@localhost>]

On Tue, Jun 09, 2009 at 10:27:53PM +0200, Manuel Bouyer wrote:
> On Tue, Jun 09, 2009 at 03:17:24PM -0500, Eric Haszlakiewicz wrote:
> > On Tue, Jun 09, 2009 at 10:05:58AM +0200, Manuel Bouyer wrote:
> > > does /usr/pkg/etc/xen/scripts/vif-bridge exists and is executable ?
> > > I guess it would print an error if it was not.
> > > You could also change it to be #!/bin/sh -ex so it prints what it's doing.
> > 
> > yes, it exists, and it's being executed, but it doesn't do anything when
> > passed either the "1" or "5" as the second parameter.  It only has cases
> > for "6" (xenstore-rm $xpath) and "2" (some ifconfig, brconfig and 
> > xenstore-write commands).  What are 1 and 5 supposed to be?
> 
> 1 is "XenbusStateInitialising", 2 is "XenbusStateInitWait", 5 is
> "XenbusStateClosing" and 6 is "XenbusStateClosed".
> 
> The script is called on each state change, but it doesn't have work to do
> for each of them. 2 is the most important: this is where it attaches
> the vif to a bridge (or give it an IP, or take whatever action
> to get this interface functionnal and connected to the external world).
> Once this is done the script switches the state to 3 "XenbusStateInitialised"
> so the kernel and xend knows that the vif is in working state and
> they can go forward attaching the other end in the domU.

hmm.. interesting.  The machine I have that works never runs those scripts
with state 1, while the non-working one did.

I restarted the machine, and the first few things I see in xend.log are:
[2009-06-10 06:51:16 243] INFO (SrvDaemon:331) Xend Daemon started
[2009-06-10 06:51:16 243] INFO (SrvDaemon:335) Xend changeset: unavailable.
[2009-06-10 06:51:16 243] INFO (SrvDaemon:342) Xend version: Unknown.
[2009-06-10 06:51:16 243] DEBUG (XendDomainInfo:132) 
XendDomainInfo.recreate(...snip...)
[2009-06-10 06:51:16 243] INFO (XendDomainInfo:148) Recreating domain 0, UUID 
00000000-0000-0000-0000-000000000000. at /local/domain/0
[2009-06-10 06:51:16 243] DEBUG (XendDomainInfo:2093) Storing VM details: 
{...snip...}
[2009-06-10 06:51:16 243] DEBUG (XendDomain:434) Adding Domain: 0
[2009-06-10 06:51:16 243] DEBUG (XendDomain:379) number of vcpus to use is 0
[2009-06-10 06:51:16 243] DEBUG (XendDomainInfo:998) 
XendDomainInfo.handleShutdownWatch
[2009-06-10 06:51:17 243] WARNING (XendAPI:672) API call: VBD.set_device not 
found
[2009-06-10 06:51:17 243] WARNING (XendAPI:672) API call: VBD.set_type not found
etc... 

What are these warnings talking about?  I found a number of references to
these on the web, but no explanations.  I get the same warnings on my
working machine, so they don't seem to cause problems.

Now the good news: After restarting, I am now able to start a domU:
# xm create foo
Using config file "/usr/pkg/etc/xen/foo".
Started domain foo
# xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0   768     1     r-----    543.9
foo                                          1   128     1     r-----      3.0

However, I can't attach a console:
# xm console foo
xenconsole: Could not read tty from store: No such file or directory

xenstore-ls agains has problems reading everything if run without any options.
If I run "xenstore-ls /local/domain/1/console" I get:
ring-ref = "60227"
port = "2"
limit = "1048576"

Note that there's no tty entry.  I don't see anything in particular in the
logs that says anything about console or tty.

eric