jd
2007-Jun-19 07:38 UTC
[Xen-users] Xen 3.1 Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
I get the error while starting hvm doms. Any workarounds... suggestions.. Thanks /Jd Some thiings that might be useful are cut-pasted below. ifconfig -a udevmonitor output (as suggested in prev posts) qemu-dm log xend.log xend-debug does not seem to have anything interesting. ifconfig -a ==========eth0 Link encap:Ethernet HWaddr 00:0F:EA:53:5C:79 inet addr:192.168.12.103 Bcast:192.168.12.255 Mask:255.255.255.0 inet6 addr: fe80::20f:eaff:fe53:5c79/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3616 errors:0 dropped:0 overruns:0 frame:0 TX packets:1866 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2012466 (1.9 MiB) TX bytes:351189 (342.9 KiB) Interrupt:16 Base address:0xc000 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:1682 errors:0 dropped:0 overruns:0 frame:0 TX packets:1682 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3286556 (3.1 MiB) TX bytes:3286556 (3.1 MiB) xenbr0 Link encap:Ethernet HWaddr 00:0F:EA:53:5C:79 inet addr:192.168.12.103 Bcast:192.168.12.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3598 errors:0 dropped:0 overruns:0 frame:0 TX packets:1824 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1955948 (1.8 MiB) TX bytes:345201 (337.1 KiB) ====== udev monitor output ===udevmonitor prints the received event from the kernel [UEVENT] and the event which udev sends out after rule processing [UDEV] UEVENT[1182238470.444318] add@/devices/xen-backend/vfb-8-0 UDEV [1182238470.451658] add@/devices/xen-backend/vfb-8-0 UEVENT[1182238470.475845] add@/devices/xen-backend/vbd-8-768 UDEV [1182238470.475845] add@/devices/xen-backend/vbd-8-768 UEVENT[1182238470.498735] add@/devices/xen-backend/vbd-8-5632 UDEV [1182238470.498735] add@/devices/xen-backend/vbd-8-5632 UEVENT[1182238470.543309] add@/devices/xen-backend/vif-8-0 UDEV [1182238470.543309] add@/devices/xen-backend/vif-8-0 UEVENT[1182238470.551555] add@/class/net/tap0 UDEV [1182238470.578702] add@/class/net/tap0 UEVENT[1182238470.651827] add@/devices/xen-backend/console-8-0 UDEV [1182238470.667398] add@/devices/xen-backend/console-8-0 UEVENT[1182238570.888056] remove@/class/net/tap0 UDEV [1182238570.900534] remove@/class/net/tap0 ====================== qemu-dm log ==========domid: 8 qemu: the number of cpus is 1 Watching /local/domain/8/logdirty/next-active qemu_map_cache_init nr_buckets = 4000 shared page at pfn ffff buffered io page at pfn fffd Time offset set 0 xs_read(): vncpasswd get error. /vm/bf8b49f7-03d0-7311-ab3f-cc1bb4719bba/vncpasswd. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Triggered log-dirty buffer switch ============xend.log [2007-06-19 00:34:30 3694] DEBUG (XendDomainInfo:824) Storing domain details: {''console/port'': ''3'', ''name'': ''ubuntu-6'', ''console/limit'': ''1048576'', ''vm'': ''/vm/bf8b49f7-03d0-7311-ab3f-cc1bb4719bba'', ''domid'': ''8'', ''image/suspend-cancel'': ''1'', ''cpu/0/availability'': ''online'', ''memory/target'': ''262144'', ''control/platform-feature-multiprocessor-suspend'': ''1'', ''store/ring-ref'': ''65534'', ''store/port'': ''2''} [2007-06-19 00:34:30 3694] DEBUG (DevController:115) DevController: writing {''state'': ''1'', ''backend-id'': ''0'', ''backend'': ''/local/domain/0/backend/console/8/0''} to /local/domain/8/device/console/0. [2007-06-19 00:34:30 3694] DEBUG (DevController:117) DevController: writing {''domain'': ''ubuntu-6'', ''protocol'': ''vt100'', ''uuid'': ''6559d304-1ba1-b752-f2c6-9a237ef4d6b2'', ''frontend'': ''/local/domain/8/device/console/0'', ''state'': ''1'', ''location'': ''3'', ''online'': ''1'', ''frontend-id'': ''8''} to /local/domain/0/backend/console/8/0. [2007-06-19 00:34:30 3694] DEBUG (XendDomainInfo:908) XendDomainInfo.handleShutdownWatch [2007-06-19 00:34:30 3694] DEBUG (DevController:148) Waiting for devices vif. [2007-06-19 00:34:30 3694] DEBUG (DevController:153) Waiting for 0. [2007-06-19 00:34:30 3694] DEBUG (DevController:539) hotplugStatusCallback /local/domain/0/backend/vif/8/0/hotplug-status. [2007-06-19 00:36:10 3694] DEBUG (XendDomainInfo:1660) XendDomainInfo.destroy: domid=8 [2007-06-19 00:36:10 3694] DEBUG (XendDomainInfo:1677) XendDomainInfo.destroyDomain(8) ____________________________________________________________________________________ Got a little couch potato? Check out fun summer activities for kids. http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Possibly Parallel Threads
- Device 0 (vif) could not be connected. Hotplug scripts not working.
- Re: [Xen-users] Error: Device 0 (vif) could not be connected. Backend device not found.
- Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures
- XM create issue: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
- XM create issue: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.