From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NKHlj-0005IS-7K for qemu-devel@nongnu.org; Mon, 14 Dec 2009 15:43:47 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NKHle-0005Es-Ju for qemu-devel@nongnu.org; Mon, 14 Dec 2009 15:43:46 -0500 Received: from [199.232.76.173] (port=44609 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NKHle-0005Ei-6y for qemu-devel@nongnu.org; Mon, 14 Dec 2009 15:43:42 -0500 Received: from mail-yx0-f188.google.com ([209.85.210.188]:35280) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NKHld-0001sp-TI for qemu-devel@nongnu.org; Mon, 14 Dec 2009 15:43:42 -0500 Received: by yxe26 with SMTP id 26so3319049yxe.4 for ; Mon, 14 Dec 2009 12:43:41 -0800 (PST) Message-ID: <4B26A37A.20309@codemonkey.ws> Date: Mon, 14 Dec 2009 14:43:38 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: qdev property bug? References: <4B2647AF.1030605@codemonkey.ws> <20091214141143.GA1360@redhat.com> <20091214141341.GB1360@redhat.com> <4B264AF1.6060802@codemonkey.ws> <7FB8DD1225E54176BCAF5523B6AEA89B@FSCPC> <4B26931E.4000101@codemonkey.ws> <20091214194210.GB6150@redhat.com> <4B269933.3010906@codemonkey.ws> <20091214202019.GF6150@redhat.com> <4B26A0DE.5000304@redhat.com> <20091214203428.GI6150@redhat.com> In-Reply-To: <20091214203428.GI6150@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: glommer@redhat.com, qemu-devel@nongnu.org, Alexander Graf , Kevin O'Connor , Gerd Hoffmann , Sebastian Herbszt Michael S. Tsirkin wrote: > On Mon, Dec 14, 2009 at 09:32:30PM +0100, Gerd Hoffmann wrote: > >> On 12/14/09 21:20, Michael S. Tsirkin wrote: >> >>>> So far, it's not clear to me that anyone has demonstrated how this is >>>> harmful for people that don't want pxe booting. Assuming we fix the bug >>>> about rom loading, then there's really no impact to users. >>>> >> Fix (v2) is on the list already. >> >> >>> PXE booting might have security impact. You do not want to >>> do this if you are on a hostile network. >>> >> Option rom loaded doesn't imply pxe boot will be tried. It only means >> PXE boot can be selected, either via >> >> -boot order=[something with 'n' here] >> >> or via >> >> -boot menu=on + F12 + picking menu entry >> >> By default qemu doesn't try to PXE-boot, even if no other bootable >> device is available. >> >> cheers, >> Gerd >> > > I guess so. But then, why are we loading it in BIOS > and wasting memory? Let's only shadow the ROM > when PXE is selected? > Because it can be selected by the user via the menu and because it can be selected at runtime via the boot_set monitor command. Also, the comment about "wasting memory" not quite accurate. The memory region in question is only used for roms. If we didn't put roms there, it would go to waste. Currently, the only roms we load are pxe roms or things specified by -option-rom. You could certainly argue that making -option-rom higher priority than implicit pxe roms is valuable but removing the pxe roms really serves no purpose. Regards, Anthony Liguori