From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:59784) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1THBRs-0002Iw-C9 for qemu-devel@nongnu.org; Thu, 27 Sep 2012 06:36:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1THBRi-0002vD-I8 for qemu-devel@nongnu.org; Thu, 27 Sep 2012 06:36:04 -0400 Received: from e23smtp03.au.ibm.com ([202.81.31.145]:51094) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1THBRi-0002tc-0m for qemu-devel@nongnu.org; Thu, 27 Sep 2012 06:35:54 -0400 Received: from /spool/local by e23smtp03.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 27 Sep 2012 20:33:52 +1000 From: Nikunj A Dadhania In-Reply-To: <20120927101305.GL23096@redhat.com> References: <50641A82.4030708@linux.vnet.ibm.com> <1348738150.24701.21.camel@pasglop> <20120927095136.GI23096@redhat.com> <87fw63hjb2.fsf@linux.vnet.ibm.com> <20120927101305.GL23096@redhat.com> Date: Thu, 27 Sep 2012 16:04:54 +0530 Message-ID: <87a9wbhhyp.fsf@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Qemu-devel] [Qemu-ppc] Qemu boot device precedence over nvram boot-device setting List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: qemu-devel qemu-devel , Benjamin Herrenschmidt , "qemu-ppc@nongnu.org List" , Alexander Graf , Avik Sil On Thu, 27 Sep 2012 12:13:05 +0200, Gleb Natapov wrote: > On Thu, Sep 27, 2012 at 03:35:53PM +0530, Nikunj A Dadhania wrote: > > > > If the user does not set bootindex, qemu would decide the bootindex? > > > No. Firmware decides. QEMU just tells to firmware that it does not have > bootindex. Ok. That should work in that case, we need to make sure that bootindex is being send via device-tree. I do not see such code in place currently. > > > If it does, there will be a default bootindex. Then the problem still > > remains, qemu decided the boot-order, in which case we would want to > > pick the nvram based setting. This is again difficult to distinguish. > > > > > There is nothing "blurry" about OF device > > > path. The problem is that it works reasonably well with legacy BIOS > > > since it is enough to specify device to boot from, but with EFI (OF is > > > the same I guess) it is not enough to point to a device to boot from, > > > but you also need to specify a file you want to boot and this is where > > > bootindex approach fails. > > > > By file I suppose you mean OF device-path. > > > No. By file I mean a file on dedicated EFI FAT partition that EFI loads > during boot. I do not know if OF has something similar. > No, it just needs the device-path. Rest it figures out. Regards Nikunj