WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Cannot ping DomU from Dom0 / cannot ping same site from two

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Cannot ping DomU from Dom0 / cannot ping same site from two DomUs at the same time
From: Wolfgang Formann <wformann@xxxxxxxx>
Date: Tue, 09 Jun 2009 10:27:47 +0200
Delivery-date: Tue, 09 Jun 2009 01:28:58 -0700
Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=arcor.de; s=mail-in; t=1244536068; bh=TN2w5HKqSihQs9wthfsXHjy2ps+TLjNJGlq5fX4N3xU=; h=Message-ID:Date:From:MIME-Version:To:Subject:Content-Type: Content-Transfer-Encoding; b=BoQAaH5lCodYzDSjr/jHYe0Q9VIyMgPRb3VNsf0HM2lBb0nL/upk4aRmhDPZbZGJT QD9vHwIRdEv8rLuHfLzuWhrp2wjkGxitcgIAgcAkMwMtX41MCtUVF+O88tpYCmO2To 19oBPFzHo29yu8bwCknPdTL0Z8KoyFSf2DaMB9mw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.13) Gecko/20070221
Hello!

I have two problems. One is, that I cannot ping a DomU from Dom0 (or any
other host in my local network) and the second one is, that I cannot
ping the same site (eg. www.suse.com) from two DomU's at the same time.

I have a fresh installation of openSuse 11.0 with Kernel
2.6.25.20-0.1-xen and my box has two physical ethernet cards.

As far as I have investigated, eth0 is the one which is grabbed by the
Xen-scripts, als you can see here:

# brctl show
bridge name     bridge id               STP enabled     interfaces
eth0            8000.003048d69cfa       no              peth0
                                                        tap0
                                                        vif7.0

The file xend-config.sxp is unmodified, I filter here all those comments:
# egrep -v "^$|^#" xend-config.sxp
(xen-api-server ((unix none)))
(xend-unix-server yes)
(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
(network-script network-bridge)
(vif-script vif-bridge)
(dom0-min-mem 512)
(dom0-cpus 0)
(vncpasswd '')

ifconfig shows these one, while one DomU is running.

# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:30:48:D6:9C:FA
          inet addr:192.168.222.16  Bcast:192.168.222.255 Mask:255.255.255.0
          inet6 addr: fe80::230:48ff:fed6:9cfa/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1032642 errors:0 dropped:0 overruns:0 frame:0
          TX packets:668426 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1101565708 (1050.5 Mb)  TX bytes:83483260 (79.6 Mb)

eth1      Link encap:Ethernet  HWaddr 00:30:48:D6:9C:FB
          inet addr:192.168.224.1  Bcast:192.168.224.255  Mask:255.255.255.0
          inet6 addr: fe80::230:48ff:fed6:9cfb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2093348 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2372864 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:177871101 (169.6 Mb)  TX bytes:7055283604 (6728.4 Mb)
          Interrupt:20 Base address:0xe000

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:329651 errors:0 dropped:0 overruns:0 frame:0
          TX packets:329651 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1269637544 (1210.8 Mb)  TX bytes:1269637544 (1210.8 Mb)

peth0     Link encap:Ethernet  HWaddr 00:30:48:D6:9C:FA
          inet6 addr: fe80::230:48ff:fed6:9cfa/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:1322260 errors:0 dropped:0 overruns:0 frame:0
          TX packets:739433 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1319675729 (1258.5 Mb)  TX bytes:92076405 (87.8 Mb)
          Interrupt:20 Base address:0xa000

tap0      Link encap:Ethernet  HWaddr 00:FF:C5:E9:26:66
          inet6 addr: fe80::2ff:c5ff:fee9:2666/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:216 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1313 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:40640 (39.6 Kb)  TX bytes:96970 (94.6 Kb)

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

It also seems, that all those various arp-addresses are set up fine.
00:16:3e:1f:0b:3c is the one I see inside the DomU

# brctl showmacs eth0
port no mac addr                is local?       ageing timer
  1     00:03:c5:01:4d:52       no                 0.29
  2     00:16:3e:1f:0b:3c       no               109.27
  1     00:17:f2:c4:a0:ca       no                 8.32
  1     00:30:48:d6:9c:fa       yes                0.00
  1     00:50:ba:70:05:87       no               193.89
  1     00:e0:7d:79:a6:c1       no                 0.92
  2     00:ff:c5:e9:26:66       yes                0.00
  1     08:00:20:0b:cf:35       no                 0.92
  3     fe:ff:ff:ff:ff:ff       yes                0.00

Now when I do a ping from Dom0 to DomU I see the following tcpdump:
09:45:43.191701 arp who-has 192.168.222.102 tell 192.168.222.16
and no answer within a few seconds.

So it seems that something with arp is not fine. Any ideas what to do next?

#######

The other problem which may be related is a little bit more strange. I have set
up two DomU's, one with Vista-32bit and one with Vista-64bit. Both have
differend IP-addresses and different MAC-addresses. I can ping whatever host (in
my LAN or in the internet) with both DomU's. No problem. I can also ping any
host, even on a different subnet in my LAN from both DomU's at the same time.

But when I try to ping www.suse.com (or any other host in the internet) at the
same time only that DomU pings successfully where I started the ping first, the
other DomU fails. If one DomU pings www.slashdot.org an other other pings
www.suse.com both pings work fine. Ping also works fine, when I ping any other
host in my LAN from both DomU's. This one puzzles mee too. I crosschecked and
can ping from any other pair of my machines to the outside without problems.

Thanks
Wolfgang


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

<Prev in Thread] Current Thread [Next in Thread>