All of lore.kernel.org
 help / color / mirror / Atom feed
From: David F Barrera <dfbp@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Networking problem in domUs
Date: Wed, 15 Feb 2006 12:19:07 -0600	[thread overview]
Message-ID: <1140027548.9887.4.camel@dbarrera_tp> (raw)

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@firebug.cl.cam.ac.uk
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

             reply	other threads:[~2006-02-15 18:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 18:19 David F Barrera [this message]
2006-02-15 18:24 ` Networking problem in domUs Saku Ytti
2006-02-15 21:32   ` David F Barrera
2006-02-16  8:52     ` Saku Ytti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1140027548.9887.4.camel@dbarrera_tp \
    --to=dfbp@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.