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/
Home Products Support Community News


Re: [Xen-users] eth0 disappears replaced by eth1

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] eth0 disappears replaced by eth1
From: Georg Fleckenstein <georg.fleckenstein@xxxxxx>
Date: Fri, 09 Nov 2007 21:06:59 +0100
Delivery-date: Fri, 09 Nov 2007 12:07:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <002801c822fb$a59c03a0$0500a8c0@claradol>
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>
References: <002801c822fb$a59c03a0$0500a8c0@claradol>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Windows/20070728)
TURPIN Olivier schrieb:

I have just installed xen 3.1
After booting kernel (without xen) I have one eth0 with static IP NIC is a nvidia MCP65 ethernet on Asus M2N-X motherboard. After booting with xen kernel dom0, eth0 disappears (config file still present). No peth0 visible. And eth1 has appeared with noconfig (it has not inherited
the eth0 config).
ifconfig shows lo and xenbr0 only, nothing else.
ifconfig -a shows all the vif, xenbr0, eth1 but no eth0 and no peth0.
Network is not operational.

Does anyone have an idea of what is going on ? Is it possible that xen kernel would identify motherboard NIC as different from eth0 ?
Is it possible to force motherboard NIC to be eth0 ?

I had the same problem with Asus M2N-MX mainboard.
It is the combination of the nic-driver "forcedeth" and udev.
Older versions of the driver could not get the MAC-Adress of the nic, so they randomly create one. But udev uses the MAC for creating the devices. With every boot the devicenumber is one more. eth0,eth1,eth2 ...

For one nic and debian etch i fixed it with a rule in /etc/udev/rules.d/z25_persistent-net.rules. SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{vendor}=="0x10de", ATTRS{device}=="0x03ef", NAME="eth0" Infos about vendor and device you got with
 udevinfo -a -p /class/net/ethxxx
where xxx ist the current devicename of the nic.
Please search in Google for complete howtos.


Xen-users mailing list

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