Port-xen archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: "Hotplug scripts not working" again
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:
> > On Mon, Jun 08, 2009 at 07:08:39PM -0500, Eric Haszlakiewicz wrote:
> > > I restart xenbackendd with "xenbackendd -d". Here's the log file:
> > > exec /usr/pkg/etc/xen/scripts/block /local/domain/0/backend/vbd/18/1 1
> > > exec /usr/pkg/etc/xen/scripts/vif-bridge /local/domain/0/backend/vif/18/0
> > > 1
> > > Failed to read /local/domain/0/backend/console/18/0/script (No such file
> > > or directory)
> > > exec /usr/pkg/etc/xen/scripts/vif-bridge /local/domain/0/backend/vif/18/0
> > > 5
> > > exec /usr/pkg/etc/xen/scripts/vif-bridge /local/domain/0/backend/vif/18/0
> > > 5
> > > exec /usr/pkg/etc/xen/scripts/block /local/domain/0/backend/vbd/18/1 5
> > > exec /usr/pkg/etc/xen/scripts/block /local/domain/0/backend/console/18/0 5
> > > xenstore-read: couldn't read path
> > > /local/domain/0/backend/console/18/0/type
> >
> > 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.
--
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
--
Home |
Main Index |
Thread Index |
Old Index