From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55588) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zi0j7-000328-EG for qemu-devel@nongnu.org; Fri, 02 Oct 2015 09:50:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zi0j3-0002rx-Ku for qemu-devel@nongnu.org; Fri, 02 Oct 2015 09:50:21 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52596) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zi0j3-0002rJ-BT for qemu-devel@nongnu.org; Fri, 02 Oct 2015 09:50:17 -0400 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> From: Laszlo Ersek Message-ID: <560E8B96.5040000@redhat.com> Date: Fri, 2 Oct 2015 15:50:14 +0200 MIME-Version: 1.0 In-Reply-To: <20151002134041.GB16190@morn.lan> Content-Type: text/plain; charset=windows-1252 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 , Gerd Hoffmann Cc: "Gabriel L. Somlo" , Stefan Hajnoczi , =?UTF-8?Q?Marc_Mar=c3=ad?= , Drew , qemu-devel@nongnu.org On 10/02/15 15:40, 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? OVMF & AAVMF look at QEMU_CFG_KERNEL_SIZE first, and process the bootorder only after. (The kernel boot can fail due to various reasons, after which it makes sense to start processing the bootorder fw_cfg file.) Thanks Laszlo