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] in domU eth0 is now eth3?

To: Xen users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] in domU eth0 is now eth3?
From: Rune Elvemo <rune.elvemo@xxxxxxx>
Date: Wed, 14 Mar 2007 16:15:16 +0100
Delivery-date: Thu, 15 Mar 2007 03:37:52 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
We had a little strange experience here. We had to copy something to our
xen image. It was done while the domU was down, mounting using the
loopback device.
After we had finished the job, unmounted, and restarted the domU, we had
no eth0. Got an error message in the bootup. I thought something had
gone really wrong, and that we no more had network access in this
particular domU.

After checking things out, there was still an ethernet device, however
now it's listed as eth3 inside the domU. Is there a way to control what
the virtual ethernet device should be named inside the virtual domU? 

Given the current config it could  for instance all of a sudden turn up
as eth2, so it would be nice to be able to say that it should ALWAYS be
known as eth0

Anyone who has any suggestions?

(I've attached the current config, only diffence from the actual config
is that the real IP is not specified, there is only one bridge in use,
and eth3 does work exactly like the previous eth0 did)

Thanks!

Attachment: vm_server.cfg
Description: Text document

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>