[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] domU networking trouble in Xen 3.0-unstable.hg



I'm just getting started with Xen and am having some trouble getting networking up and running in domU. The symptoms are that packets can leave domU and go through xen-br0, but packets are not getting back into domU. Specifically, this is what I'm seeing when sending a ping from within domU:

Note: domU is 192.168.0.12
Note: dom0 is 192.168.0.11

[root@domU ~]# tcpdump -i eth0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
19:48:48.173992 arp who-has 192.168.0.11 tell 192.168.0.12
19:48:49.173981 arp who-has 192.168.0.11 tell 192.168.0.12
19:48:50.173981 arp who-has 192.168.0.11 tell 192.168.0.12
19:48:52.183980 arp who-has 192.168.0.11 tell 192.168.0.12
19:48:53.183991 arp who-has 192.168.0.11 tell 192.168.0.12

Watching this ping from dom0 shows a different story:

[root@dom0 ~]# tcpdump -i vif1.1
tcpdump: WARNING: vif1.1: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vif1.1, link-type EN10MB (Ethernet), capture size 96 bytes
19:50:41.780777 arp who-has 192.168.0.11 tell 192.168.0.12
19:50:41.969751 arp reply 192.168.0.11 is-at 00:a0:c9:e3:75:5e
19:50:42.900698 arp who-has 192.168.0.11 tell 192.168.0.12
19:50:42.900728 arp reply 192.168.0.11 is-at 00:a0:c9:e3:75:5e
19:50:43.900690 arp who-has 192.168.0.11 tell 192.168.0.12
19:50:43.900717 arp reply 192.168.0.11 is-at 00:a0:c9:e3:75:5e
19:50:44.900677 arp who-has 192.168.0.11 tell 192.168.0.12
19:50:44.900705 arp reply 192.168.0.11 is-at 00:a0:c9:e3:75:5e
19:50:46.910656 arp who-has 192.168.0.11 tell 192.168.0.12
19:50:46.910685 arp reply 192.168.0.11 is-at 00:a0:c9:e3:75:5e

It looks like domU is sending out the arp request, but never getting the arp reply. However, clearly the arp reply is being sent by dom0...it seems to be getting lost somewhere in the connection between vif1.1 and the domU/eth0. I'm including some additional configuration information about my setup below. If additional information would be helpful, just let me know.

Does anyone have thoughts about how to solve this?

Thanks,
bryan


========== DOMU Information ====================
[root@domU ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr AA:00:00:3D:B1:DD
inet addr:192.168.0.12 Bcast:192.168.0.255 Mask: 255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:1848 (1.8 KiB)

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:39 errors:0 dropped:0 overruns:0 frame:0
          TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4368 (4.2 KiB)  TX bytes:4368 (4.2 KiB)

[root@domU ~]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 192.168.0.254 0.0.0.0 UG 0 0 0 eth0
[root@domU ~]# ping 192.168.0.11
PING 192.168.0.11 (192.168.0.11) 56(84) bytes of data.
From 192.168.0.12 icmp_seq=0 Destination Host Unreachable
From 192.168.0.12 icmp_seq=1 Destination Host Unreachable
From 192.168.0.12 icmp_seq=2 Destination Host Unreachable
From 192.168.0.12 icmp_seq=3 Destination Host Unreachable
From 192.168.0.12 icmp_seq=4 Destination Host Unreachable
From 192.168.0.12 icmp_seq=5 Destination Host Unreachable

--- 192.168.0.11 ping statistics ---
7 packets transmitted, 0 received, +6 errors, 100% packet loss, time 6055ms
, pipe 4
[root@domU ~]#


========== DOM0 Information ====================
[root@dom0 ~]# xm list
Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
Domain-0           0      1500    0      1  r-----     85.7
domU               1       255    0      1  -b----      8.7
[root@dom0 ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:A0:C9:E3:75:5E
inet addr:192.168.0.11 Bcast:192.168.0.255 Mask: 255.255.255.0
          inet6 addr: fe80::2a0:c9ff:fee3:755e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:221 errors:0 dropped:0 overruns:0 frame:0
          TX packets:224 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:66104 (64.5 KiB)  TX bytes:34473 (33.6 KiB)

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:135 errors:0 dropped:0 overruns:0 frame:0
          TX packets:135 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10210 (9.9 KiB)  TX bytes:10210 (9.9 KiB)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:215 errors:0 dropped:0 overruns:0 frame:0
          TX packets:308 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:71438 (69.7 KiB)  TX bytes:41704 (40.7 KiB)

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:224 errors:0 dropped:0 overruns:0 frame:0
          TX packets:222 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:34473 (33.6 KiB)  TX bytes:66194 (64.6 KiB)

vif1.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:53 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:89 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2226 (2.1 KiB)  TX bytes:0 (0.0 b)

xen-br0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:102 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9297 (9.0 KiB)  TX bytes:378 (378.0 b)

[root@dom0 ~]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 192.168.0.254 0.0.0.0 UG 0 0 0 eth0
[root@dom0 ~]# cat /etc/xen/domU
kernel = "/boot/vmlinuz-2.6.12-xenU"
memory = 256
name = "domU"
nics=1
disk = ['file:/opt/xen_images/domU.img,sda1,w' ]
root = "/dev/sda1"
extra = "ro selinux=0 3"
[root@dom0 ~]#
====================

Attachment: smime.p7s
Description: S/MIME cryptographic signature

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.