[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] domU gets eth1 instead of eth0

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Tomoki Taniguchi" <tomoki.taniguchi@xxxxxxxxx>
  • Date: Mon, 30 Jul 2007 19:42:58 +0900
  • Delivery-date: Mon, 30 Jul 2007 03:40:49 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=KbgnqICY29/IREQtu/JPC74E5gwdDa+agpd+3lXQWM09XE5219fz5cpY7bN2fUA3DPa9FzYoDp7GVwANs1B5i/xUtvwYCL0Tf3WF18cE85E5sz+wep3mVmfGMRr3kX7mF8LX2Ddilb1y3d8ZnPN24aVxfrvdwC42oN9aG4ItUmM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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?


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.