All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Gleb Natapov <gleb@redhat.com>,
	seabios@seabios.org, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCHv2] Support for booting from virtio disks
Date: Tue, 11 May 2010 11:19:07 +0300	[thread overview]
Message-ID: <4BE912FB.9030702@redhat.com> (raw)
In-Reply-To: <4BE82ADA.6000302@codemonkey.ws>

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


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: seabios@seabios.org, qemu-devel@nongnu.org,
	Gleb Natapov <gleb@redhat.com>,
	kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCHv2] Support for booting from virtio disks
Date: Tue, 11 May 2010 11:19:07 +0300	[thread overview]
Message-ID: <4BE912FB.9030702@redhat.com> (raw)
In-Reply-To: <4BE82ADA.6000302@codemonkey.ws>

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

  parent reply	other threads:[~2010-05-11  8:19 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10  8:11 [PATCHv2] Support for booting from virtio disks Gleb Natapov
2010-05-10  8:11 ` [Qemu-devel] " Gleb Natapov
2010-05-10  8:25 ` Stefan Hajnoczi
2010-05-10  8:25   ` [Qemu-devel] " Stefan Hajnoczi
2010-05-10  8:29   ` Gleb Natapov
2010-05-10  8:29     ` [Qemu-devel] " Gleb Natapov
2010-05-10 15:48 ` Anthony Liguori
2010-05-10 15:48   ` [Qemu-devel] " Anthony Liguori
2010-05-10 15:54   ` Gleb Natapov
2010-05-10 15:54     ` [Qemu-devel] " Gleb Natapov
2010-05-10 15:58     ` Anthony Liguori
2010-05-10 15:58       ` [Qemu-devel] " Anthony Liguori
2010-05-10 16:09       ` Gleb Natapov
2010-05-10 16:09         ` [Qemu-devel] " Gleb Natapov
2010-05-13 16:49       ` [SeaBIOS] " Avi Kivity
2010-05-13 16:49         ` [Qemu-devel] " Avi Kivity
2010-05-16  8:28         ` Gleb Natapov
2010-05-16  8:28           ` [Qemu-devel] " Gleb Natapov
2010-05-11  8:19   ` Avi Kivity [this message]
2010-05-11  8:19     ` [Qemu-devel] " Avi Kivity
2010-05-11  9:04     ` Stefan Hajnoczi
2010-05-11  9:04       ` [Qemu-devel] " Stefan Hajnoczi
2010-05-11 12:33       ` Gleb Natapov
2010-05-11 12:33         ` [Qemu-devel] " Gleb Natapov
2010-05-11 12:45       ` [SeaBIOS] " Kevin O'Connor
2010-05-11 12:45         ` [Qemu-devel] " Kevin O'Connor
2010-05-11 12:47         ` Gleb Natapov
2010-05-11 12:47           ` [Qemu-devel] " Gleb Natapov
2010-05-12  0:44           ` Kevin O'Connor
2010-05-12  0:44             ` [Qemu-devel] " Kevin O'Connor
2010-05-11 12:31     ` Gleb Natapov
2010-05-11 12:31       ` [Qemu-devel] " Gleb Natapov
2010-05-12  7:22       ` Avi Kivity
2010-05-12  7:22         ` [Qemu-devel] " Avi Kivity
2010-05-12  7:55         ` Gleb Natapov
2010-05-12  7:55           ` [Qemu-devel] " Gleb Natapov
2010-05-12 12:57         ` Kevin O'Connor
2010-05-12 12:57           ` [Qemu-devel] " Kevin O'Connor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BE912FB.9030702@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.