[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working., Error: Device 0 (vif) could not be connected. Hotplug scripts not working.



OK, after 12 hours there is a solution for those with the same problem:

1) make some more loop devices (I have done it, but just to be sure)
2) start the DomU in IDE mode (that was the main problem - I run SATA drives in SW RAID and it didn't like it)

this guy helped me a lot:
http://www.debian-administration.org/articles/396#comment_17

Copy of the post:
I've installed xen 3 and xen-tools on my ubuntu server and all seems well, until I try to start a client domain. (running on Linux xenserver 2.6.12.6-xen #1 SMP Wed Feb 1 21:23:17 UTC 2006 i686 GNU/ Linux)

I get the error: "Error: Device 2049 (vbd) could not be connected. Backend device not found.

Solution :
I've set "use-ide = 1" in /etc/xen-tools/xen-tools.conf and recreated my images and it seems to work now.
I figure that an IDE server has problems trying to run a SCSI domU.
Just to confirm, changing use-ide = 1 and changing my /etc/init.d/ xend to read:

start)
modprobe loop max_loop=64
cd /dev && /dev/MAKEDEV loop
xend start
await_daemons_up
;;

fixed my problems. I now have three domU's working happily.



Josef wrote:
Hello, I'm completely stuck at this point:

I have Debian Etch, SATA drives using sw RAID and I have installed XEN from debian packages. But when I try to start a new image (created by xen-tools: #xen-create-image --hostname=postak3 --ip=10.0.0.3), I got following error:

telex:/home/pepus# xm create postak3.cfg
Using config file "/etc/xen/postak3.cfg".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

the syslog shows this:
[2007-04-28 15:14:39 xend 2913] DEBUG (__init__:1072) Waiting for devices vif.
[2007-04-28 15:14:39 xend 2913] DEBUG (__init__:1072) Waiting for 0.
[2007-04-28 15:14:39 xend 2913] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vif/21/0/hotplug-status.

So i tried to # the whole vif line, after that I got this:
Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working.

and syslog:
[2007-04-28 15:19:19 xend 2913] DEBUG (__init__:1072) Waiting for devices vif. [2007-04-28 15:19:19 xend 2913] DEBUG (__init__:1072) Waiting for devices usb. [2007-04-28 15:19:19 xend 2913] DEBUG (__init__:1072) Waiting for devices vbd.
[2007-04-28 15:19:19 xend 2913] DEBUG (__init__:1072) Waiting for 2049.
[2007-04-28 15:19:19 xend 2913] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vbd/22/2049/hotplug-status.


My /etc/xen/postak3.cfg is following:
kernel  = '/home/boot/vmlinuz-2.6.18-4-xen-686'
ramdisk = '/home/boot/initrd.img-2.6.18-4-xen-686'
memory  = '128'
root    = '/dev/sda1 ro'
disk = [ 'file:/home/xen/domains/postak3/disk.img,sda1,w', 'file:/home/xen/domains/postak3/swap.img,sda2,w' ]
name    = 'postak3'
vif  = [ 'ip=10.0.0.3,mac=00:16:3e:4b:bb:4e,bridge=xenbr0' ]
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'

And the /etc/xen/xend-config.sxp:
(logfile /var/log/xen/xend.log)
(loglevel DEBUG)
(network-script 'network-bridge netdev=eth1')
(vif-script network-bridge)
(dom0-min-mem 196)
(dom0-cpus 0)

brctl show:
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif0.0
                                                       peth1

ifconfig:
eth0 Link encap:Ethernet HWaddr 00:16:76:7A:E1:F2 inet addr:192.168.0.2 Bcast:192.168.255.255 Mask:255.255.0.0
         inet6 addr: fe80::216:76ff:fe7a:e1f2/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:7259 errors:0 dropped:0 overruns:0 frame:0
         TX packets:4669 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:9101345 (8.6 MiB)  TX bytes:449958 (439.4 KiB)
         Base address:0x2000 Memory:88180000-881a0000

eth1 Link encap:Ethernet HWaddr 00:16:76:7A:E1:F3 inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
         inet6 addr: fe80::216:76ff:fe7a:e1f3/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:64 errors:0 dropped:0 overruns:0 frame:0
         TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:6429 (6.2 KiB)  TX bytes:468 (468.0 b)

lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:669 errors:0 dropped:0 overruns:0 frame:0
         TX packets:669 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:83544 (81.5 KiB)  TX bytes:83544 (81.5 KiB)

peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
         UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
         RX packets:64 errors:0 dropped:0 overruns:0 frame:0
         TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:100
         RX bytes:6685 (6.5 KiB)  TX bytes:574 (574.0 b)
         Base address:0x1100 Memory:88020000-88040000

vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
         UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
         RX packets:6 errors:0 dropped:0 overruns:0 frame:0
         TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:468 (468.0 b)  TX bytes:6429 (6.2 KiB)

xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
         UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
         RX packets:69 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:5853 (5.7 KiB)  TX bytes:0 (0.0 b)


Any suggestions? Any help is welcome!
Thanks

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




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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.