thr3ads.net - Xen users - [Xen-users] Error: Device 0 (vif) could not be connected. ip addr add 10.0.0.329 dev vif28.0 failed [Oct 2011]

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

Heist

2011-Oct-04 19:12 UTC

[Xen-users] Error: Device 0 (vif) could not be connected. ip addr add 10.0.0.329 dev vif28.0 failed

I''ve looked everywhere for the error message I''ve posted in
the title,
doesn''t seem like anyone else has it (lots of missing hotplugs
scripts).
We''re using network-nat. ifconfig -a outputs this:

eth0      Link encap:Ethernet  HWaddr 00:19:99:a8:f4:5c
          inet addr:X.X.X.X  Bcast:X.X.X.X  Mask:255.255.255.255
          inet6 addr: X::X:X:X:X/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:233907120 errors:0 dropped:13 overruns:0 frame:1
          TX packets:207650975 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:211662949632 (197.1 GiB)  TX bytes:94589739440 (88.0 GiB)
          Interrupt:18

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:34177 errors:0 dropped:0 overruns:0 frame:0
          TX packets:34177 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2870973 (2.7 MiB)  TX bytes:2870973 (2.7 MiB)

vif10.0   Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          inet addr:10.0.0.128  Bcast:0.0.0.0  Mask:255.255.255.255
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12709868 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15200680 errors:0 dropped:5 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:9168041480 (8.5 GiB)  TX bytes:9449301463 (8.8 GiB)

vif2.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          inet addr:10.0.0.144  Bcast:0.0.0.0  Mask:255.255.255.255
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14675180 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14909317 errors:0 dropped:5 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:7856634435 (7.3 GiB)  TX bytes:3609331825 (3.3 GiB)

vif21.0   Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          inet addr:10.0.0.153  Bcast:0.0.0.0  Mask:255.255.255.255
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5339 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4593 errors:0 dropped:2 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:426184 (416.1 KiB)  TX bytes:867356 (847.0 KiB)

vif5.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          inet addr:10.0.0.145  Bcast:0.0.0.0  Mask:255.255.255.255
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6168852 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6017891 errors:0 dropped:3 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:2187308579 (2.0 GiB)  TX bytes:2578588258 (2.4 GiB)

vif8.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          inet addr:10.0.0.147  Bcast:0.0.0.0  Mask:255.255.255.255
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2315417 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3079044 errors:0 dropped:5 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:830772507 (792.2 MiB)  TX bytes:2375279128 (2.2 GiB)

--
View this message in context:
http://xen.1045712.n5.nabble.com/Error-Device-0-vif-could-not-be-connected-ip-addr-add-10-0-0-329-dev-vif28-0-failed-tp4869998p4869998.html
Sent from the Xen - User mailing list archive at Nabble.com.

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

Felix Kuperjans

2011-Oct-09 16:40 UTC

head link

Re: [Xen-users] Error: Device 0 (vif) could not be connected. ip addr add 10.0.0.329 dev vif28.0 failed

Maybe you should try a valid IPv4 address instead of 10.0.0.329?

IPv4 addresses may only have four values from 0 to 254 (effectively
because 255 is in most cases broadcast), separated by dots.
Try an address like 10.0.0.229, that should work.

Regards,
Felix

Am 04.10.2011 21:12, schrieb Heist:> I''ve looked everywhere for the error message I''ve posted
in the title,
> doesn''t seem like anyone else has it (lots of missing hotplugs
scripts).
> We''re using network-nat. ifconfig -a outputs this:
>
> eth0      Link encap:Ethernet  HWaddr 00:19:99:a8:f4:5c
>           inet addr:X.X.X.X  Bcast:X.X.X.X  Mask:255.255.255.255
>           inet6 addr: X::X:X:X:X/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:233907120 errors:0 dropped:13 overruns:0 frame:1
>           TX packets:207650975 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:211662949632 (197.1 GiB)  TX bytes:94589739440 (88.0
GiB)
>           Interrupt:18
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:34177 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:34177 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:2870973 (2.7 MiB)  TX bytes:2870973 (2.7 MiB)
>
> vif10.0   Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
>           inet addr:10.0.0.128  Bcast:0.0.0.0  Mask:255.255.255.255
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:12709868 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:15200680 errors:0 dropped:5 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:9168041480 (8.5 GiB)  TX bytes:9449301463 (8.8 GiB)
>
> vif2.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
>           inet addr:10.0.0.144  Bcast:0.0.0.0  Mask:255.255.255.255
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:14675180 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:14909317 errors:0 dropped:5 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:7856634435 (7.3 GiB)  TX bytes:3609331825 (3.3 GiB)
>
> vif21.0   Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
>           inet addr:10.0.0.153  Bcast:0.0.0.0  Mask:255.255.255.255
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:5339 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:4593 errors:0 dropped:2 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:426184 (416.1 KiB)  TX bytes:867356 (847.0 KiB)
>
> vif5.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
>           inet addr:10.0.0.145  Bcast:0.0.0.0  Mask:255.255.255.255
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:6168852 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:6017891 errors:0 dropped:3 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:2187308579 (2.0 GiB)  TX bytes:2578588258 (2.4 GiB)
>
> vif8.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
>           inet addr:10.0.0.147  Bcast:0.0.0.0  Mask:255.255.255.255
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:2315417 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:3079044 errors:0 dropped:5 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:830772507 (792.2 MiB)  TX bytes:2375279128 (2.2 GiB)
>
> --
> View this message in context:
http://xen.1045712.n5.nabble.com/Error-Device-0-vif-could-not-be-connected-ip-addr-add-10-0-0-329-dev-vif28-0-failed-tp4869998p4869998.html
> Sent from the Xen - User mailing list archive at Nabble.com.
>
> _______________________________________________
> 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

Heist

2011-Dec-14 18:42 UTC

head link

Re: Error: Device 0 (vif) could not be connected. ip addr add 10.0.0.329 dev vif28.0 failed

Ok, so a few months late because I found a way around my problem, but
I''d
rather fix it:

The domU is not configured to use 329, but rather 202, which as far as I
know, should be ok. The problem is not present on older versions of Xen.

--
View this message in context:
http://xen.1045712.n5.nabble.com/Error-Device-0-vif-could-not-be-connected-ip-addr-add-10-0-0-329-dev-vif28-0-failed-tp4869998p5075327.html
Sent from the Xen - User mailing list archive at Nabble.com.

Heist

2011-Dec-14 18:44 UTC

head link

Re: Error: Device 0 (vif) could not be connected. ip addr add 10.0.0.329 dev vif28.0 failed

Relevant line from the domU''s config file:

vif         = [ ''ip=10.0.0.202,mac=00:16:3E:6A:A0:60'' ]

--
View this message in context:
http://xen.1045712.n5.nabble.com/Error-Device-0-vif-could-not-be-connected-ip-addr-add-10-0-0-329-dev-vif28-0-failed-tp4869998p5075329.html
Sent from the Xen - User mailing list archive at Nabble.com.

Apparently Analagous Threads

Search for more seemingly similar threads

Xen users - Oct 2011 - Error: Device 0 (vif) could not be connected. ip addr add 10.0.0.329 dev vif28.0 failed

[Xen-users] Error: Device 0 (vif) could not be connected. ip addr add 10.0.0.329 dev vif28.0 failed

Re: [Xen-users] Error: Device 0 (vif) could not be connected. ip addr add 10.0.0.329 dev vif28.0 failed

Re: Error: Device 0 (vif) could not be connected. ip addr add 10.0.0.329 dev vif28.0 failed

Re: Error: Device 0 (vif) could not be connected. ip addr add 10.0.0.329 dev vif28.0 failed

Apparently Analagous Threads