[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100721.123324.237334251.davem@davemloft.net>
Date: Wed, 21 Jul 2010 12:33:24 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: gregory.v.rose@...el.com
Cc: leedom@...lsio.com, shemminger@...tta.com, andy@...yhouse.net,
harald@...hat.com, bhutchings@...arflare.com, sassmann@...hat.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
gospo@...hat.com, alexander.h.duyck@...el.com
Subject: Re: [PATCH net-next] sysfs: add entry to indicate network
interfaces with random MAC address
From: "Rose, Gregory V" <gregory.v.rose@...el.com>
Date: Wed, 21 Jul 2010 12:02:17 -0700
>>From: David Miller <davem@...emloft.net>
>>Date: Wed, 21 Jul 2010 11:48:51 -0700 (PDT)
>>
>>> You could do things like have the PF controller use the root
>>filesystem
>>> ID label to construct the VF's MAC address, or something like that.
>>
>>And here I of course mean the root filesystem of the guest the VF will
>>be given to.
>
> I suppose you could do that but then the VM is going to have to be
> allowed to set its own MAC address. There is a lot of opposition
> and concern about allowing VMs to set their own MAC address.
Why would that be necessary? The host with the PF creating the guest
has access to the "device" and thus the root filesystem of the guest,
and thus could pull in the root filesystem "key" and instantiate the
VF's MAC before booting the guest.
That was the idea, the control node sets up the VF MAC before the guest
boots or can have access to the VF device.
This is completely agnostic of migration or anything like that. The
procedure for setting the VF MAC is always the same.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists