From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Ml1kh-0000xq-5E
	for qemu-devel@nongnu.org; Tue, 08 Sep 2009 10:32:59 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Ml1kc-0000wX-7K
	for qemu-devel@nongnu.org; Tue, 08 Sep 2009 10:32:58 -0400
Received: from [199.232.76.173] (port=44195 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Ml1kb-0000wR-TI
	for qemu-devel@nongnu.org; Tue, 08 Sep 2009 10:32:53 -0400
Received: from mail-qy0-f191.google.com ([209.85.221.191]:64323)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1Ml1kb-0005GK-Hi
	for qemu-devel@nongnu.org; Tue, 08 Sep 2009 10:32:53 -0400
Received: by qyk29 with SMTP id 29so2575898qyk.16
	for <qemu-devel@nongnu.org>; Tue, 08 Sep 2009 07:32:51 -0700 (PDT)
Message-ID: <4AA66B10.2050901@codemonkey.ws>
Date: Tue, 08 Sep 2009 09:32:48 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [PATCH 0/2] port over extboot from kvm
References: <1252401463-3249-1-git-send-email-kraxel@redhat.com>	<4AA6607C.4050505@siemens.com>
	<4AA668A2.1080801@redhat.com>
In-Reply-To: <4AA668A2.1080801@redhat.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel@nongnu.org

Gerd Hoffmann wrote:
> 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

x86 boot is strange.  The BIOS boots from the "first hard disk"  What 
extboot allows you do to is redefine to the bios what constitutes the 
"first hard disk".

This is the motivation for making it a -drive option.  Perhaps this is 
something we want to hide from the user but that was the motivation.

For instance, it would not be possible to define a boot sequence of 
"first virtio disk, then second virtio disk, then cdrom" because we 
can't present two disks as the first hard disk.

If extboot supported BCV and our bios did, the above would be possible.

Regards,

Anthony Liguori