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

Re: [Xen-users] Interface incrementation problem

  • To: Andy Smith <andy@xxxxxxxxxxxxxx>
  • From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
  • Date: Tue, 10 Apr 2007 18:35:26 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 10 Apr 2007 10:32:42 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=NvAz5YaoQgkHew7Egn5cy6VP6+PBiP464/66OdCpb0xLev8ucoQytJJhnMiMMOs2+gyyrTj0ZDgIvc60JAJDk2wfzV27xiza9gu3jBWqTsNenR3OesrdIUrv4NNu7e3BkDmKv/YAcOAH7Rc+Fq+4QvV/nhTkU4GNsAdimbShNW0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Andy Smith wrote:
On Thu, Apr 05, 2007 at 11:11:48AM +0200, Radek Antoniuk wrote:
When I'm putting:
vif = [ ' bridge=xenbr0' ]
in the config file, every restart of the virtual machine, the mac
address is changed. Because of that, I get, eth0 after first run, then
eth1 (with no eth0), then eth2... and so on.
That is not good.

It's because of udev, creating persistent device names based on
MAC address.

And the solution is:
The problem is solvable via setting the MAC explicitly in the vif
syntax, but that is not comfortable while doing a lot of new machines

Why are you not comfortable with this?  I generally find it
essential for management purposes that each domain has a stable MAC
address that is used by it and only it.

Agreed. And it's easy to assing a MAC address range to each Xen Dom0 server to allocate for its DomU's, so when you see some spewiing cient in the logs or on a switch you have some idea what the heck it is.

Xen-users mailing list



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