thr3ads.net - Xen users - [Xen-users] (domU) Device 0 (vif) could not be connected. Hotplug scripts not working. [Jan 2006]

If this information is useful, please help other people find it:
Share via:

BugOne S

2006-Jan-30 11:58 UTC

[Xen-users] (domU) Device 0 (vif) could not be connected. Hotplug scripts not working.

Hi, i cant run domU, because of this error:

xen xen # xm create -c client1
Using config file "client1".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

my config file for the domU is:

kernel = "/boot/linux-2.6.12-xenU"
memory = 512
name = "domU"
# doesnt change error type if i uncomment or i comment the following line...
#vif = [ ''mac=aa:00:00:00:00:11, bridge=xenbr0'' ]
disk = [ ''phy:sda1,sda1,w'' ]
root = "/dev/sda1 ro"
extra = "4"

(like the default conf file...)

i also installed udev, hotplug, bridge-utils, sysfsutils like said in other 
thread with the same problem...
but nothing change...
what''s wrong?

/var/log/messages:

Jan 30 11:45:44 xen kernel: EXT3 FS on sda1, internal journal
Jan 30 11:45:46 xen uptimed: created bootid: 1138621512
Jan 30 11:45:47 xen kernel: tg3: eth0: Link is up at 100 Mbps, full duplex.
Jan 30 11:45:47 xen kernel: tg3: eth0: Flow control is off for TX and off 
for RX.
Jan 30 11:46:08 xen kernel: device vif0.0 entered promiscuous mode
Jan 30 11:46:08 xen kernel: bridge: can''t decode speed from peth0: 0
Jan 30 11:46:08 xen kernel: device peth0 entered promiscuous mode
Jan 30 11:46:08 xen kernel: xenbr0: port 1(vif0.0) entering learning state
Jan 30 11:46:08 xen kernel: xenbr0: topology change detected, propagating
Jan 30 11:46:08 xen kernel: xenbr0: port 1(vif0.0) entering forwarding state
Jan 30 11:46:10 xen kernel: tg3: peth0: Link is up at 100 Mbps, full duplex.
Jan 30 11:46:10 xen kernel: tg3: peth0: Flow control is off for TX and off 
for RX.
Jan 30 11:46:10 xen kernel: xenbr0: port 2(peth0) entering learning state
Jan 30 11:46:10 xen kernel: xenbr0: topology change detected, propagating
Jan 30 11:46:10 xen kernel: xenbr0: port 2(peth0) entering forwarding state


/var/log/xend.log:

