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] Dom0 network UP but not RUNNING (openSUSE 10.2)

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Dom0 network UP but not RUNNING (openSUSE 10.2)
From: Paul Uiterlinden <puiterl@xxxxxxxxx>
Date: Mon, 1 Jan 2007 18:23:49 +0100
Delivery-date: Tue, 02 Jan 2007 01:30:09 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.5
After installing Xen from openSUSE 10.2 rpm (3.0.3_11774-20) and 
successfully starting Dom0, I lose all access to the network.

I have found a work around, but that's all what it is: just a work 
around. The root cause remains unclear to me. I hope my message will 
be the start of finding the real cause. I am of course willing to 
provide more information and help debugging if necessary.

After quite some digging, I have come to the conclusion that the 
reason for having no network access at all is the following:

# ifconfig peth0
peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST NOARP  MTU:1500  Metric:1
          RX packets:9684 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6396 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:12095362 (11.5 Mb)  TX bytes:465140 (454.2 Kb)
          Interrupt:17 Base address:0xc800

The link is UP, but nor RUNNING. In this situation, pinging to a 
locally connected device gives "Destination Host Unreachable":

# ping -c1 10.0.0.138
PING 10.0.0.138 (10.0.0.138) 56(84) bytes of data.
From 10.0.0.5: icmp_seq=1 Destination Host Unreachable

--- 10.0.0.138 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 
0ms


The work around that I found is bringing the link down and, after a 
few seconds, bring it up again:

# ip link set peth0 down; sleep 3; ip link set peth0 up

After a few seconds, the state of the link is UP and RUNNING:

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  MTU:1500  Metric:1
          RX packets:9691 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6404 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:12095923 (11.5 Mb)  TX bytes:465573 (454.6 Kb)
          Interrupt:17 Base address:0xc800

Im this state the network works fine, locally and to the outside 
world.

Stopping the Xen bridge with "/etc/xen/scripts/network-bridge stop" 
brings the link (now called eth0) in a similar state as above: up, 
but not running. The same trick works here too: bring eth0 down, wait 
a few seconds and bring it up again. In this case, also the default 
route needs to be restored: ip route add to default via 10.0.0.138


The hardware I'm using is:

CPU:
Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz

The ethernet device is integrated in the motherboard:
ALi Corporation ULi 1689,1573 integrated ethernet. (rev 50)

I'm using SUSE:
openSUSE 10.2 (X86-64) - Kernel 2.6.18.2-34-xen

The Xen configuration is clean out of the box.

Just let me know if more information is needed.


As a side note: as I was (and still am) not quite sure about the 
meaning of UP and RUNNING in the output of ifconfig, I found this 
after some googling: 

http://lists.freebsd.org/pipermail/freebsd-hackers/2004-August/007817.html

Quote:
As a matter of fact, the IFF_RUNNING flag, visible as ``RUNNING'' in
the output from ifconfig(8), is intended for interface's internal use
and should not influence the interaction of the interface with other
modules, except for affecting careful user's experience :-)

I don't know if this is BSD behavior only. It is at least not the 
behavior I see.

-- 
Paul.

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

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