thr3ads.net - Xen users - [Xen-users] Networking Questions [Nov 2005]

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

Steven Anderson

2005-Nov-04 14:58 UTC

[Xen-users] Networking Questions

Hello:

For the first time I have setup Xen. Using Fedora Core
4 and Xen Unstable using 2.6.12-1.1454 xen kernel. I
have installed a guest of fedora for my first
experiment.

What I dont really understand (although am a cisco
certified WAN engineer) is the networking components
of RedHat and Xen. 

I want to understand virtual IP''s Bridging, NAT and
things like that from a linux point of view that are
relative to Xen. Can anyone point me to good documents
that are relative and applicable to fedora core 4 and
Xen 3.0?

Thanks!

Steve


		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

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

wei huang

2005-Nov-04 16:21 UTC

head link

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

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@lists.xensource.com
http://lists.xensource.com/xen-users

Mark Williamson

2005-Nov-04 16:32 UTC

head link

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@lists.xensource.com
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

wei huang

2005-Nov-04 16:46 UTC

head link

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

Wow! Thanks for the quick response!

I will try to check these. And I will appreciate if you can keep me
updated once you have a change to look into it.

Thanks again!

Regards,
Wei Huang

On Fri, 4 Nov 2005, Mark Williamson wrote:
> 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@lists.xensource.com
> > http://lists.xensource.com/xen-users
>

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

wei huang

2005-Nov-04 16:59 UTC

head link

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

Hi Mark,

Actually this is my /etc/udev/scripts/hotplug.dev

if [ "$INTERFACE" = "$DEVNAME" ]; then
        exit 0
fi

# ok, we have renamed this device, so let''s set $INTERFACE to the new
name
# and call the network hotplug script to handle it properly...
INTERFACE=$DEVNAME
export INTERFACE
if [ -f /etc/hotplug.d/default/default.hotplug ]; then
        exec /etc/hotplug.d/default/default.hotplug net
fi

I think this is just Linux AS4 default scripts ...

By the way, do you the error only on yesterday''s pull? If this is so,
may
be I can try some older version?

Thank you!

Regards,
Wei Huang



On Fri, 4 Nov 2005, Mark Williamson wrote:
> 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@lists.xensource.com
> > http://lists.xensource.com/xen-users
>

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

wei huang

2005-Nov-07 16:41 UTC

head link

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

Hi Mark,

I am still having problem to create domUs on my server. The problem is
still like:
#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.
				~~~~~~~~~~~~~~~~ should it be vif0.0 or
						 vif?
Backend device not found!

I didn''t change anything related with hotplug or udev scripts on my OS.
I
started with a new Linux AS4 and just still xen + whatever packages your
require (brige-utils-1.0.6, Twisted-1.3.0, and iproute package was
already there). Really not sure what is happening.

Could you please give some suggestions? Here is the basic info about my
server. If you need more specific information, I will be happy to provide.
(output of xm log is also in the context)

Intel Xeon dual 2.40 GHz
1GB memory
Intel Corp. EtherExpress PRO/100 S Server Adapter
OS: Linux-AS4

Thanks!

-- Wei
> 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@lists.xensource.com
> > http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

Ewan Mellor

2005-Nov-07 17:16 UTC

head link

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

On Mon, Nov 07, 2005 at 11:41:57AM -0500, wei huang wrote:
> Hi Mark,
> 
> I am still having problem to create domUs on my server. The problem is
> still like:
> #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.
> 				~~~~~~~~~~~~~~~~ should it be vif0.0 or
> 						 vif?
''vif'' is correct.
> I didn''t change anything related with hotplug or udev scripts on
my OS. I
> started with a new Linux AS4 and just still xen + whatever packages your
> require (brige-utils-1.0.6, Twisted-1.3.0, and iproute package was
> already there). Really not sure what is happening.
Do you have udev and/or hotplug installed?

Ewan.

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

wei huang

2005-Nov-07 19:24 UTC

head link

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

Hi Ewan,

I have compiled my kernel with "Plug and Play support" and "ISA
Plug and
Play support". Is this what you mean by install hotplug?

I am not sure what you mean by install udev ... Do you mean I need to put
some special udev rules?

Please let me know if I miss something.

Thanks.

Regards,
Wei Huang

774 Dreese Lab, 2015 Neil Ave,
Dept. of Computer Science and Engineering
Ohio State University
OH 43210
Tel: (614)292-8501


