All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 0/2] port over extboot from kvm
Date: Tue, 08 Sep 2009 19:05:15 +0300	[thread overview]
Message-ID: <4AA680BB.5020201@redhat.com> (raw)
In-Reply-To: <4AA66B10.2050901@codemonkey.ws>

On 09/08/2009 05:32 PM, Anthony Liguori wrote:
> 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".

It's not just booting - it's the int 0x13 interface.  Grub for example 
continues to use it and can boot from the second hard disk if desired.


>
> 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.

I agree with this and I think we should extend it to boot=0x80|0x81....  
boot=on is an alias to boot=0x80.

>
> 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.
>


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

  reply	other threads:[~2009-09-08 16:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08  9:17 [Qemu-devel] [PATCH 0/2] port over extboot from kvm Gerd Hoffmann
2009-09-08  9:17 ` [Qemu-devel] [PATCH 1/2] extboot: add option rom Gerd Hoffmann
2009-09-08  9:17 ` [Qemu-devel] [PATCH 2/2] extboot: qemu code Gerd Hoffmann
2009-09-08 11:59 ` [Qemu-devel] [PATCH 0/2] port over extboot from kvm Gerd Hoffmann
2009-09-08 13:47 ` [Qemu-devel] " Jan Kiszka
2009-09-08 14:22   ` Gerd Hoffmann
2009-09-08 14:32     ` Anthony Liguori
2009-09-08 16:05       ` Avi Kivity [this message]
2009-09-08 17:21         ` Anthony Liguori
2009-09-08 19:11           ` Avi Kivity
2009-09-08 19:46             ` Anthony Liguori
2009-09-08 20:00               ` Avi Kivity
2009-09-08 20:10                 ` Anthony Liguori
2009-09-12 15:03         ` Kevin O'Connor
2009-09-08 14:40     ` Jan Kiszka
2009-09-08 14:52       ` Gerd Hoffmann
2009-09-08 16:15         ` Jan Kiszka
2009-09-08 17:12           ` Anthony Liguori
2009-09-08 19:03             ` Gerd Hoffmann
2009-09-08 19:39               ` Anthony Liguori
2009-09-12 15:43       ` Kevin O'Connor
2009-09-08 14:16 ` [Qemu-devel] " Anthony Liguori
2009-11-09 16:06   ` Paul Brook
2009-11-09 16:31     ` Gerd Hoffmann
2009-11-09 16:40       ` Anthony Liguori
2009-11-11 13:01         ` Hannes Reinecke
2009-11-11 13:25           ` Anthony Liguori
2009-11-11 13:54             ` Paul Brook

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=4AA680BB.5020201@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=jan.kiszka@siemens.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.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.