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

[Xen-devel] Networking problem in domUs


  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: David F Barrera <dfbp@xxxxxxxxxx>
  • Date: Wed, 15 Feb 2006 12:19:07 -0600
  • Delivery-date: Wed, 15 Feb 2006 18:31:31 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I've been having issues with domU networking on an IBM xSeries 460. It
is running several guest domains, and most, but not all, of them are
having networking problems. These guest domains HAVE worked properly in
the past, so it is unlikely a setup problem. 


HW:
IBM xSeries 460, SAS drives, 8GB of RAM
0000:0f:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit
Ethernet (rev 10)
Distro: SLES 9 SP2

changeset:   8833:39b392a22002 (and 8830 before that)
tag:         tip
user:        kaf24@xxxxxxxxxxxxxxxxxxxx
date:        Tue Feb 14 12:43:45 2006 +0100
summary:     Fix segment-register dumping in show_registers()

For example, when I ping one of them:
x366-xentest:/skyline/barrera/xm-test # ping x460-xentest-vm8
PING x460-xentest-vm8.ltc.austin.ibm.com (9.3.190.126) 56(84) bytes of data.
64 bytes from x460-xentest-vm8.ltc.austin.ibm.com (9.3.190.126): icmp_seq=1
ttl=63 time=0.609 ms
wrong data byte #22 should be 0x16 but was 0x0
#16     10 11 12 13 14 15 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
#48     0 0 0 0 0 0 0 0
64 bytes from x460-xentest-vm8.ltc.austin.ibm.com (9.3.190.126): icmp_seq=2
ttl=63 time=0.592 ms
wrong data byte #22 should be 0x16 but was 0x0
#16     10 11 12 13 14 15 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
#48     0 0 0 0 0 0 0 0
64 bytes from x460-xentest-vm8.ltc.austin.ibm.com (9.3.190.126): icmp_seq=3
ttl=63 time=0.533 ms
wrong data byte #22 should be 0x16 but was 0x0
#16     10 11 12 13 14 15 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
#48     0 0 0 0 0 0 0 0

----
vm8 is configured properly:
[root@x460-xentest-vm8 ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:3E:51:9D:72
          inet addr:9.3.190.126  Bcast:9.3.190.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12165 errors:0 dropped:0 overruns:0 frame:0
          TX packets:342 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1408961 (1.3 MiB)  TX bytes:54400 (53.1 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:22 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1672 (1.6 KiB)  TX bytes:1672 (1.6 KiB)

The networking on the guest domain is set up properly; however, I can't ssh or 
ping any machines.
Out of roughly 10 guest domains, only a couple have functioning networking.
Again, this setup has worked in the past.


-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides


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


 


Rackspace

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