From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCHv2] Support for booting from virtio disks Date: Tue, 11 May 2010 11:19:07 +0300 Message-ID: <4BE912FB.9030702@redhat.com> References: <20100510081118.GI24787@redhat.com> <4BE82ADA.6000302@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Gleb Natapov , seabios@seabios.org, qemu-devel@nongnu.org, kvm@vger.kernel.org To: Anthony Liguori Return-path: Received: from mx1.redhat.com ([209.132.183.28]:6224 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750925Ab0EKITQ (ORCPT ); Tue, 11 May 2010 04:19:16 -0400 In-Reply-To: <4BE82ADA.6000302@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: 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 > > 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