From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=50319 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OBkgS-00074s-8f
	for qemu-devel@nongnu.org; Tue, 11 May 2010 04:19:21 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1OBkgL-0004Vi-0j
	for qemu-devel@nongnu.org; Tue, 11 May 2010 04:19:20 -0400
Received: from mx1.redhat.com ([209.132.183.28]:23242)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1OBkgK-0004VQ-PC
	for qemu-devel@nongnu.org; Tue, 11 May 2010 04:19:12 -0400
Message-ID: <4BE912FB.9030702@redhat.com>
Date: Tue, 11 May 2010 11:19:07 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <20100510081118.GI24787@redhat.com>
	<4BE82ADA.6000302@codemonkey.ws>
In-Reply-To: <4BE82ADA.6000302@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: [PATCHv2] Support for booting from virtio disks
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.nongnu.org/archive/html/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: Anthony Liguori <anthony@codemonkey.ws>
Cc: seabios@seabios.org, qemu-devel@nongnu.org, Gleb Natapov <gleb@redhat.com>, kvm@vger.kernel.org

On 05/10/2010 06:48 PM, Anthony Liguori wrote:
> On 05/10/2010 03:11 AM, Gleb Natapov wrote:
>> This patch adds native support for booting from virtio disks to Seabios.
>>
>> Signed-off-by: Gleb Natapov<gleb@redhat.com>
>
> A related problem that I think we need to think about how we solve is 
> indicating to Seabios which device we want to boot from
>
> With your patch, a user can select a virtio device explicitly or if 
> they use only one virtio device, it will Just Work.
>
> However, if a user uses IDE and virtio, or a user has multiple disks, 
> they cannot select a device via -boot.
>
> Is this something we need to address?  I don't think we'd break 
> libvirt if we didn't.

BIOSes traditionally address this by storing the boot order in RTC 
non-volatile memory, and allow the user to configure the order via a 
menu.  We could do the same (storing the RTC memory in a small disk image).

Alternatively we can seed the order from the command line (-boot 
id1,id2,id3 where id* are some qdev property attached to disks, this is 
more flexible than the current syntax I think).

-- 
error compiling committee.c: too many arguments to function