RE: [Xen-users] Error "Device 0 (vif) could not be connected"

["Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>]

I think you have a line that say "vif=.." in your DomU config. Make that
line vif0 or delete it. That should get you going. Though I am not sure
if this is a bug.

Cheers,
Aravindh

> -----Original Message-----
> From: Mark Williamson [mailto:mark.williamson@xxxxxxxxxxxx]
> Sent: Friday, November 04, 2005 11:32 AM
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Cc: ewan@xxxxxxxxxxxxx; wei huang
> Subject: Re: [Xen-users] Error "Device 0 (vif) could not be connected"
> 
> I also saw this error (on yesterday's pull), haven't had to diagnose
it
> yet.
> 
> Apparently this message is something to do with Xend detecting a
failure /
> problem with the hotplug scripts...  Ewan (cc'ed) suggested I check my
> hotplug / udev setup was working and that I look for hotplug-related
> errors
> in the main syslog.
> 
> HTH,
> Mark
> 
> On Friday 04 November 2005 16:21, wei huang wrote:
> > Hi,
> >
> > I have a problem to start domU on my server.
> >
> > Everything upto "xm create" look normal. However, it pops up saying
> > the above error message when I try to create domU.
> >
> > I verified that xend has started and vif device is created, here is
the
> > output of ifconfig after xend start:
> >
> > eth0      Link encap:Ethernet  HWaddr 00:30:48:51:65:A7
> >           inet addr:192.168.103.5  Bcast:192.168.255.255
> Mask:255.255.0.0
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:28742 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:11075 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:28955962 (27.6 MiB)  TX bytes:2259219 (2.1 MiB)
> >
> > lo        Link encap:Local Loopback
> >           inet addr:127.0.0.1  Mask:255.0.0.0
> >           UP LOOPBACK RUNNING  MTU:16436  Metric:1
> >           RX packets:26 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:2072 (2.0 KiB)  TX bytes:2072 (2.0 KiB)
> >
> > peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> >           UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
> >           RX packets:29448 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:11658 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:1000
> >           RX bytes:29103901 (27.7 MiB)  TX bytes:2346856 (2.2 MiB)
> >
> > vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:11076 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:28742 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:2260133 (2.1 MiB)  TX bytes:28955962 (27.6 MiB)
> >
> > xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:949 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:138255 (135.0 KiB)  TX bytes:0 (0.0 b)
> >
> > However, this is the error message when I try to start domU:
> > #c4xen# /etc/xen> sudo xm create -c as4_conf
> > Password:
> > Using config file "as4_conf".
> > Error: Error creating domain: Device 0 (vif) could not be connected.
> > Backend device not found!
> >
> > There is nothing abnormal in dmesg and xm dmesg. But here is the
trace
> of
> > xm log:
> >
> > [2005-11-04 11:08:02 xend.XendDomainInfo] DEBUG (XendDomainInfo:147)
> > XendDomainInfo.create(['vm', ['name', 'domu-as4-1'], ['memory',
'256'],
> > ['image', ['linux', ['kernel', '/boot/xen-3.0/vmlinuz-2.6.12-xenU'],
> > ['ip',
'192.168.170.5:1.2.3.4:192.168.1.1:255.255.0.0:c4xen:eth0:off'],
> > ['root', '/dev/hda1 ro'], ['args', '3'], ['vcpus', '1'], ['vcpus',
'1'],
> > ['boot', 'c'], ['display', 'localhost:10.0']]], ['device', ['vbd',
> > ['uname', 'phy:hdb3'], ['dev', 'hda1'], ['mode', 'w']]], ['device',
> > ['vif', ['mac', 'aa:00:00:00:01:05'], ['bridge', 'xenbr0']]]])
> > [2005-11-04 11:08:02 xend.XendDomainInfo] DEBUG (XendDomainInfo:250)
> > parseConfig: config is ['vm', ['name', 'domu-as4-1'], ['memory',
'256'],
> > ['image', ['linux', ['kernel', '/boot/xen-3.0/vmlinuz-2.6.12-xenU'],
> > ['ip',
'192.168.170.5:1.2.3.4:192.168.1.1:255.255.0.0:c4xen:eth0:off'],
> > ['root', '/dev/hda1 ro'], ['args', '3'], ['vcpus', '1'], ['vcpus',
'1'],
> > ['boot', 'c'], ['display', 'localhost:10.0']]], ['device', ['vbd',
> > ['uname', 'phy:hdb3'], ['dev', 'hda1'], ['mode', 'w']]], ['device',
> > ['vif', ['mac', 'aa:00:00:00:01:05'], ['bridge', 'xenbr0']]]]
> > [2005-11-04 11:08:02 xend.XendDomainInfo] DEBUG (XendDomainInfo:308)
> > parseConfig: result is {'ssidref': None, 'name': 'domu-as4-1',
> > 'on_reboot': None, 'maxmem': None, 'on_poweroff': None, 'mem_kb':
None,
> > 'maxmem_kb': None, 'on_crash': None, 'backend': [], 'vcpus': 1,
> > 'cpu_weight': None, 'vcpu_avail': None, 'memory': 256, 'device':
> [('vbd',
> > ['vbd', ['uname', 'phy:hdb3'], ['dev', 'hda1'], ['mode', 'w']]),
('vif',
> > ['vif', ['mac', 'aa:00:00:00:01:05'], ['bridge', 'xenbr0']])],
> > 'bootloader': None, 'image': ['linux', ['kernel',
> > '/boot/xen-3.0/vmlinuz-2.6.12-xenU'], ['ip',
> > '192.168.170.5:1.2.3.4:192.168.1.1:255.255.0.0:c4xen:eth0:off'],
> ['root',
> > '/dev/hda1 ro'], ['args', '3'], ['vcpus', '1'], ['vcpus', '1'],
['boot',
> > 'c'], ['display', 'localhost:10.0']], 'cpu': None, 'uuid': None}
> > [2005-11-04 11:08:02 xend.XendDomainInfo] DEBUG
(XendDomainInfo:1047)
> > XendDomainInfo.construct: None 0
> > [2005-11-04 11:08:02 xend.XendDomainInfo] DEBUG
(XendDomainInfo:1077)
> > XendDomainInfo.initDomain: 6 262144 1.0
> > [2005-11-04 11:08:02 xend] INFO (image:131) buildDomain os=linux
dom=6
> > vcpus=1
> > [2005-11-04 11:08:02 xend] DEBUG (image:169) dom            = 6
> > [2005-11-04 11:08:02 xend] DEBUG (image:170) image          =
> > /boot/xen-3.0/vmlinuz-2.6.12-xenU
> > [2005-11-04 11:08:02 xend] DEBUG (image:171) store_evtchn   = 1
> > [2005-11-04 11:08:02 xend] DEBUG (image:172) console_evtchn = 2
> > [2005-11-04 11:08:02 xend] DEBUG (image:173) cmdline        =
> > ip=192.168.170.5:1.2.3.4:192.168.1.1:255.255.0.0:c4xen:eth0:off
> > root=/dev/hda1 ro 3
> > [2005-11-04 11:08:02 xend] DEBUG (image:174) ramdisk        =
> > [2005-11-04 11:08:02 xend] DEBUG (image:175) vcpus          = 1
> > [2005-11-04 11:08:02 xend] DEBUG (DevController:256) DevController:
> > writing {'virtual-device': '769', 'backend-id': '0', 'backend':
> > '/local/domain/0/backend/vbd/6/769'} to
/local/domain/6/device/vbd/769.
> > [2005-11-04 11:08:02 xend] DEBUG (DevController:258) DevController:
> > writing {'domain': 'domu-as4-1', 'params': 'hdb3', 'frontend-id':
'6',
> > 'type': 'phy', 'dev': 'hda1', 'frontend':
> > '/local/domain/6/device/vbd/769'} to
/local/domain/0/backend/vbd/6/769.
> > [2005-11-04 11:08:02 xend] DEBUG (DevController:256) DevController:
> > writing {'backend-id': '0', 'mac': 'aa:00:00:00:01:05', 'handle':
'0',
> > 'backend': '/local/domain/0/backend/vif/6/0'} to
> > /local/domain/6/device/vif/0.
> > [2005-11-04 11:08:02 xend] DEBUG (DevController:258) DevController:
> > writing {'bridge': 'xenbr0', 'mac': 'aa:00:00:00:01:05', 'handle':
'0',
> > 'script': '/etc/xen/scripts/vif-bridge', 'frontend-id': '6',
'domain':
> > 'domu-as4-1', 'frontend': '/local/domain/6/device/vif/0'} to
> > /local/domain/0/backend/vif/6/0.
> > [2005-11-04 11:08:03 xend.XendDomainInfo] ERROR (XendDomainInfo:158)
> > Domain construction failed
> > Traceback (most recent call last):
> >   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 152, in
create
> >     vm.initDomain()
> >   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1109, in
> > initDomain
> >     self.createDevices()
> >   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1222, in
> > createDevices
> >     self.createDevice(n, c)
> >   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 893, in
> > createDevice
> >     return
self.getDeviceController(deviceClass).createDevice(devconfig)
> >   File "/usr/lib/python/xen/xend/server/DevController.py", line 72,
in
> > createDevice
> >     raise VmError( ("Device %s (%s) could not be connected. "
> > VmError: Device 0 (vif) could not be connected. Backend device not
> found!
> > [2005-11-04 11:08:03 xend.XendDomainInfo] DEBUG
(XendDomainInfo:1156)
> > XendDomainInfo.destroy: domid=6
> > [2005-11-04 11:08:03 xend.XendDomainInfo] DEBUG
(XendDomainInfo:1164)
> > XendDomainInfo.destroyDomain(6)
> > [2005-11-04 11:08:03 xend] ERROR (SrvBase:87) Request create 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/SrvDomainDir.py", line 82,
in
> > op_create
> >     raise XendError("Error creating domain: " + str(ex))
> > XendError: Error creating domain: Device 0 (vif) could not be
connected.
> > Backend device not found!
> >
> > Would you please instruct what might be the problem?
> >
> > Thanks
> >
> >
> > Regards,
> > Wei Huang
> >
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> 


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