From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50726) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zj228-0002tR-7p for qemu-devel@nongnu.org; Mon, 05 Oct 2015 05:26:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zj224-0007Jx-63 for qemu-devel@nongnu.org; Mon, 05 Oct 2015 05:26:12 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58563) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zj224-0007Jp-0G for qemu-devel@nongnu.org; Mon, 05 Oct 2015 05:26:08 -0400 Message-ID: <1444037164.14636.33.camel@redhat.com> From: Gerd Hoffmann Date: Mon, 05 Oct 2015 11:26:04 +0200 In-Reply-To: <20151002134041.GB16190@morn.lan> References: <1443701677-13629-1-git-send-email-markmb@redhat.com> <1443701819-13855-1-git-send-email-markmb@redhat.com> <1443701819-13855-7-git-send-email-markmb@redhat.com> <560D5057.6010308@redhat.com> <1443773357.14636.6.camel@redhat.com> <20151002134041.GB16190@morn.lan> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v4 6/7] Make the kernel image in the fw_cfg DMA interface bootable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin O'Connor Cc: Drew , Stefan Hajnoczi , "Gabriel L. Somlo" , qemu-devel@nongnu.org, Marc =?ISO-8859-1?Q?Mar=ED?= , Laszlo Ersek On Fr, 2015-10-02 at 09:40 -0400, Kevin O'Connor wrote: > On Fri, Oct 02, 2015 at 10:09:17AM +0200, Gerd Hoffmann wrote: > > > - read four bytes from under the fw_cfg selector QEMU_CFG_KERNEL_SIZE > > > (0x0008), > > > - if it is zero, return -1 --> no kernel boot requested, > > > - if it is nonzero, return 0 --> which means "top priority". > > > > > > In other words, I agree with: > > > > > > > - option_rom[nb_option_roms].bootindex = 0; > > > > + option_rom[nb_option_roms].bootindex = 1; > > The bootindex in QEMU is not visible in the firmware, so if the rest > of patch 6 is dropped then the above should be dropped as well. > > > Hmm. That makes the boot order undefined for "qemu -kernel foo -device > > virtio-blk,drive=bar,bootindex=1" when using an old seabios. I don't > > think this is a good idea. > > Wouldn't that make the bootorder undefined everywhere? What does it > mean to use -kernel and specify a bootorder? Kernel gets priority 0, everything else what you specify (typically configs start with bootindex=1), so the kernel gets the highest priority. So unless the user uses F12 to enter the boot menu and picks something else the kernel is booted. cheers, Gerd