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/
Home Products Support Community News


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

To: "Xen list" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Slackware 12 DomU NIC increments on each start
From: "Florian Heigl" <florian.heigl@xxxxxxxxx>
Date: Sun, 25 Nov 2007 04:56:20 +0100
Cc: Andy Smith <andy@xxxxxxxxxxxxxx>
Delivery-date: Sat, 24 Nov 2007 19:57:02 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=qsUjYk3PHyLxkCxXuowvhqFdpWsD8L6IDGoHFxeSP6Y=; b=Gypo6TuZl+AONaQAAhfVHkkiPEfJY4rZ6FrPKOYJ4LcUrH/s+ZxfPH4abZrUGsLucgVoXUKY4GKC4HTZeaPw9PuuBHc+KiHp+J12mOomATfdhRNm3fxrk7+b7dI2IOVSosEUPWcBSBd3HyzmxNcsjbDxXXfDjJYrh/1IGl4zXIY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=bwgUkhciVS/xu3szoprtQsXYUjtdJuzGz+3EH9ABefh2dUgxUwSqO95M2KyaJz1aVOAO5+gSG8briKf3pK3NgXlyseyR2C9QkwU+HrBRu+xRbBynOGKCrEZYyTD53p78JpTx5/ccXTfuVc+svz8t9RE9jMRpkBFiRdLMF0zbWzs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071124191402.GX3347@xxxxxxxxxxx>
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>
References: <447CD0A4E64B1D45AE4838B0B214FD2D015C2770@xxxxxxxxxxxxxxxxxxxxxxxxxx> <200711231749.08776.jim_burn@xxxxxxxxxxxxx> <77abe410711231622gd2674faw4124904d10deec83@xxxxxxxxxxxxxx> <20071124191402.GX3347@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi Andy,

2007/11/24, Andy Smith <andy@xxxxxxxxxxxxxx>:
> Hi Florian,
> On Sat, Nov 24, 2007 at 01:22:24AM +0100, Florian Heigl wrote:
> [MAC address selection]
> > This is a functionality best placed with Xen
> > - as half of it is already there
> > - as xend is the best thing to query other members in
> > clustered/load-balanced setups
> > - as there is NO point in everyone being asked to handle it manually
> > or hack scripts
> > - as it will save time for everyone.
> I'd be happy with that as long as there is still a way to override
> it.  I have more than one dom0 on the same LAN so I need to keep my
> MAC address assignments in a database.  In theory one dom0 could be
> made to query all others, but I see the open source version of Xen
> to be just one (admittedly major) building block of a larger system
> and it does not need to do everything.

I agree on both points...
The easiest thing would be to have a "pluggable" script like, for
example, xen-block or network-bridge are called, or the way you select
different loaders in the domU config.

one could simply define mac_handling = auto

Having this script replacable would allow for useful extensions - i.e.
if someone uses dom0 firewalling for egress filtering the dom0 could
do an actual first dhcprequest and set up firewalling before the
(untrusted) domU is launched - just an example.

i'd say it's a good job for xend's to handle as with loadbalancing or
some other features the amount of dom0-dom0 xmlrpc communications will
probably increase anyway.
my feeling is the current approach is half-baked ... "if it generates
it, it should deal with it, too"

but easy management of such a feature (enable/disable, replace and
influence it's options) is definitely crucial, on the other hand i
think thats easy enough to accomplish

one could start with
vif [ 'bridge=xxx','mac=auto,persistent' ]

then you can have scripts with backend support (xend, a textfile, a
database table from Enomalism), without backend support, with extra
functions (like the dhcp+firewall) example, and so on without changing
standard behaviour.


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

Xen-users mailing list