From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ml1ae-0001WS-2q for qemu-devel@nongnu.org; Tue, 08 Sep 2009 10:22:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ml1aZ-0001U0-TY for qemu-devel@nongnu.org; Tue, 08 Sep 2009 10:22:35 -0400 Received: from [199.232.76.173] (port=40960 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ml1aZ-0001Tq-Jm for qemu-devel@nongnu.org; Tue, 08 Sep 2009 10:22:31 -0400 Received: from mx1.redhat.com ([209.132.183.28]:28071) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ml1aZ-0003Xu-5Q for qemu-devel@nongnu.org; Tue, 08 Sep 2009 10:22:31 -0400 Message-ID: <4AA668A2.1080801@redhat.com> Date: Tue, 08 Sep 2009 16:22:26 +0200 From: Gerd Hoffmann MIME-Version: 1.0 References: <1252401463-3249-1-git-send-email-kraxel@redhat.com> <4AA6607C.4050505@siemens.com> In-Reply-To: <4AA6607C.4050505@siemens.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 0/2] port over extboot from kvm List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: qemu-devel@nongnu.org On 09/08/09 15:47, Jan Kiszka wrote: > Before setting this definitely useful feature in stone, I have two > questions though: > > - -drive ...,boot=on is logically in conflict with -boot. Yes, -boot > for x86 currently cannot differentiate between multiple disks, only > between boot media types. Still, this two-stage configuration is > rather unintuitive and looks like a patchwork. Given that we have > full control over all components, is it really the preferred > approach? I already thought about, e.g., -boot c2 to select the > second disk. Not that nice, but I would rather vote for a consistent > configuration than a scattered one. Disk numbers are bad. Define "second hard disk". Especially for a system with different kinds of disks (say one scsi and one virtio). Drives have names though which can be used to reference the disks, so we could use that instead. -boot cmd line syntax becomes a bit tricky then though, we somehow have to figure whenever the user gave us names or old-style letters. Something like this ... -drive if=virtio,id=sys,file=/path/to/disk.img -cdrom /path/to/install.iso -boot order=[sys],once=d,menu=off ... might work out nicely. I suspect the libvirt folks will hate us for that though. > - This is just an implementation detail: Do we really need to implement > booting from virtio and scsi via an extension rom? Isn't it possible > to merge the corresponding support into the main bios? Well. There are quite a few. bochs pcbios, seabios, coreboot ... cheers, Gerd