From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LNS1o-0002rs-Ea
	for qemu-devel@nongnu.org; Thu, 15 Jan 2009 08:12:57 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LNS1m-0002rD-02
	for qemu-devel@nongnu.org; Thu, 15 Jan 2009 08:12:55 -0500
Received: from [199.232.76.173] (port=53192 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LNS1j-0002qh-Vq
	for qemu-devel@nongnu.org; Thu, 15 Jan 2009 08:12:52 -0500
Received: from mail2.shareable.org ([80.68.89.115]:40566)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1LNS1j-0000hZ-Dd
	for qemu-devel@nongnu.org; Thu, 15 Jan 2009 08:12:51 -0500
Date: Thu, 15 Jan 2009 13:12:49 +0000
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] Re: [PATCH 1/5] virtio-net: Allow setting the MAC
	address via set_config
Message-ID: <20090115131249.GD32368@shareable.org>
References: <1231881829.9095.191.camel@bling> <496DB8D1.2070101@redhat.com>
	<1231947298.7109.262.camel@lappy>
	<20090114164155.GA6431@shareable.org> <496E61F0.8060605@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <496E61F0.8060605@redhat.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: dlaor@redhat.com, qemu-devel@nongnu.org
Cc: Mark McLoughlin <markmc@redhat.com>, kvm <kvm@vger.kernel.org>

Dor Laor wrote:
> What I meant is that if we allow the guest to change his mac address, it 
> can deliberately
> change it to other hosts/guests mac and thus create networking problems.
> Although guest can always mangle packets, maybe it worth enforcing these 
> macs for the guest.

Although it can create network problems, sometimes it is also wanted.

I think if you want to restrict the guests's ability to break the
network by changing its MAC, it would be appropriate to have an option
to completely lock down the MAC so the guest can't change its MAC at all.

-- Jamie