On Mon, 7 Nov 2005, Ewan Mellor wrote:
> On Mon, Nov 07, 2005 at 11:41:57AM -0500, wei huang wrote:
>
> > Hi Mark,
> >
> > I am still having problem to create domUs on my server. The problem is
> > still like:
> > #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.
> > 				~~~~~~~~~~~~~~~~ should it be vif0.0 or
> > 						 vif?
>
> ''vif'' is correct.
>
> > I didn''t change anything related with hotplug or udev scripts
on my OS. I
> > started with a new Linux AS4 and just still xen + whatever packages
your
> > require (brige-utils-1.0.6, Twisted-1.3.0, and iproute package was
> > already there). Really not sure what is happening.
>
> Do you have udev and/or hotplug installed?
>
> Ewan.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

Ewan Mellor

2005-Nov-07 20:34 UTC

head link

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

On Mon, Nov 07, 2005 at 02:24:17PM -0500, wei huang wrote:
> Hi Ewan,
> 
> I have compiled my kernel with "Plug and Play support" and
"ISA Plug and
> Play support". Is this what you mean by install hotplug?
> 
> I am not sure what you mean by install udev ... Do you mean I need to put
> some special udev rules?
There is a userspace program that you need to make udev work, called udevd.
You will need this installed for things to work at all.

In any case, I''ve found the bug that is causing you problems. 
I''ll have a
patch ready this evening.

Cheers,

Ewan.

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

wei huang

2005-Nov-07 20:49 UTC

head link

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

Thanks!

I will wait for your patch :)

Regards,
Wei Huang

774 Dreese Lab, 2015 Neil Ave,
Dept. of Computer Science and Engineering
Ohio State University
OH 43210
Tel: (614)292-8501


On Mon, 7 Nov 2005, Ewan Mellor wrote:
> On Mon, Nov 07, 2005 at 02:24:17PM -0500, wei huang wrote:
>
> > Hi Ewan,
> >
> > I have compiled my kernel with "Plug and Play support" and
"ISA Plug and
> > Play support". Is this what you mean by install hotplug?
> >
> > I am not sure what you mean by install udev ... Do you mean I need to
put
> > some special udev rules?
>
> There is a userspace program that you need to make udev work, called udevd.
> You will need this installed for things to work at all.
>
> In any case, I''ve found the bug that is causing you problems. 
I''ll have a
> patch ready this evening.
>
> Cheers,
>
> Ewan.
>

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

Two KHz

2005-Nov-07 22:29 UTC

head link

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

Oh, i just downloaded the latest one, even I am getting same error, same
"unstable" version downloaded just one month back was working
perfectly
fine....
STRANGE!!!!!

I will work on it and see what is the issue.


On 11/8/05, wei huang <huanwei@cse.ohio-state.edu>
wrote:>
> Thanks!
>
> I will wait for your patch :)
>
> Regards,
> Wei Huang
>
> 774 Dreese Lab, 2015 Neil Ave,
> Dept. of Computer Science and Engineering
> Ohio State University
> OH 43210
> Tel: (614)292-8501
>
>
> On Mon, 7 Nov 2005, Ewan Mellor wrote:
>
> > On Mon, Nov 07, 2005 at 02:24:17PM -0500, wei huang wrote:
> >
> > > Hi Ewan,
> > >
> > > I have compiled my kernel with "Plug and Play support"
and "ISA Plug
> and
> > > Play support". Is this what you mean by install hotplug?
> > >
> > > I am not sure what you mean by install udev ... Do you mean I
need to
> put
> > > some special udev rules?
> >
> > There is a userspace program that you need to make udev work, called
> udevd.
> > You will need this installed for things to work at all.
> >
> > In any case, I''ve found the bug that is causing you problems.
I''ll have
> a
> > patch ready this evening.
> >
> > Cheers,
> >
> > Ewan.
> >
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

Two KHz

2005-Nov-07 22:46 UTC

head link

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

Hmm.......
I dont understand these below lines from my logs, can anyone tell whats
happening here...

