From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH RFC OSSTEST 09/19] ts-host-install: Add force-mac-address host flag Date: Fri, 10 Oct 2014 15:12:58 +0100 Message-ID: <1412950378.27111.27.camel@citrix.com> References: <1412942404.27111.12.camel@citrix.com> <1412942554-752-9-git-send-email-ian.campbell@citrix.com> <21559.59568.250785.481559@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <21559.59568.250785.481559@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Fri, 2014-10-10 at 15:09 +0100, Ian Jackson wrote: > Ian Campbell writes ("[PATCH RFC OSSTEST 09/19] ts-host-install: Add force-mac-address host flag"): > > This causes us to emit udev runes which force the device named in > > the host's Interface_Force property to have the MAC address given in > > the host's Ether property. This is the reverse of the behaviour of > > the Interface_Force property without this flag, which is to rename > > the device with MAC address Ether to have the requested name. > > There is a potential problem with this, which is that Linux doctrine > is that devices do not have stable names. So if you don't identify > the device by mac address, and your system has more than one network > interface, osstest can't identify the device reliably at all. > > Do your actual boards have more than one eth* ? Just the one. Ian.