Lee Azzarello
2011-Aug-03 23:02 UTC
[Pkg-xen-devel] Bug#636552: xen-hypervisor-4.1-i386: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Package: xen-hypervisor-4.1-i386
Version: 4.1.1-1
Severity: important
Tags: wheezy
I cannot boot a domU with networking after installing the package.
root at topsail:~# xm create /etc/xen/udevtest.cfg -c
root at topsail:~# Error: Device 0 (vif) could not be connected. Hotplug scripts
not working.
[2011-08-03 15:56:53 4411] DEBUG (DevController:139) Waiting for devices tap2.
[2011-08-03 15:56:53 4411] DEBUG (XendDomainInfo:1881)
XendDomainInfo.handleShutdownWatch
[2011-08-03 15:56:53 4411] DEBUG (DevController:139) Waiting for devices vif.
[2011-08-03 15:56:53 4411] DEBUG (DevController:144) Waiting for 0.
[2011-08-03 15:56:53 4411] DEBUG (DevController:628) hotplugStatusCallback
/local/domain/0/backend/vif/2/0/hotplug-status.
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:3071) XendDomainInfo.destroy:
domid=2
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2401) Destroying device model
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2408) Releasing devices
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing vif/0
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing console/0
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing vbd/2050
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2050
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing vbd/2049
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2049
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2406) No device model
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2408) Releasing devices
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing vif/0
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing vbd/2050
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2050
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing vbd/2049
[2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2049
root at topsail:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
#allow-hotplug eth0
#NetworkManager#iface eth0 inet dhcp
iface xenbr0 inet dhcp
bridge_ports eth0
root at topsail:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr f0:de:f1:39:cb:60
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10118 errors:0 dropped:0 overruns:0 frame:0
TX packets:1698 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2294125 (2.1 MiB) TX bytes:391169 (382.0 KiB)
Interrupt:20 Memory:f2500000-f2520000
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:204 errors:0 dropped:0 overruns:0 frame:0
TX packets:204 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:33561 (32.7 KiB) TX bytes:33561 (32.7 KiB)
wlan0 Link encap:Ethernet HWaddr 00:24:d7:7d:89:a8
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
xenbr0 Link encap:Ethernet HWaddr f0:de:f1:39:cb:60
inet addr:10.0.2.211 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::f2de:f1ff:fe39:cb60/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8950 errors:0 dropped:1 overruns:0 frame:0
TX packets:1616 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1919871 (1.8 MiB) TX bytes:378625 (369.7 KiB)
root at topsail:~# ps ax | grep udev
303 ? Ss 0:00 udevd --daemon
1989 ? S 0:00 udevd --daemon
4671 ? S 0:00 udevd --daemon
root at topsail:~# ls -l /etc/udev/rules.d/
total 12
-rw-r--r-- 1 root root 578 Feb 26 17:50 60-wacom.rules
-rw-r--r-- 1 root root 786 Jan 24 2011 70-persistent-cd.rules
-rw-r--r-- 1 root root 813 Jul 16 15:11 70-persistent-net.rules
lrwxrwxrwx 1 root root 35 Aug 3 13:51 xen-backend.rules ->
/lib/udev/rules.d
/xen-backend.rules
lrwxrwxrwx 1 root root 28 Aug 3 14:39 xend.rules ->
/lib/udev/rules.d/xend.rules
lrwxrwxrwx 1 root root 15 Jan 24 2011 z60_hdparm.rules -> ../hdparm.rules
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.39-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
xen-hypervisor-4.1-i386 depends on no packages.
Versions of packages xen-hypervisor-4.1-i386 recommends:
ii xen-utils-4.1 4.1.1-1 XEN administrative tools
Versions of packages xen-hypervisor-4.1-i386 suggests:
pn xen-docs-4.1 <none> (no description available)
-- no debconf information
Todd Deshane
2011-Aug-04 03:30 UTC
[Pkg-xen-devel] Bug#636552: Bug#636552: xen-hypervisor-4.1-i386: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
On Wed, Aug 3, 2011 at 7:02 PM, Lee Azzarello <lee at rockingtiger.com> wrote:> Package: xen-hypervisor-4.1-i386 > Version: 4.1.1-1 > Severity: important > Tags: wheezy > > ?I cannot boot a domU with networking after installing the package. > > root at topsail:~# xm create /etc/xen/udevtest.cfg -cYou should post the output of /etc/xen/udevtest.cfg> root at topsail:~# Error: Device 0 (vif) could not be connected. Hotplug scripts > not working. >See also: http://wiki.xensource.com/xenwiki/XenCommonProblems#head-f75dde47e11dbf9bfd8fca200917316babb654eb> [2011-08-03 15:56:53 4411] DEBUG (DevController:139) Waiting for devices tap2. > [2011-08-03 15:56:53 4411] DEBUG (XendDomainInfo:1881) > XendDomainInfo.handleShutdownWatch > [2011-08-03 15:56:53 4411] DEBUG (DevController:139) Waiting for devices vif. > [2011-08-03 15:56:53 4411] DEBUG (DevController:144) Waiting for 0. > [2011-08-03 15:56:53 4411] DEBUG (DevController:628) hotplugStatusCallback > /local/domain/0/backend/vif/2/0/hotplug-status. > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:3071) XendDomainInfo.destroy: > domid=2 > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2401) Destroying device model > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2408) Releasing devices > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing vif/0 > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276) > XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing console/0 > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276) > XendDomainInfo.destroyDevice: deviceClass = console, device = console/0 > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing vbd/2050 > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276) > XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2050 > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing vbd/2049 > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276) > XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2049 > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2406) No device model > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2408) Releasing devices > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing vif/0 > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276) > XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing vbd/2050 > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276) > XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2050 > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:2414) Removing vbd/2049 > [2011-08-03 15:58:33 4411] DEBUG (XendDomainInfo:1276) > XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2049 > > root at topsail:~# cat /etc/network/interfaces > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface > #allow-hotplug eth0 > #NetworkManager#iface eth0 inet dhcp > > iface xenbr0 inet dhcp > ?bridge_ports eth0 > > root at topsail:~# ifconfig -a > eth0 ? ? ?Link encap:Ethernet ?HWaddr f0:de:f1:39:cb:60 > ? ? ? ? ?UP BROADCAST RUNNING MULTICAST ?MTU:1500 ?Metric:1 > ? ? ? ? ?RX packets:10118 errors:0 dropped:0 overruns:0 frame:0 > ? ? ? ? ?TX packets:1698 errors:0 dropped:0 overruns:0 carrier:0 > ? ? ? ? ?collisions:0 txqueuelen:1000 > ? ? ? ? ?RX bytes:2294125 (2.1 MiB) ?TX bytes:391169 (382.0 KiB) > ? ? ? ? ?Interrupt:20 Memory:f2500000-f2520000 > > 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:204 errors:0 dropped:0 overruns:0 frame:0 > ? ? ? ? ?TX packets:204 errors:0 dropped:0 overruns:0 carrier:0 > ? ? ? ? ?collisions:0 txqueuelen:0 > ? ? ? ? ?RX bytes:33561 (32.7 KiB) ?TX bytes:33561 (32.7 KiB) > > wlan0 ? ? Link encap:Ethernet ?HWaddr 00:24:d7:7d:89:a8 > ? ? ? ? ?BROADCAST MULTICAST ?MTU:1500 ?Metric:1 > ? ? ? ? ?RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > ? ? ? ? ?TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > ? ? ? ? ?collisions:0 txqueuelen:1000 > ? ? ? ? ?RX bytes:0 (0.0 B) ?TX bytes:0 (0.0 B) > > xenbr0 ? ?Link encap:Ethernet ?HWaddr f0:de:f1:39:cb:60 > ? ? ? ? ?inet addr:10.0.2.211 ?Bcast:10.0.2.255 ?Mask:255.255.255.0 > ? ? ? ? ?inet6 addr: fe80::f2de:f1ff:fe39:cb60/64 Scope:Link > ? ? ? ? ?UP BROADCAST RUNNING MULTICAST ?MTU:1500 ?Metric:1 > ? ? ? ? ?RX packets:8950 errors:0 dropped:1 overruns:0 frame:0 > ? ? ? ? ?TX packets:1616 errors:0 dropped:0 overruns:0 carrier:0 > ? ? ? ? ?collisions:0 txqueuelen:0 > ? ? ? ? ?RX bytes:1919871 (1.8 MiB) ?TX bytes:378625 (369.7 KiB) > > root at topsail:~# ps ax | grep udev > ?303 ? ? ? ? ?Ss ? ? 0:00 udevd --daemon > ?1989 ? ? ? ? ?S ? ? ?0:00 udevd --daemon > ?4671 ? ? ? ? ?S ? ? ?0:00 udevd --daemon > > root at topsail:~# ls -l /etc/udev/rules.d/ > total 12 > -rw-r--r-- 1 root root 578 Feb 26 17:50 60-wacom.rules > -rw-r--r-- 1 root root 786 Jan 24 ?2011 70-persistent-cd.rules > -rw-r--r-- 1 root root 813 Jul 16 15:11 70-persistent-net.rules > lrwxrwxrwx 1 root root ?35 Aug ?3 13:51 xen-backend.rules -> /lib/udev/rules.d > /xen-backend.rules > lrwxrwxrwx 1 root root ?28 Aug ?3 14:39 xend.rules -> > /lib/udev/rules.d/xend.rules > lrwxrwxrwx 1 root root ?15 Jan 24 ?2011 z60_hdparm.rules -> ../hdparm.rules > > > > -- System Information: > Debian Release: wheezy/sid > ?APT prefers testing > ?APT policy: (500, 'testing') > Architecture: i386 (i686) > > Kernel: Linux 2.6.39-2-686-pae (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > xen-hypervisor-4.1-i386 depends on no packages. > > Versions of packages xen-hypervisor-4.1-i386 recommends: > ii ?xen-utils-4.1 ? ? ? ? ? ? ? ? 4.1.1-1 ? ?XEN administrative tools > > Versions of packages xen-hypervisor-4.1-i386 suggests: > pn ?xen-docs-4.1 ? ? ? ? ? ? ? ? ?<none> ? ? (no description available) > > -- no debconf information > > > > _______________________________________________ > Pkg-xen-devel mailing list > Pkg-xen-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xen-devel >-- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/
Maybe Matching Threads
- Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1
- domU's being killed - strange?
- DRBD VBD script not working in squeeze ?
- Re: Error: Device 0 (vif) could not be connected.Hotplugscripts not working
- Centos 5.2 using LVM -> DRBD 0.82 -> Xen Problems