Re: "Hotplug scripts not working" again

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Wed, Jun 10, 2009 at 09:07:30AM -0500, Eric Haszlakiewicz wrote:
> > 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.

This would mean either that the kernel failed to get the vif to state 1,
or that the xenstore didn't notice the state change.

> 
> 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 don't know. I get these too.

> 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

Does it stay in 'r' state, or does it switch to 'b' ?

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

maybe the domU didn't create its tty yet.

> 
> xenstore-ls agains has problems reading everything if run without any options.

known problem.

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

I think xenconsoled is supposed to write the tty. Is xenconsled running
properly ?
What does
xenstore-ls /local/domain/0/backend/console/1 
says ?

-- 
Manuel Bouyer, LIP6, Universite Paris VI.           
Manuel.Bouyer%lip6.fr@localhost
     NetBSD: 26 ans d'experience feront toujours la difference
--