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

Re: [Xen-users] Slackware 12 DomU NIC increments on each start

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Florian Heigl" <florian.heigl@xxxxxxxxx>
  • Date: Sun, 18 Nov 2007 06:01:58 +0100
  • Delivery-date: Sat, 17 Nov 2007 21:02:41 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NYnXJMCQvsD6KM9c1g1YUSBPqiwTr0axaa8K98/enBo4DOCsqZr/V/BpnipPwOG7qDQjI73ORgzH3AM/jd6lbx3bdSiHljT9m/X2BQOLbgHxKVz8s5hzs+FK08bU2XJj6+sLNLnGx6uZ/c/b7PNkYo21rJ1HnPHE3oEHoi3EaKs=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi all,

just a little proposal ;)

2007/11/16, Tom Brown <xensource.com@xxxxxxxxxxxxxxxxxxx>:
> On Fri, 16 Nov 2007, Steve Kemp wrote:
> > On Fri Nov 16, 2007 at 13:21:58 -0000, Russell Packer wrote:
> >
> >> The problem is that networking doesn't work properly. Each time I
> >> shutdown and restart, the NIC increments... eth0, eth1, eth2... I'm on
> >> eth12 right now! Once the system starts I can use ifconfig & route to
> >> assign an IP and a default gateway, and I get a network connection.
> >> Weird stuff.
> >>
> >> Does anyone have any ideas what is going on / what I need to do? I just
> >> want my nice eth0...
> >
> >  This is almost certainly udev being "helpful".
> I suspect it's kudzu ... which IMHO is not really appropriate on domUs and
> should be disabled, but I don't like/trust automagic... With kudzu turned
> off (chkconfig kudzu off) and making sure there is no MAC= line in your
> /etc/sysconfig/network-scripts/ifcfg-eth0 file, you should be ok even if
> the mac address is changing.... at least this is true for my old and new
> redhat based systems. -Tom

I posted about this like half a year ago, and still think it would be
the best if there was
some xen magic to save back the GUID and MAC autogenerated on first
startup into the
domU config.
it might not be the right way to mess with the domU conf file, but
maybe someone has a more elegant idea, still it'd be best if they only
got auto-generated once and be committed "somewhere" automatically.
back on Xen2 i still generated the MAC addresses manually, but ever
since a valid mac specification is valid people trip over this as it
just seems unnatural *unless* you know how xen currently handles it. I
think in the long run it'd be better to handle it the way anyone would
expecpt it. "if it can generate it, then why can't it remember it?"


'Sie brauchen sich um Ihre Zukunft keine Gedanken zu machen'

Xen-users mailing list



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