Traceback (most recent call last):
File "/local/scratch/xenod/cron-build/xen-unstable-x86_32.W28422.dir/xen-
unstable.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line
152, in create
File "/local/scratch/xenod/cron-build/xen-unstable-x86_32.W28422.dir/xen-
unstable.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line
1109, in initDomain
File "/local/scratch/xenod/cron-build/xen-unstable-x86_32.W28422.dir/xen-
unstable.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line
1222, in createDevices
File "/local/scratch/xenod/cron-build/xen-unstable-x86_32.W28422.dir/xen-
unstable.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line
893, in createDevice
File "/local/scratch/xenod/cron-build/xen-unstable-x86_32.W28422.dir/xen-
unstable.hg/dist/install/usr/lib/python/xen/xend/server/DevController.py",
line 72, in createDevice
VmError: Device 0 (vif) could not be connected. Backend device not found!
[2005-11-08 03:56:07 xend.XendDomainInfo] DEBUG (XendDomainInfo:1156)
XendDomainInfo.destroy: domid=1
[2005-11-08 03:56:07 xend.XendDomainInfo] DEBUG (XendDomainInfo:1164)
XendDomainInfo.destroyDomain(1)
[2005-11-08 03:56:08 xend] ERROR (SrvBase:87) Request create failed.
Traceback (most recent call last):
File "/local/scratch/xenod/cron-build/xen-unstable-x86_32.W28422.dir/xen-
unstable.hg/dist/install/usr/lib/python/xen/web/SrvBase.py", line 85, in
perform
File "/local/scratch/xenod/cron-build/xen-unstable-x86_32.W28422.dir/xen-
unstable.hg/dist/install/usr/lib/python/xen/xend/server/SrvDomainDir.py",
line 82, in op_create
XendError: Error creating domain: Device 0 (vif) could not be connected.
Backend device not found!

Regards,
2khz

On 11/8/05, Two KHz <twokhz@gmail.com> wrote:>
> Oh, i just downloaded the latest one, even I am getting same error, same
> "unstable" version downloaded just one month back was working
perfectly
> fine....
> STRANGE!!!!!
>
> I will work on it and see what is the issue.
>
>
> On 11/8/05, wei huang <huanwei@cse.ohio-state.edu> wrote:
> >
> > Thanks!
> >
> > I will wait for your patch :)
> >
> > Regards,
> > Wei Huang
> >
> > 774 Dreese Lab, 2015 Neil Ave,
> > Dept. of Computer Science and Engineering
> > Ohio State University
> > OH 43210
> > Tel: (614)292-8501
> >
> >
> > On Mon, 7 Nov 2005, Ewan Mellor wrote:
> >
> > > On Mon, Nov 07, 2005 at 02:24:17PM -0500, wei huang wrote:
> > >
> > > > Hi Ewan,
> > > >
> > > > I have compiled my kernel with "Plug and Play
support" and "ISA Plug
> > and
> > > > Play support". Is this what you mean by install
hotplug?
> > > >
> > > > I am not sure what you mean by install udev ... Do you mean
I need
> > to put
> > > > some special udev rules?
> > >
> > > There is a userspace program that you need to make udev work,
called
> > udevd.
> > > You will need this installed for things to work at all.
> > >
> > > In any case, I''ve found the bug that is causing you
problems. I''ll
> > have a
> > > patch ready this evening.
> > >
> > > Cheers,
> > >
> > > Ewan.
> > >
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
>
>

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

Ewan Mellor

2005-Nov-08 00:14 UTC

head link

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

On Mon, Nov 07, 2005 at 03:49:20PM -0500, wei huang wrote:
> Thanks!
> 
> I will wait for your patch :)
Sorry, I have got myself all confused!

Wensheng Wang / Toens Bueker, it is your problem that I was referring to.
That is the one that I have a patch for.

Wei, I''m afraid I still don''t know what your problem is.  You
need to check
that you have the udevd daemon installed and running, and that the latest Xen
scripts are in all the right places (/etc/xen/scripts, /etc/udev/rules.d).  If
they are in place then there should be some useful information in your
/var/log/messages.  If not, then I am stuck!

Ewan.

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

takebe_akio@jp.fujitsu.com

2005-Nov-08 00:41 UTC

head link

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

Hi Wei,

I have same error, and I solved the problem when I install bridge-utils 
and sysfsutils.

Thanks,

Akio Takebe

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

wei huang

2005-Nov-08 02:05 UTC

head link

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

Hi Ewan,
>
> Sorry, I have got myself all confused!
>
> Wensheng Wang / Toens Bueker, it is your problem that I was referring to.
> That is the one that I have a patch for.
>
> Wei, I''m afraid I still don''t know what your problem is. 
You need to check
> that you have the udevd daemon installed and running, and that the latest
Xen
> scripts are in all the right places (/etc/xen/scripts, /etc/udev/rules.d). 
If
> they are in place then there should be some useful information in your
> /var/log/messages.  If not, then I am stuck!
I''ve verified that udevd is there and is running:
#c5xen# /etc/xen> ps -ef | grep udevd
root      2772     1  0 20:33 ?        00:00:00 udevd

