WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 392] domU cannot start: Device 0 (vif) could not be conn

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 392] domU cannot start: Device 0 (vif) could not be connected
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 14 Nov 2005 21:58:36 +0000
Delivery-date: Mon, 14 Nov 2005 21:58:40 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=392





------- Additional Comments From hien1@xxxxxxxxxx  2005-11-14 21:58 -------
Tried new built today and domU couldn't start with the same errors:

[root@x335-hien1 xen]# xm create -c x335-hien1-vm4.cfg
Using config file "x335-hien1-vm4.cfg".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working

[root@x335-hien1 xen]# cd /xen-unstable.hg
[root@x335-hien1 xen-unstable.hg]# hg tip
changeset:   7793:090e44133d40
tag:         tip
user:        kaf24@xxxxxxxxxxxxxxxxxxxx
date:        Mon Nov 14 11:13:38 2005 +0100
summary:     Use make_lowmem_page_readonly/writable() in preference to the
------------------
xend.log showed:

[root@x335-hien1 xen-unstable.hg]# tail -30 /var/log/xend.log
[2005-11-14 15:44:54 xend] DEBUG (image:171) image          = 
/boot/vmlinuz-2.6-xenU
[2005-11-14 15:44:54 xend] DEBUG (image:172) store_evtchn   = 1
[2005-11-14 15:44:54 xend] DEBUG (image:173) console_evtchn = 2
[2005-11-14 15:44:54 xend] DEBUG (image:174) cmdline        =  root=/dev/sdb1 ro
ro selinux=0 3
[2005-11-14 15:44:54 xend] DEBUG (image:175) ramdisk        =
[2005-11-14 15:44:54 xend] DEBUG (image:176) vcpus          = 1
[2005-11-14 15:44:54 xend] DEBUG (DevController:286) DevController: writing
{'virtual-device': '2065', 'backend-id': '0', 'state': '1', 'backend':
'/local/domain/0/backend/vbd/1/2065'} to /local/domain/1/device/vbd/2065.
[2005-11-14 15:44:54 xend] DEBUG (DevController:288) DevController: writing
{'domain': 'x335-hien1-vm4', 'params': '/FC4-FILEVBD4/FC4-32-filevbd4',
'frontend-id': '1', 'type': 'file', 'state': '1', 'dev': 'sdb1', 'frontend':
'/local/domain/1/device/vbd/2065'} to /local/domain/0/backend/vbd/1/2065.
[2005-11-14 15:44:54 xend] DEBUG (DevController:286) DevController: writing
{'backend-id': '0', 'mac': 'AA:00:00:17:12:6A', 'handle': '0', 'state': '1',
'backend': '/local/domain/0/backend/vif/1/0'} to /local/domain/1/device/vif/0.
[2005-11-14 15:44:54 xend] DEBUG (DevController:288) DevController: writing
{'domain': 'x335-hien1-vm4', 'handle': '0', 'script': 
'/etc/xen/scripts/vif-route',
'ip': '10.8.1.2', 'state': '1', 'frontend': '/local/domain/1/device/vif/0',
'mac': 'AA:00:00:17:12:6A', 'frontend-id': '1'} to 
/local/domain/0/backend/vif/1/0.
[2005-11-14 15:44:54 xend.XendDomainInfo] DEBUG (XendDomainInfo:549) Storing VM
details: {'ssidref': '0', 'uuid': '82e21de7-5b53-e9ed-409b-e73ae344b06e',
'on_reboot': 'restart', 'image': "(linux (kernel /boot/vmlinuz-2.6-xenU) (root
'/dev/sdb1 ro') (args 'ro selinux=0 3') (vcpus 1) (vcpus 1) (boot c) (display
localhost:10.0))", 'on_poweroff': 'destroy', 'name': 'x335-hien1-vm4', 'vcpus':
'1', 'vcpu_avail': '1', 'memory': '1024', 'on_crash': 'restart', 'maxmem': 
'1024'}
[2005-11-14 15:44:54 xend.XendDomainInfo] DEBUG (XendDomainInfo:574) Storing
domain details: {'console/ring-ref': '122705', 'console/port': '2', 'name':
'x335-hien1-vm4', 'console/limit': '1048576', 'vm':
'/vm/82e21de7-5b53-e9ed-409b-e73ae344b06e', 'domid': '1', 'cpu/0/availability':
'online', 'memory/target': '1048576', 'store/ring-ref': '122706', 'store/port': 
'1'}
[2005-11-14 15:44:54 xend] DEBUG (DevController:82) Waiting for devices vif.
[2005-11-14 15:44:54 xend] DEBUG (DevController:88) Waiting for 0.
[2005-11-14 15:44:59 xend] ERROR (SrvBase:87) Request wait_for_devices failed.
Traceback (most recent call last):
  File "/usr/lib/python/xen/web/SrvBase.py", line 85, in perform
    return op_method(op, req)
  File "/usr/lib/python/xen/xend/server/SrvDomain.py", line 68, in
op_wait_for_devices
    return self.dom.waitForDevices()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1200, in 
waitForDevices
    self.waitForDevices_(c)
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 856, in 
waitForDevices_
    return self.getDeviceController(deviceClass).waitForDevices()
  File "/usr/lib/python/xen/xend/server/DevController.py", line 84, in
waitForDevices
    return map(self.waitForDevice, self.deviceIDs())
  File "/usr/lib/python/xen/xend/server/DevController.py", line 93, in 
waitForDevice
    raise VmError( ("Device %s (%s) could not be connected. "
VmError: Device 0 (vif) could not be connected. Hotplug scripts not working
[2005-11-14 15:44:59 xend] DEBUG (DevController:309) hotplugStatus 0
-------------

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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