Re: "Hotplug scripts not working" again

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

On Mon, Jun 08, 2009 at 10:46:55AM +0200, Manuel Bouyer wrote:
> On Sun, Jun 07, 2009 at 10:56:06AM -0500, Eric Haszlakiewicz wrote:
> > When I run:
> > xm create foo
> > It hangs for a while, then prints:
> > Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
> 
> This is usually when it tries to connect the vif to a non-existing bridge

Yeah, that's what I figured, but I'm pretty sure I've got the bridge created.
I thought that maybe it was something to do with the wm driver, but the only
other interface on this machine is lo0, and trying to bridge that doesn't
work.
# ifconfig wm0
wm0: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST> mtu 
1500
        
capabilities=2bf80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Tx,UDP6CSUM_Tx>
        enabled=0
        address: 00:11:43:0f:bb:32
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet xxx.xxx.xxx.xxx netmask 0xffffffc0 broadcast xxx.xxx.xxx.xxx
        inet6 fe80::xxxx:xxxx:xxxx:xxxx%wm0 prefixlen 64 scopeid 0x1
# ifconfig bridge1
bridge1: flags=41<UP,RUNNING> mtu 1500
# brconfig bridge1
bridge1: flags=41<UP,RUNNING>
        Configuration:
                priority 32768 hellotime 2 fwddelay 15 maxage 20
                ipfilter disabled flags 0x0
        Interfaces:
                wm0 flags=3<LEARNING,DISCOVER>
                        port 1 priority 128
        Address cache (max cache: 100, timeout: 1200):
                00:19:b9:b6:bc:9d wm0 1194 flags=0<>
...58 more lines...
                00:15:f9:f7:77:e0 wm0 4294967203 flags=0<>



> > In the xend.log, the last few lines when it hangs are:
> > [2009-06-06 21:26:54 12883] DEBUG (DevController:151) Waiting for devices 
> > vif.
> > [2009-06-06 21:26:54 12883] DEBUG (DevController:151) Waiting for devices 
> > usb.
> > [2009-06-06 21:26:54 12883] DEBUG (DevController:151) Waiting for devices 
> > vbd.
> > [2009-06-06 21:26:54 12883] DEBUG (DevController:156) Waiting for 1.
> > [2009-06-06 21:26:54 12883] DEBUG (DevController:590) hotplugStatusCallback 
> > /local/domain/0/backend/vbd/9/1/hotplug-status.
> > 
> > but eventually it figures out things aren't working and destroys the domain.
> > 
> > In xend-debug.log I see these lines:
> > Xend started at Sat Jun  6 21:22:56 2009.
> > brctl: not found
> > brctl: not found
> 
> What about /var/log/xenbackendd.log ?

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

That last line about not being able to read .../type is new.  It wasn't
doing that before, but I don't know what I did to make it appear now.
I'm thinking that maybe I should reboot the machine, but I don't currently
have easy physical access to is so I'm a bit wary. :(


> > I noticed that when it's hanging, if I run xenstore-ls, that also gets 
> > stuck,
> 
> I also noticed that xenstore-ls can't list the whole store, but it's
> usually not a problem.
 Ok, I'll believe you, but it doesn't exactly inspire confidence. :|

eric