All xen scripts are in correct place except there is no xen related
files in rules.d. However I checked your install scripts and find statements
like this:

if [ -x /sbin/udev ] && [ ! -z `udev -V` ] && [ `/sbin/udev -V`
-ge 059 ];
then
  cp -f $src/etc/udev/rules.d/*.rules $dst/etc/udev/rules.d/
else
  cp -f $src/etc/hotplug/*.agent $dst/etc/hotplug/
fi

The udev -V command outputs nothing on my system. And udevinfo -V
outputs 039. So I believe the else
branch gets executed. And I check that xen-backend.agent is there in
/etc/hotplug. Is this the problem? Do I have to install a newer version of
udev to make the whole thing work?

I tried manually copy your xen-backend.rules to rules.d but it doesn''t
seem to help.

And I find entry like this in /var/log/messages after xm create fails:

Nov  7 20:40:56 c5xen kernel: e100: peth0: e100_watchdog: link up, 100Mbps,
full-duplex
Nov  7 20:40:56 c5xen kernel: ip_tables: (C) 2000-2002 Netfilter core team
Nov  7 20:40:57 c5xen kernel: xenbr0: port 2(peth0) entering learning state
Nov  7 20:40:57 c5xen kernel: xenbr0: topology change detected,
propagating
Nov  7 20:40:57 c5xen kernel: xenbr0: port 2(peth0) entering forwarding state
Nov  7 20:41:44 c5xen ntpd[3633]: synchronized to LOCAL(0), stratum 10
Nov  7 20:42:47 c5xen logger: /etc/xen/scripts/vif-bridge: brctl addif xenbr0
vif1.0 failed
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Nov  7 20:42:48 c5xen ntpd[3633]: synchronized to 80.28.46.78, stratum 2
Nov  7 20:43:52 c5xen ntpd[3633]: kernel time sync enabled 0001

This is the only problem I can find. Would you please give more
suggestions?

Thank you very much!

-- Wei Huang>
> Ewan.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

Ewan Mellor

2005-Nov-08 02:24 UTC

head link

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

On Mon, Nov 07, 2005 at 09:05:23PM -0500, wei huang wrote:
> The udev -V command outputs nothing on my system. And udevinfo -V
> outputs 039. So I believe the else
> branch gets executed. And I check that xen-backend.agent is there in
> /etc/hotplug. Is this the problem? Do I have to install a newer version of
> udev to make the whole thing work?
That makes sense.  I think the intention here is to use udev if it is version
059 or greater, or to use the older hotplug approach otherwise.  Your system
should be using hotplug, in that case.  From the log message below, it looks
like your hotplug is OK, since the vif-bridge script is running.
> I tried manually copy your xen-backend.rules to rules.d but it
doesn''t
> seem to help.
> 
> And I find entry like this in /var/log/messages after xm create fails:
> 
> Nov  7 20:40:56 c5xen kernel: e100: peth0: e100_watchdog: link up, 100Mbps,
full-duplex
> Nov  7 20:40:56 c5xen kernel: ip_tables: (C) 2000-2002 Netfilter core team
> Nov  7 20:40:57 c5xen kernel: xenbr0: port 2(peth0) entering learning state
> Nov  7 20:40:57 c5xen kernel: xenbr0: topology change detected,
> propagating
> Nov  7 20:40:57 c5xen kernel: xenbr0: port 2(peth0) entering forwarding
state
> Nov  7 20:41:44 c5xen ntpd[3633]: synchronized to LOCAL(0), stratum 10
> Nov  7 20:42:47 c5xen logger: /etc/xen/scripts/vif-bridge: brctl addif
xenbr0 vif1.0 failed
So this line here says that we have failed to add the vif to the bridge.  Do
you intend to use bridged networking?  If so, is the bridge up?  You can check
using brctl show.

Usually, your bridge would be brought up by the network-bridge script, which
would be run by xend at start-of-day.  This is configured in
/etc/xen/xend-config.sxp, in the network-script option.  If you are using this
option, then presumably the network-bridge script is failing.

You can run the network-bridge script manually like this:

/etc/xen/scripts/network-bridge start

and then check your /var/log/messages for error messages again.

The network-bridge script has a few options.  These are discussed in the Xen
distribution''s example xend-config.sxp.

HTH,

Ewan.


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

Nivedita Singhvi

2005-Nov-08 02:28 UTC

head link

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

wei huang wrote:
> And I find entry like this in /var/log/messages after xm create fails:
> 
> Nov  7 20:40:56 c5xen kernel: e100: peth0: e100_watchdog: link up, 100Mbps,
full-duplex
> Nov  7 20:40:56 c5xen kernel: ip_tables: (C) 2000-2002 Netfilter core team
> Nov  7 20:40:57 c5xen kernel: xenbr0: port 2(peth0) entering learning state
> Nov  7 20:40:57 c5xen kernel: xenbr0: topology change detected,
> propagating
> Nov  7 20:40:57 c5xen kernel: xenbr0: port 2(peth0) entering forwarding
state
> Nov  7 20:41:44 c5xen ntpd[3633]: synchronized to LOCAL(0), stratum 10
> Nov  7 20:42:47 c5xen logger: /etc/xen/scripts/vif-bridge: brctl addif
xenbr0 vif1.0 failed
Well, that would be the fatal failure.

You seem to have created bridges successfully so assuming you have brctl
on your system. But try doing the above step (adding the interface to the
bridge) manually.

Also, put a set -x in your /etc/xen/scripts/network-bridge and
/etc/xen/scripts/vif-bridge script, and post their output found
in /var/log/xen-debug.log. Could be an older version of brctl
which doesn''t return status (?).

thanks,
Nivedita


>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Nov  7 20:42:48 c5xen ntpd[3633]: synchronized to 80.28.46.78, stratum 2
> Nov  7 20:43:52 c5xen ntpd[3633]: kernel time sync enabled 0001
> 
> This is the only problem I can find. Would you please give more
> suggestions?

thanks,
Nivedita


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

wei huang

2005-Nov-08 03:24 UTC

head link

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

Thanks for all your suggestions!

Actually it turns out to be quite a silly mistake. I use sudo to run all
those commands. brctl is located in /usr/local/sbin, which is in my local
PATH but not in root''s. I only check the path under my own account.
However the boot scripts encounters a ''command not found''... I
redirect
the output and find this.

Now though I still get some problem with domU''s file system, at least I
can go through the initial stage.

Thanks!

Regards,
Wei Huang

> wei huang wrote:
>
> > And I find entry like this in /var/log/messages after xm create fails:
> >
> > Nov  7 20:40:56 c5xen kernel: e100: peth0: e100_watchdog: link up,
100Mbps, full-duplex
> > Nov  7 20:40:56 c5xen kernel: ip_tables: (C) 2000-2002 Netfilter core
team
> > Nov  7 20:40:57 c5xen kernel: xenbr0: port 2(peth0) entering learning
state
> > Nov  7 20:40:57 c5xen kernel: xenbr0: topology change detected,
> > propagating
> > Nov  7 20:40:57 c5xen kernel: xenbr0: port 2(peth0) entering
forwarding state
> > Nov  7 20:41:44 c5xen ntpd[3633]: synchronized to LOCAL(0), stratum 10
>
> > Nov  7 20:42:47 c5xen logger: /etc/xen/scripts/vif-bridge: brctl addif
xenbr0 vif1.0 failed
>
> Well, that would be the fatal failure.
>
> You seem to have created bridges successfully so assuming you have brctl
> on your system. But try doing the above step (adding the interface to the
> bridge) manually.
>
> Also, put a set -x in your /etc/xen/scripts/network-bridge and
> /etc/xen/scripts/vif-bridge script, and post their output found
> in /var/log/xen-debug.log. Could be an older version of brctl
> which doesn''t return status (?).
>
> thanks,
> Nivedita
>
>
>
> >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > Nov  7 20:42:48 c5xen ntpd[3633]: synchronized to 80.28.46.78, stratum
2
> > Nov  7 20:43:52 c5xen ntpd[3633]: kernel time sync enabled 0001
> >
> > This is the only problem I can find. Would you please give more
> > suggestions?
>
>
> thanks,
> Nivedita
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

benjamin

2005-Nov-08 12:13 UTC

head link

Re: [Xen-users] Networking Questions

On 11/4/05, Steven Anderson <hikenboot@yahoo.com>
wrote:>
> Hello:
>
> For the first time I have setup Xen. Using Fedora Core
> 4 and Xen Unstable using 2.6.12-1.1454 xen kernel. I
> have installed a guest of fedora for my first
> experiment.
>
> What I dont really understand (although am a cisco
> certified WAN engineer) is the networking components
> of RedHat and Xen.
>
> I want to understand virtual IP''s Bridging, NAT and
> things like that from a linux point of view that are
> relative to Xen.
Can anyone point me to good documents> that are relative and applicable to fedora core 4 and
> Xen 3.0?

Good docs, diffcult to find right now. :-( . Best bet right now seesm to be
searching the list archive with related term.

I really like the diagram over here -

http://lists.xensource.com/archives/html/xen-users/2005-10/msg00152.html


Thanks!>
> Steve
>
>
>
> __________________________________
> Yahoo! FareChase: Search multiple travel sites in one click.
> http://farechase.yahoo.com
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>


--
benjamin rualthanzauva


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

Two KHz

2005-Nov-08 16:39 UTC

head link

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

Oh, me too the same issue, simple path.......
Now its working fine...
Thanks Wei for that point..

Regards,

On 11/8/05, wei huang <huanwei@cse.ohio-state.edu>
wrote:>
> Thanks for all your suggestions!
>
> Actually it turns out to be quite a silly mistake. I use sudo to run all
> those commands. brctl is located in /usr/local/sbin, which is in my local
> PATH but not in root''s. I only check the path under my own
account.
> However the boot scripts encounters a ''command not
found''... I redirect
> the output and find this.
>
> Now though I still get some problem with domU''s file system, at
least I
> can go through the initial stage.
>
> Thanks!
>
> Regards,
> Wei Huang
>
>
> > wei huang wrote:
> >
> > > And I find entry like this in /var/log/messages after xm create
fails:
> > >
> > > Nov 7 20:40:56 c5xen kernel: e100: peth0: e100_watchdog: link up,
> 100Mbps, full-duplex
> > > Nov 7 20:40:56 c5xen kernel: ip_tables: (C) 2000-2002 Netfilter
core
> team
> > > Nov 7 20:40:57 c5xen kernel: xenbr0: port 2(peth0) entering
learning
> state
> > > Nov 7 20:40:57 c5xen kernel: xenbr0: topology change detected,
> > > propagating
> > > Nov 7 20:40:57 c5xen kernel: xenbr0: port 2(peth0) entering
forwarding
> state
> > > Nov 7 20:41:44 c5xen ntpd[3633]: synchronized to LOCAL(0),
stratum 10
> >
> > > Nov 7 20:42:47 c5xen logger: /etc/xen/scripts/vif-bridge: brctl
addif
> xenbr0 vif1.0 failed
> >
> > Well, that would be the fatal failure.
> >
> > You seem to have created bridges successfully so assuming you have
brctl
> > on your system. But try doing the above step (adding the interface to
> the
> > bridge) manually.
> >
> > Also, put a set -x in your /etc/xen/scripts/network-bridge and
> > /etc/xen/scripts/vif-bridge script, and post their output found
> > in /var/log/xen-debug.log. Could be an older version of brctl
> > which doesn''t return status (?).
> >
> > thanks,
> > Nivedita
> >
> >
> >
> > >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > Nov 7 20:42:48 c5xen ntpd[3633]: synchronized to
80.28.46.78<http://80.28.46.78>,
> stratum 2
> > > Nov 7 20:43:52 c5xen ntpd[3633]: kernel time sync enabled 0001
> > >
> > > This is the only problem I can find. Would you please give more
> > > suggestions?
> >
> >
> > thanks,
> > Nivedita
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

boy (sent by Nabble.com)

2005-Nov-22 19:21 UTC

head link

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

I am getting the same error while creating a domain in  unstable. In my case

1) No issue with bridge mode networking

2) Issue arises only with routed/nated mode networking

udev seems to be running. This happens on Sarge domU on Sarge dom0.
--
Sent from the Xen - User forum at Nabble.com:
http://www.nabble.com/Networking-Questions-t491634.html#a1605353


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

boy (sent by Nabble.com)

2005-Nov-23 00:35 UTC

head link

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

Sorry for having to  post again. ould really appreciate if someone can tell me
what different thing Xn does with  bridge-mode and routed/nated mode networking
in 3.
--
Sent from the Xen - User forum at Nabble.com:
http://www.nabble.com/Networking-Questions-t491634.html#a1610261


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

Xen users - Nov 2005 - Networking Questions

[Xen-users] Networking Questions

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Re: [Xen-users] Networking Questions

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

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

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