From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:53468) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TO2es-0005E2-CA for qemu-devel@nongnu.org; Tue, 16 Oct 2012 04:37:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TO2eo-0002eg-75 for qemu-devel@nongnu.org; Tue, 16 Oct 2012 04:37:50 -0400 Message-ID: <507D1CD4.7070504@suse.de> Date: Tue, 16 Oct 2012 10:37:40 +0200 From: =?ISO-8859-1?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <1349921082-980-1-git-send-email-aviksil@linux.vnet.ibm.com> <20121011225934.GL25270@truffula.fritz.box> <1DCDCFB3-839C-4BF8-A89C-29FCD362E841@suse.de> <507CD815.6010203@linux.vnet.ibm.com> <80A8CD3C-C79E-45F8-8861-EEB37272D2B1@suse.de> In-Reply-To: <80A8CD3C-C79E-45F8-8861-EEB37272D2B1@suse.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH] Add nvram to default boot device list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Nikunj A Dadhania , Gleb Natapov , qemu-devel qemu-devel , David Gibson , qemu-ppc List , Avik Sil , Anthony Liguori Am 16.10.2012 10:04, schrieb Alexander Graf: >=20 >=20 > On 16.10.2012, at 05:44, Avik Sil wrote: >=20 >> On 10/12/2012 05:33 AM, Alexander Graf wrote: >>> >>> On 12.10.2012, at 00:59, David Gibson wrote: >>> >>>> On Thu, Oct 11, 2012 at 07:34:42AM +0530, Avik Sil wrote: >>>>> This patch adds nvram specified boot device into qemu default >>>>> boot_devices list. This helps firmware to boot from nvram specified >>>>> boot device if no -boot option is specified. >>>> >>>> I really don't think this is a good idea, it extends an already >>>> deprecated mechanism in a fuzzy way and requires careful checking to >>>> see if it could break anything. On all platforms the boot sequence >>>> should be: >>>> if bootindex is specified: >>>> boot according to bootindex >>>> else if -boot is specified: >>>> boot according to -boot sequence >>>> else: >>>> use platform firmware default sequence >>>> >>>> The last will of course vary by platform, and could depend on platfo= rm >>>> details like the contents of NVRAM. Your original idea of making it >>>> clear to the guest when -boot has been specified (as opposed to when >>>> it contains its default value) was the right one, and this "x" in >>>> -boot is going the wrong direction. >>> >>> Given that this is a fundamental direction for a bunch of machines, h= ow about we talk about it on the weekly QEMU call? >>> >> Was there any discussion on this in the last QEMU call? >=20 > The call is today :) ...and the topic is not officially on the agenda yet. :) Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg