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: Thu, 17 Nov 2005 17:02:49 +0000
Delivery-date: Thu, 17 Nov 2005 17:02:53 +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


hien1@xxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




------- Additional Comments From hien1@xxxxxxxxxx  2005-11-17 17:02 -------
I reopened the bug since it still happended with :

changeset:   7826:9bf6f907b3ff
tag:         tip
user:        kaf24@xxxxxxxxxxxxxxxxxxxx
date:        Wed Nov 16 04:29:52 2005 +0100
summary:     Trivial coding style fix.

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

[root@x335-hien1 xen]# tail -30 /var/log/xend.log
[2005-11-17 10:25:32 xend] DEBUG (image:174) cmdline        =  root=/dev/sde1
roro selinux=0 3
[2005-11-17 10:25:32 xend] DEBUG (image:175) ramdisk        =
[2005-11-17 10:25:32 xend] DEBUG (image:176) vcpus          = 1
[2005-11-17 10:25:32 xend] DEBUG (blkif:24) exception looking up device number
for /dev/sde1: [Errno 2] No such file or directory: '/dev/sde1'
[2005-11-17 10:25:32 xend] DEBUG (DevController:302) DevController: writing
{'virtual-device': '2113', 'backend-id': '0', 'state': '1', 'backend':
'/local/domain/0/backend/vbd/23/2113'} to /local/domain/23/device/vbd/2113.
[2005-11-17 10:25:32 xend] DEBUG (DevController:304) DevController: writing
{'domain': 'x335-rhel4-vm3', 'params': '/FC4-FILEVBD4/FC4-32-filevbd4',
'frontend-id': '23', 'type': 'file', 'state': '1', 'dev': '/dev/sde1',
'frontend': '/local/domain/23/device/vbd/2113'} to
/local/domain/0/backend/vbd/23/2113.
[2005-11-17 10:25:32 xend] DEBUG (DevController:302) DevController: writing
{'virtual-device': '2096', 'backend-id': '0', 'state': '1', 'backend':
'/local/domain/0/backend/vbd/23/2096'} to /local/domain/23/device/vbd/2096.
[2005-11-17 10:25:32 xend] DEBUG (DevController:304) DevController: writing
{'domain': 'x335-rhel4-vm3', 'params': 'sdd', 'frontend-id': '23', 'type':
'phy', 'state': '1', 'dev': 'sdd', 'frontend':
'/local/domain/23/device/vbd/2096'} to /local/domain/0/backend/vbd/23/2096.
[2005-11-17 10:25:32 xend] DEBUG (DevController:302) DevController: writing
{'backend-id': '0', 'mac': 'AA:00:00:17:12:6D', 'handle': '0', 'state': '1',
'backend': '/local/domain/0/backend/vif/23/0'} to /local/domain/23/device/vif/0.
[2005-11-17 10:25:32 xend] DEBUG (DevController:304) DevController: writing
{'domain': 'x335-rhel4-vm3', 'handle': '0', 'script': 
'/etc/xen/scripts/vif-route',
'ip': '9.3.189.251', 'state': '1', 'frontend': '/local/domain/23/device/vif/0',
'mac': 'AA:00:00:17:12:6D', 'frontend-id': '23'} to
/local/domain/0/backend/vif/23/0.
[2005-11-17 10:25:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:557) Storing VM
details: {'ssidref': '0', 'uuid': '358df4d7-27f6-cc69-21e1-11a97b441f46',
'on_reboot': 'restart', 'image': "(linux (kernel /boot/vmlinuz-2.6-xenU) (root
'/dev/sde1 ro') (args 'ro selinux=0 3') (vcpus 1) (vcpus 1) (boot c) (display
localhost:10.0))", 'on_poweroff': 'destroy', 'name': 'x335-rhel4-vm3', 'vcpus':
'1', 'vcpu_avail': '1', 'memory': '512', 'on_crash': 'restart', 'maxmem': '512'}
[2005-11-17 10:25:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:582) Storing
domain details: {'console/ring-ref': '122612', 'console/port': '2', 'name':
'x335-rhel4-vm3', 'console/limit': '1048576', 'vm':
'/vm/358df4d7-27f6-cc69-21e1-11a97b441f46', 'domid': '23', 'cpu/0/availability':
'online', 'memory/target': '524288', 'store/ring-ref': '122613', 'store/port': 
'1'}
[2005-11-17 10:25:32 xend] DEBUG (DevController:88) Waiting for devices vif.
[2005-11-17 10:25:32 xend] DEBUG (DevController:94) Waiting for 0.
[2005-11-17 10:25:32 xend] DEBUG (DevController:361) hotplugStatusCallback
/local/domain/0/backend/vif/23/0/hotplug-status.
[2005-11-17 10:25:37 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 1205, in
waitForDevices    self.waitForDevices_(c)
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 864, in
waitForDevices_    return self.getDeviceController(deviceClass).waitForDevices()
  File "/usr/lib/python/xen/xend/server/DevController.py", line 90, in
waitForDevices
    return map(self.waitForDevice, self.deviceIDs())
  File "/usr/lib/python/xen/xend/server/DevController.py", line 100, in
waitForDevice
    raise VmError("Device %s (%s) could not be connected. "
VmError: Device 0 (vif) could not be connected. Hotplug scripts not working


-- 
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