On Wed, Feb 5, 2014 at 9:46 AM, Kurt Lidl <l...@pix.net> wrote:

> On Feb 5, 2014, at 3:33 , Kai Gallasch <k at free.de> wrote:
>>  Am 05.02.2014 um 08:03 schrieb Craig Rodrigues:
>>>> Hi,
>>>> I am running many BHyve VM's and am using tap interfaces
>>>> with a single bridge.  I am configuring the IP addresses
>>>> of these VM's via DHCP.
>>>> I need to have separate MAC addresses for each VM.
>>>> Can anyone recommend a range of MAC addresses to use?
>>>> I seem to recall that at the 2013 FreeBSD Vendor Summit in
>>>> Sunnyvale, California, that George mentioned that
>>>> there might be a Organizational Unique Identifier (OUI) for the FreeBSD
>>>> project that we can use for BHyve VM's.  Is that right?
>>>> If not, can people recommend a range of addresses to use?
>>> http://standards.ieee.org/develop/regauth/oui/public.html
>>> Using "Search the Public MA-L Listing" with search term FreeBSD reveals..
>>> --- snip ---
>>> Here are the results of your search through the public section of the
>>> IEEE Standards OUI database report for freebsd:
>>>  58-9C-FC   (hex)               FreeBSD
>>> Foundation
>>>  589CFC     (base 16)
>>> FreeBSD
>>> Foundation
>>>                                 P.O. Box 20247
>>>                                 Boulder CO  80308-3247
>>>                                 UNITED STATES
>>> --- snap ---
>> Correct, that is an address that the Foundation has registered with the
>> IEEE.
>> If you look at sys/net/ieee_oui.h you will see that I've allocated a
>> range to bhyve already.
> At work, we modified the bhyverun command to seed the hostname
> of them machine running the hypervisor as part of the "generate a MAC
> address" routine.  That means that for virtual machine "foo",
> you now get different MACs on server "bar" and server "baz".
> Without this patch, you're likely to get identical MAC addresses
> for virtual machine "foo" on different servers.
> I personally also have my virtual machines set bit 2 in
> the first octet of the MAC address, so it falls into the
> "locally administered" catagory of MAC addresses.  My gut feel
> is that using the FreeBSD OUI bhyve range, *AND* setting the
> locally administered bit in the MAC address is the way to go.
> b


Thanks for allocating that range of MAC addresses.
We shoud probably document that MAC address range in one of the BHyve man


Your change is definitely useful.  It changes the behavior of BHyve with
respect to MAC addresses,
but it is a very useful change.  Have you submitted your change
to Peter and Neel to see if they can evaluate if it can be made part of
BHyve in the FreeBSD src tree?

freebsd-virtualization@freebsd.org mailing list
To unsubscribe, send any mail to 

Reply via email to