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] Slackware 12 DomU NIC increments on each start

To: Russell Packer <russell.packer@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Slackware 12 DomU NIC increments on each start
From: Steve Kemp <steve@xxxxxxxxxxxx>
Date: Fri, 16 Nov 2007 13:59:28 +0000
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 16 Nov 2007 06:00:38 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <447CD0A4E64B1D45AE4838B0B214FD2D015C2770@xxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <447CD0A4E64B1D45AE4838B0B214FD2D015C2770@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: mutt-ng/devel-r804 (Debian)
On Fri Nov 16, 2007 at 13:21:58 -0000, Russell Packer wrote:

> The problem is that networking doesn't work properly. Each time I
> shutdown and restart, the NIC increments... eth0, eth1, eth2... I'm on
> eth12 right now! Once the system starts I can use ifconfig & route to
> assign an IP and a default gateway, and I get a network connection.
> Weird stuff.
> Does anyone have any ideas what is going on / what I need to do? I just
> want my nice eth0...

  This is almost certainly udev being "helpful".

  If you don't have a special vif line each time your guest will
 receive a new MAC address for the nic.  The first time it boots
 udev will think "Hmmmm MAC xxxx thats new.  I'll call that eth0".

  The next time you boot you'll have a different MAC address so
 udev thinks "Hmmm this is new!  I'll call this eth1 in case that other
 one comes back...".

  Solution:  Setup a static MAC address in your Xen configuration
 file with something like:

    vif = [' mac=aa:bb:cc:dd::ee::ff' ]

  Once you've done that you can remove the stored mac addresses
 from /etc/udev/rules.d/ and all will be well.

  Failing that you could have random MAC addresses and just delete
 the relevant udev files. I  guess they will be called something like

# The Debian Security Audit Project.

Xen-users mailing list