| To: | "Xen users mailing list" <xen-users@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-users] 'Wandering' eth interface - Xen 3.0.4 + linux 2.6.16.29 |
| From: | TMC <tmciolek@xxxxxxxxx> |
| Date: | Tue, 1 May 2007 01:09:43 +1000 |
| Delivery-date: | 2007年4月30日 08:08:19 -0700 |
| Dkim-signature: | a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Ubqg6xlu9P/MMzzIeIkCnajNK9/cDRysCt5N+C7XwCBl5g2IX2bGWxC5/NHHfnQdg9KI//Ci4+PacfuPcxShIwNBJb2RuDxVoiaI5ELXBohrkTRT4ovD0qUmGdcVgyJuGWaRhJggvVzo/fJ7M4BRViQGHfENpLnCXfvPLT05vV4= |
| 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=ivBCRdKWSn+W22Q3PfE6pFxnETUG3hu3nkWyfQK2ICTQquiBUS6Qqn/CQtaIshY7GmtTS+IqHZVzQy9pmCG4sQQwXXYi6I7ZmroicsyvxOxi7z8oxZBVCDUNdeo5a9feoLJ5Kh89mlW/m89FIntmHJHO8B0Ff3IUmLWBwf+szao= |
| 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 |
I have a Xen 3.0.4 with Debian Etch (4.0) running quite successfully... except for an annoying problem, which i have not observed in other DomU instances, nor have I observed it with my test server... The problem I am observing in that one domain is that on reboot, the eth interface seems to "wander" - that is monotonically increase the index value... so on one reboot it will be eth0 on next eth1, on one after that eth3 and so on. Of course this causes all sorts of scripts to fail, and manual intervention is required. has anyone else seen this misbehaviour? Is there a method of pinning or making this behaviour consistent? Tomasz -- GPG key fingerprint: 3883 B308 8256 2246 D3ED A1FF 3A1D 0EAD 41C4 C2F0 GPG public key availabe on pgp.mit .edu keyserver _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-users] error creating domain in xen 3.0.5 , Mark Williamson |
|---|---|
| Next by Date: | Re: [Xen-users] error creating domain in xen 3.0.5 , Itamar Reis Peixoto |
| Previous by Thread: | [Xen-users] xen HVM when Window is closed ! , louis nerion |
| Next by Thread: | RE: [Xen-users] 'Wandering' eth interface - Xen 3.0.4 + linux 2.6.16.29 , Petersson, Mats |
| Indexes: | [Date] [Thread] [Top] [All Lists] |