Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759074Ab0GUTdK (ORCPT ); Wed, 21 Jul 2010 15:33:10 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:49413 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758793Ab0GUTdI (ORCPT ); Wed, 21 Jul 2010 15:33:08 -0400 Date: Wed, 21 Jul 2010 12:33:24 -0700 (PDT) Message-Id: <20100721.123324.237334251.davem@davemloft.net> To: gregory.v.rose@intel.com Cc: leedom@chelsio.com, shemminger@vyatta.com, andy@greyhouse.net, harald@redhat.com, bhutchings@solarflare.com, sassmann@redhat.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, gospo@redhat.com, alexander.h.duyck@intel.com Subject: Re: [PATCH net-next] sysfs: add entry to indicate network interfaces with random MAC address From: David Miller In-Reply-To: <43F901BD926A4E43B106BF17856F0755F1846247@orsmsx508.amr.corp.intel.com> References: <20100721.114851.200597269.davem@davemloft.net> <20100721.115023.69942880.davem@davemloft.net> <43F901BD926A4E43B106BF17856F0755F1846247@orsmsx508.amr.corp.intel.com> X-Mailer: Mew version 6.3 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1355 Lines: 32 From: "Rose, Gregory V" Date: Wed, 21 Jul 2010 12:02:17 -0700 >>From: David Miller >>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 linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/