From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Pratt <Ian.Pratt@eu.citrix.com>
Cc: Xen Devel <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"Gianni Tedesco (3P)" <gianni.tedesco@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH]: xl: use libuuid to generate random UUID's
Date: Wed, 04 Aug 2010 19:27:47 -0700 [thread overview]
Message-ID: <4C5A21A3.3020601@goop.org> (raw)
In-Reply-To: <4FA716B1526C7C4DB0375C6DADBC4EA37AD0596B2F@LONPMAILBOX01.citrite.net>
On 08/04/2010 07:19 PM, Ian Pratt wrote:
> The best approach is to generate locally administered MAC addresses hence giving us 46 bits of freedom rather than XenSource registered OUI addresses which have just 24 bits -- collisions will be *much* less likely. Further, it's best not to generate random addresses every time, but to derive the MAC address from a good hash of the VM UUID and the NIC number so that they are deterministic.
Yes! I've been doing that manually (where my hash is '+'), but its
irritating to keep doing over and over.
J
next prev parent reply other threads:[~2010-08-05 2:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 17:49 [PATCH]: xl: use libuuid to generate random UUID's Gianni Tedesco
2010-08-05 2:19 ` Ian Pratt
2010-08-05 2:27 ` Jeremy Fitzhardinge [this message]
2010-08-10 10:44 ` Ian Campbell
2010-08-10 11:14 ` Vincent Hanquez
2010-08-10 14:38 ` Stefano Stabellini
2010-08-10 19:38 ` Jeremy Fitzhardinge
2010-08-05 9:19 ` Vincent Hanquez
2010-08-05 10:13 ` Christoph Egger
2010-08-05 11:11 ` Vincent Hanquez
2010-08-05 16:42 ` Stefano Stabellini
2010-08-05 10:34 ` Stefano Stabellini
2010-08-09 10:51 ` Ian Jackson
2010-08-09 11:04 ` Gianni Tedesco
2010-08-10 15:23 ` Ian Jackson
2010-08-10 15:24 ` Gianni Tedesco
2010-08-10 16:55 ` Ian Jackson
2010-08-10 16:06 ` Ian Pratt
2010-08-10 19:43 ` Jeremy Fitzhardinge
2010-08-11 11:15 ` Ian Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C5A21A3.3020601@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=gianni.tedesco@citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.