[2006-01-30 11:41:24 xend.XendDomainInfo] DEBUG (XendDomainInfo:177) 
XendDomainInfo.create([''vm'', [''name'',
''ClientDiProva''], [''memory'',
''512''],
[''image'', [''linux'',
[''kernel'', ''/boot/linux-2.6.12-xenU''],
[''root'',
''/dev/sda1 ro''], [''args'',
''4''], [''vcpus'', ''1''],
[''vcpus'', ''1''], [''boot'',
''c''], [''nics'', ''2'']]],
[''device'', [''vbd'',
[''uname'', ''phy:sda1''],
[''dev'',
''sda1''], [''mode'', ''w'']]],
[''device'', [''vif'']],
[''device'', [''vif'']]])
[2006-01-30 11:41:24 xend.XendDomainInfo] DEBUG (XendDomainInfo:282) 
parseConfig: config is [''vm'', [''name'',
''ClientDiProva''], [''memory'',
''512''],
[''image'', [''linux'',
[''kernel'', ''/boot/linux-2.6.12-xenU''],
[''root'',
''/dev/sda1 ro''], [''args'',
''4''], [''vcpus'', ''1''],
[''vcpus'', ''1''], [''boot'',
''c''], [''nics'', ''2'']]],
[''device'', [''vbd'',
[''uname'', ''phy:sda1''],
[''dev'',
''sda1''], [''mode'', ''w'']]],
[''device'', [''vif'']],
[''device'', [''vif'']]]
[2006-01-30 11:41:24 xend.XendDomainInfo] DEBUG (XendDomainInfo:374) 
parseConfig: result is {''ssidref'': None,
''uuid'': None, ''on_crash'': None,
''on_reboot'': None, ''image'':
[''linux'', [''kernel'',
''/boot/linux-2.6.12-xenU''],
[''root'', ''/dev/sda1 ro''],
[''args'', ''4''], [''vcpus'',
''1''], [''vcpus'', ''1''],
[''boot'', ''c''], [''nics'',
''2'']], ''on_poweroff'': None,
''cpus'': None, ''name'':
''ClientDiProva'', ''backend'': [],
''vcpus'': 1, ''cpu_weight'': None,
''vcpu_avail'': None, ''memory'': 512,
''device'': [(''vbd'', [''vbd'',
[''uname'',
''phy:sda1''], [''dev'',
''sda1''], [''mode'', ''w'']]),
(''vif'', [''vif'']), (''vif'',
[''vif''])], ''bootloader'': None,
''cpu'': None, ''maxmem'': None}
[2006-01-30 11:41:24 xend.XendDomainInfo] DEBUG (XendDomainInfo:1129) 
XendDomainInfo.construct: None 0
[2006-01-30 11:41:24 xend.XendDomainInfo] DEBUG (XendDomainInfo:1161) 
XendDomainInfo.initDomain: 9 1.0
[2006-01-30 11:41:24 xend] DEBUG (balloon:84) Balloon: free 1547; need 513; 
done.
[2006-01-30 11:41:24 xend] INFO (image:132) buildDomain os=linux dom=9 
vcpus=1
[2006-01-30 11:41:24 xend] DEBUG (image:170) dom            = 9
[2006-01-30 11:41:24 xend] DEBUG (image:171) image          = 
/boot/linux-2.6.12-xenU
[2006-01-30 11:41:24 xend] DEBUG (image:172) store_evtchn   = 1
[2006-01-30 11:41:24 xend] DEBUG (image:173) console_evtchn = 2
[2006-01-30 11:41:24 xend] DEBUG (image:174) cmdline        =  
root=/dev/sda1 ro 4
[2006-01-30 11:41:24 xend] DEBUG (image:175) ramdisk        [2006-01-30 11:41:24
xend] DEBUG (image:176) vcpus          = 1
[2006-01-30 11:41:24 xend] DEBUG (DevController:104) DevController: writing 
{''virtual-device'': ''2049'',
''backend-id'': ''0'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/9/2049''} to
/local/domain/9/device/vbd/2049.
[2006-01-30 11:41:24 xend] DEBUG (DevController:106) DevController: writing 
{''domain'': ''ClientDiProva'',
''frontend'':
''/local/domain/9/device/vbd/2049'',
''dev'': ''sda1'', ''state'':
''1'', ''params'': ''sda1'',
''mode'': ''w'',
''frontend-id'':
''9'', ''type'': ''phy''} to
/local/domain/0/backend/vbd/9/2049.
[2006-01-30 11:41:24 xend] DEBUG (DevController:104) DevController: writing 
{''backend-id'': ''0'', ''mac'':
''00:16:3e:10:e5:5f'', ''handle'':
''0'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vif/9/0''} to
/local/domain/9/device/vif/0.
[2006-01-30 11:41:24 xend] DEBUG (DevController:106) DevController: writing 
{''mac'': ''00:16:3e:10:e5:5f'',
''state'': ''1'', ''handle'':
''0'', ''script'':
''/etc/xen/scripts/vif-bridge'',
''frontend-id'': ''9'',
''domain'':
''ClientDiProva'', ''frontend'':
''/local/domain/9/device/vif/0''} to
/local/domain/0/backend/vif/9/0.
[2006-01-30 11:41:24 xend] DEBUG (DevController:104) DevController: writing 
{''backend-id'': ''0'', ''mac'':
''00:16:3e:1d:40:8e'', ''handle'':
''1'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vif/9/1''} to
/local/domain/9/device/vif/1.
[2006-01-30 11:41:24 xend] DEBUG (DevController:106) DevController: writing 
{''mac'': ''00:16:3e:1d:40:8e'',
''state'': ''1'', ''handle'':
''1'', ''script'':
''/etc/xen/scripts/vif-bridge'',
''frontend-id'': ''9'',
''domain'':
''ClientDiProva'', ''frontend'':
''/local/domain/9/device/vif/1''} to
/local/domain/0/backend/vif/9/1.
[2006-01-30 11:41:24 xend.XendDomainInfo] DEBUG (XendDomainInfo:661) Storing 
VM details: {''ssidref'': ''0'',
''uuid'':
''236d893e-86f21df9-e5271fb6-cdbf77db'',
''on_reboot'': ''restart'',
''start_time'': ''1138621284.98'',
''on_poweroff'':
''destroy'', ''name'':
''ClientDiProva'', ''vcpus'':
''1'', ''vcpu_avail'': ''1'',
''memory'': ''512'',
''on_crash'': ''restart'',
''image'': "(linux (kernel
/boot/linux-2.6.12-xenU) (root ''/dev/sda1 ro'') (args 4) (vcpus
1) (vcpus 1)
(boot c) (nics 2))", ''maxmem'': ''512''}
[2006-01-30 11:41:24 xend.XendDomainInfo] DEBUG (XendDomainInfo:686) Storing 
domain details: {''console/ring-ref'':
''902087'', ''console/port'':
''2'', ''name'':
''ClientDiProva'', ''console/limit'':
''1048576'', ''vm'':
''/vm/236d893e-86f21df9-e5271fb6-cdbf77db'',
''domid'': ''9'',
''cpu/0/availability'': ''online'',
''memory/target'': ''524288'',
''store/ring-ref'':
''902088'', ''store/port'':
''1''}
[2006-01-30 11:41:25 xend] DEBUG (DevController:133) Waiting for devices 
vif.
[2006-01-30 11:41:25 xend] DEBUG (DevController:139) Waiting for 0.
[2006-01-30 11:41:25 xend] DEBUG (DevController:409) hotplugStatusCallback 
/local/domain/0/backend/vif/9/0/hotplug-status.
[2006-01-30 11:41:35 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 72, in 
op_wait_for_devices
    return self.dom.waitForDevices()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1349, in 
waitForDevices
    self.waitForDevices_(c)
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 977, in 
waitForDevices_
    return self.getDeviceController(deviceClass).waitForDevices()
  File "/usr/lib/python/xen/xend/server/DevController.py", line 135,
in
waitForDevices
    return map(self.waitForDevice, self.deviceIDs())
  File "/usr/lib/python/xen/xend/server/DevController.py", line 145,
in
waitForDevice
    raise VmError("Device %s (%s) could not be connected. "
VmError: Device 0 (vif) could not be connected. Hotplug scripts not working.


thank you for the help

Enrico

_________________________________________________________________
Blocca le pop-up pubblicitarie con MSN Toolbar! http://toolbar.msn.it/


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

CJ van den Berg

2006-Jan-30 12:19 UTC

head link

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

On Mon, Jan 30, 2006 at 12:58:36PM +0100, BugOne S
wrote:> Hi, i cant run domU, because of this error:
> 
> xen xen # xm create -c client1
> Using config file "client1".
> Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
I have this problem too. In my case it seems to be the very short timeout
for starting backend devices. Basically, AFAICT, all vif- scripts must
finish within 10 seconds or the xm create command is aborted.

In my case I do a lot of dynamic configuration in vif-nat and it often takes
much longer than 10 seconds, especially if I''m running a kernel build
or
something in the background.

You can see if this is the same problem you''re having by changing the
timeout DEVICE_CREATE_TIMEOUT in
/usr/lib/python/xen/xend/server/DevController.py (probably around line 28)
to something larger than 10.

-- 
CJ van den Berg

mailto:cj@vdbonline.com
  xmpp:cj@vdbonline.com
   sip:8918316@sipgate.de

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

BugOne S

2006-Jan-30 19:05 UTC

head link

Re: [Xen-users] (domU) Device 0 (vif) could not be connected. Hotplugscripts not working.

nothing done.... any other suggestion?
i really dont know what''s wrong!

>From: CJ van den Berg <cj@vdbonline.com>
>To: xen-users@lists.xensource.com
>Subject: Re: [Xen-users] (domU) Device 0 (vif) could not be connected. 
>Hotplugscripts not working.
>Date: Mon, 30 Jan 2006 13:19:05 +0100
>
>On Mon, Jan 30, 2006 at 12:58:36PM +0100, BugOne S wrote:
> > Hi, i cant run domU, because of this error:
> >
> > xen xen # xm create -c client1
> > Using config file "client1".
> > Error: Device 0 (vif) could not be connected. Hotplug scripts not 
>working.
>
>I have this problem too. In my case it seems to be the very short timeout
>for starting backend devices. Basically, AFAICT, all vif- scripts must
>finish within 10 seconds or the xm create command is aborted.
>
>In my case I do a lot of dynamic configuration in vif-nat and it often 
>takes
>much longer than 10 seconds, especially if I''m running a kernel
build or
>something in the background.
>
>You can see if this is the same problem you''re having by changing
the
>timeout DEVICE_CREATE_TIMEOUT in
>/usr/lib/python/xen/xend/server/DevController.py (probably around line 28)
>to something larger than 10.
>
>--
>CJ van den Berg
>
>mailto:cj@vdbonline.com
>   xmpp:cj@vdbonline.com
>    sip:8918316@sipgate.de
>
>_______________________________________________
>Xen-users mailing list
>Xen-users@lists.xensource.com
>http://lists.xensource.com/xen-users
_________________________________________________________________
SMS + facili! Prova un nuovo modo, più comodo, di inviare SMS! 
http://join2.msn.com/?page=messenger/mm&ST=1&pgmarket=it-it


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

Xen users - Jan 2006 - (domU) Device 0 (vif) could not be connected. Hotplug scripts not working.

[Xen-users] (domU) Device 0 (vif) could not be connected. Hotplug scripts not working.

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

Re: [Xen-users] (domU) Device 0 (vif) could not be connected. Hotplugscripts not working.