From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Pauline Middelink <middelink@polyware.nl>,
kvm@vger.kernel.org
Subject: Re: kvm-85 won't boot guests with virtio block device
Date: Sun, 26 Apr 2009 13:27:14 +0300 [thread overview]
Message-ID: <49F43702.4050401@redhat.com> (raw)
In-Reply-To: <49F24F49.3000305@us.ibm.com>
Anthony Liguori wrote:
> Marcelo Tosatti wrote:
>> Pauline,
>>
>> Good catch.
>>
>> Anthony, what is the reason for extboot not being upstream?
>>
>
> Paul Brook nacked it.
> He didn't like that it was so x86 specific.
Which part? The guest/host interface, or the option rom part?
> I think a better approach that would be mergable is something based on
> the FW config interface with the driver code living as a patch to the
> Bochs BIOS.
The firmware interface is for reading configuration information. It's
an idempotent, zero-latency interface. Let's not mix it with disk
sector read/writes which is a completely different thing.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-04-26 10:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 17:18 kvm-85 won't boot guests with virtio block device Pauline Middelink
2009-04-24 23:25 ` Marcelo Tosatti
2009-04-24 23:46 ` Anthony Liguori
2009-04-24 23:47 ` Anthony Liguori
2009-04-26 10:27 ` Avi Kivity [this message]
2009-04-25 20:13 ` Gerd v. Egidy
2009-04-26 10:25 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2009-04-27 7:57 Pauline Middelink
2009-04-27 9:00 ` Avi Kivity
2009-04-23 11:00 Darius Drozdowski
2009-04-23 12:05 ` Gerd v. Egidy
2009-04-23 12:40 ` Bernhard Held
2009-04-23 12:49 ` Alexey Eremenko
2009-04-23 13:27 ` Gerd v. Egidy
2009-04-23 13:49 ` Bernhard Held
2009-04-23 14:01 ` Gerd v. Egidy
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=49F43702.4050401@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=middelink@polyware.nl \
--cc=mtosatti@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox