|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] vifN.0 dropping all packets
Hi,
I'm having a problem getting Xen networking (bridging) to work with my
domUs. I am using Xen 3.0.2 with Gentoo 2006.1 as dom0 (2.6.16.28-xen).
The machine is a newer Dell with a Pentium D (VMX enabled) processor. It
has one physical ethernet interface (Tigon3). The networking works fine in
dom0 (I'm using SSH right now), but I can't get anything in my domUs. I
can't obtain an IP address in any of the domUs and setting the IP manually
doesn't help. I've even tried setting a static ARP entry on dom0 to one of
the domUs and I can't get to any of them that way either. All of the domUs
are HVMs and some are running Windows XP and some are running OpenBSD. All
of the domU config files have ne2000=0 (using pcnet NIC).
It seems all of the virtual interfaces for the domUs are dropping all of
the TX packets:
xen_test ~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:13:72:90:B0:1E
inet addr:10.100.230.53 Bcast:10.100.230.255
Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX
packets:2154068 errors:0 dropped:0 overruns:0 frame:0 TX
packets:1122632 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:700501412 (668.0 Mb) TX bytes:1295541967 (1235.5 Mb)
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:0 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:0 (0.0 b) TX bytes:0 (0.0 b)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX
packets:2154051 errors:0 dropped:0 overruns:0 frame:0 TX
packets:1122621 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:712483148 (679.4 Mb) TX bytes:1300072225 (1239.8 Mb)
Interrupt:16
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1122632 errors:0 dropped:0 overruns:0 frame:0 TX
packets:2154071 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1295541967 (1235.5 Mb) TX bytes:700501651 (668.0 Mb)
vif10.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:1352884 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif11.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:1352837 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif12.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:1352794 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif23.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:1025165 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif24.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:1016382 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1386756 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:109029513 (103.9 Mb) TX bytes:0 (0.0 b)
And the bridge looks okay:
xen_test ~ # brctl show
bridge name bridge id STP enabled interfaces xenbr0
8000.feffffffffff no vif0.0
peth0
vif23.0
vif10.0
vif11.0
vif12.0
vif24.0
All of the domUs are similar to this (just different IDs of course):
xen_test ~ # xm network-list 24
Idx BE MAC Addr. handle state evt-ch tx-/rx-ring-ref BE-path 0 0
?? 0 1 -1 -1 /-1
/local/domain/0/backend/vif/24/0
Also, when doing a 'brctl showmacs xenbr0' it doesn't show any of the
domU's MAC addresses (maybe this is normal):
xen_test ~ # brctl showmacs xenbr0
port no mac addr is local? ageing timer
2 00:00:5e:00:01:86 no 0.33
2 00:01:f4:3a:17:e5 no 0.88
2 00:01:f4:c2:e5:6d no 7.28
2 00:03:47:69:1b:33 no 27.21
2 00:03:47:75:7a:57 no 101.39
2 00:03:47:9d:d2:79 no 134.76
2 00:03:47:a0:64:4e no 50.17
2 00:04:75:db:57:63 no 2.68
2 00:04:75:db:5a:bf no 0.86
2 00:04:75:ec:6c:10 no 1.24
2 00:04:75:ee:41:61 no 0.30
2 00:04:75:ee:4c:36 no 21.70
2 00:07:e9:c1:bc:bd no 178.02
2 00:07:e9:c1:bc:c8 no 70.35
2 00:07:e9:c1:bc:e5 no 26.52
2 00:08:74:fa:34:64 no 41.99
2 00:0b:db:6a:9b:21 no 21.57
2 00:0c:29:62:41:e0 no 21.57
2 00:0c:db:24:a8:60 no 0.58
2 00:0c:f1:7a:76:7a no 120.55
2 00:0c:f1:85:8b:e8 no 46.19
2 00:0c:f1:85:8c:53 no 2.85
2 00:0c:f1:85:aa:b7 no 63.02
2 00:0c:f1:86:95:f9 no 74.22
2 00:0c:f1:86:96:06 no 21.57
2 00:0c:f1:86:96:13 no 16.69
2 00:0c:f1:8b:69:98 no 14.58
2 00:0d:56:09:8e:17 no 4.35
2 00:0f:b0:c0:21:48 no 233.13
2 00:10:4b:88:50:31 no 0.00
2 00:10:83:2c:f5:ee no 6.63
2 00:11:11:0b:92:fc no 55.59
2 00:11:11:0b:b4:ec no 184.95
2 00:11:11:0b:b5:be no 37.37
2 00:11:11:0b:ba:4d no 60.34
2 00:11:11:0b:db:79 no 131.05
2 00:11:11:12:9c:1b no 95.04
2 00:11:11:12:a0:8a no 231.88
2 00:11:11:12:a2:b1 no 242.66
2 00:11:11:12:a2:ba no 217.18
2 00:11:11:13:48:99 no 95.13
2 00:11:11:34:16:c0 no 187.49
2 00:11:11:34:31:f3 no 243.63
2 00:13:20:12:b4:7c no 53.33
2 00:13:20:39:a5:ab no 24.85
2 00:13:20:3a:89:34 no 254.88
2 00:13:20:3a:9f:2f no 117.90
2 00:13:20:3a:9f:9b no 190.64
2 00:13:20:3a:9f:a6 no 288.34
2 00:13:20:3a:a0:f3 no 195.07
2 00:13:20:42:20:f6 no 140.15
2 00:13:20:42:20:f9 no 28.59
2 00:13:20:42:45:43 no 56.57
2 00:13:20:42:5d:9d no 57.42
2 00:13:20:42:5e:b3 no 88.89
2 00:13:20:42:6f:2b no 107.30
2 00:13:20:42:70:07 no 235.70
2 00:13:20:42:70:3d no 107.57
2 00:13:20:42:70:44 no 109.29
2 00:13:20:42:71:33 no 79.85
2 00:13:20:42:72:84 no 251.82
2 00:13:20:42:74:ee no 297.31
2 00:13:20:42:a8:b0 no 199.41
2 00:13:20:4c:21:09 no 146.26
2 00:13:20:4c:2c:d8 no 60.93
2 00:13:20:4c:2d:49 no 238.06
2 00:13:20:4c:35:a5 no 253.62
2 00:13:20:4c:36:d7 no 137.50
2 00:13:20:4c:41:64 no 51.88
2 00:13:20:80:32:cb no 81.71
2 00:13:72:90:92:8c no 89.54
1 00:13:72:90:b0:1e no 0.00
2 00:14:51:03:99:26 no 21.84
2 00:14:51:a7:0d:a8 no 21.89
2 00:60:b0:13:e4:e1 no 41.89
2 08:00:09:bf:60:d6 no 28.93
2 08:00:09:c1:e0:26 no 16.29
2 08:00:37:2a:65:fb no 77.71
2 08:00:37:33:43:e3 no 77.69
2 08:00:37:33:52:37 no 57.60
1 fe:ff:ff:ff:ff:ff yes 0.00
I guess I'm a bit stumped. I don't have iptables installed. I'd like to
get this bridging method working. I've seen that you can also do
networking using the routing method, but I guess I'd still like to find
out why this isn't working. This has gotta be something simple I'm
missing. I've attached my dom0 Linux kernel .config just in case.
Any help is greatly appreciated.
Thanks for your time.
--Marc
Attachment:
config.gz _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |