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] Debian domU interface naming strangeness

To: "Xen users mailing list" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Debian domU interface naming strangeness
From: "Ray Barnes" <tical.net@xxxxxxxxx>
Date: Thu, 31 Jul 2008 17:52:04 -0400
Delivery-date: Thu, 31 Jul 2008 14:52:41 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=LFYhMATQlKwa2AgEMtlPwoDshDwJGP1+gmM/Wlzb2nk=; b=NiEQ5RWqjZspDGsNgSuTxTqPnqlpt4mFEcZgJ19PqcSJNqj2NPUvYUCp6BTsT0uI2Q Ik7YthcVK4AKhS5PYPFqO3cN48sAHuAqfv53GgZQbSQ3Nkb/8GzsDdGksMnN71bOm3m0 xniMaFEe0HTyeZxLQcZrb0KsOCmNbVh70bE6A=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=WPxVFIMoBj/m4pysl/PNeet5kgnflJOryVkIjdyEfpBmXhUwpHOb9xGgAa9/45N4GO Hy/9l3KJyuqK1ObqgFtCOP856QvHWf9MULOVRoDCpZ23v4W953qBsy6bHW0+2KjK+A4j 3HESVpWYgC6/EZrtzf2gf1n6c422fynCmsc5Y=
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
Hi all.  I've got a Debian domU I created from scratch a few weeks
ago.  Every time I rolled it out previously in testing, it worked
fine.  But now it seems to make the ethernet device eth1 rather than
eth0 in the domU:

localhost:~# ifconfig -a
eth1      Link encap:Ethernet  HWaddr 00:16:3E:3D:A0:30
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

localhost:~# dmesg|grep -i eth
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has flipping receive path.
localhost:~#

Note that as eth1, it routes traffic just fine.  I can ifconfig it up
and set an IP address, then get good routed connectivity.  I'm seeing
this eth1 naming issue on dom0s running CentOS 5.0 with the stock Xen
3.0.3 (yes that means literally 5.0, not a higher minor number), as
well as Cent 5.1 with Xen 3.2.0 compiled from source.  But obviously
it presents a problem since I can't count on consistent naming.

Thoughts?

-Ray

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

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