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

Re: [Xen-users] domU gets eth1 instead of eth0

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] domU gets eth1 instead of eth0
From: mpeters@xxxxxxxxxxxxxxx
Date: Mon, 30 Jul 2007 15:02:02 +0100
Delivery-date: Mon, 30 Jul 2007 06:59:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <718828c0707300342k605731c8h630fc1b03ed5ea44@xxxxxxxxxxxxxx>
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: <718828c0707300342k605731c8h630fc1b03ed5ea44@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Internet Messaging Program (IMP) 3.2.3
Quoting Tomoki Taniguchi <tomoki.taniguchi@xxxxxxxxx>:

> is there a reason why my domU is getting eth1 as the network device
> instead of eth0?
>
> xen version:  3.03
> dom0:  Ubuntu 7.04 Server.
>
> domU:  I created a template for the domU by creating a looback
> filesystem in an existing Ubuntu Server.  I mounted it then Rsynced
> the contents of / to the mounted filesystem.  I copied everything
> including /dev and /proc.
>
> what should i do to ensure that eth0 is created when i use the image?
> also how do i make sure that the mac address for the eth0 will be different
> each time i create a duplicate of the image file for a new domU?
>

You've copied the config from the existing server. The configuration for eth0 is
tied to the MAC address of the card on that server, this MAC address won't exist
on your DomU and so your interface will be assigned as eth1.

On your DomU, open the file /etc/udev/rules.d/30-net_persistent_names.rules. You
probably have a rule something like the following for eth0:

SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:aa:aa:aa:aa:aa",
IMPORT="/lib/udev/rename_netiface %k eth0"

Remove it and try restarting your Dom0.

--
Mike Peters
Web Site: http://www.ice2o.com


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

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