From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
"Kevin O'Connor" <kevin@koconnor.net>,
Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
Stefan Hajnoczi <stefan.hajnoczi@uk.ibm.com>
Subject: Re: [PATCH 1/2] qemu-kvm: extboot: Keep variables in RAM
Date: Fri, 19 Feb 2010 19:17:34 +0100 [thread overview]
Message-ID: <4B7ED5BE.8030706@siemens.com> (raw)
In-Reply-To: <4B7ED419.7080709@codemonkey.ws>
Anthony Liguori wrote:
> On 02/19/2010 11:03 AM, Jan Kiszka wrote:
>> Actually, I'm still in favor of proper (Sea)BIOS support for virtio and
>> scsi, either via the paravirt port 0x405 and its qemu backend or via
>> minimalistic support of the hardware directly in the BIOS. That would
>> free us from all those hooking and unhooking dances at least.
>>
>> Kevin, Anthony, and all others: what is now the merge road map for the
>> bootable scsi/virtio feature?
>>
>
> Stefan posted a virtio-blk driver for gPXE. I like this approach
> because it's generally useful (gPXE can be used with any BIOS).
Does it allow a unified boot device selection, one menu for them all, no
more "boot=on" workarounds?
>
> For the LSI SCSI adapter, I'm not really sure the best way forward.
> Honestly, it's so broken currently, I'm not sure booting really matters.
Well, we are successfully using this "broken" adapter. What is not working?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2010-02-19 18:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 16:13 [PATCH 1/2] qemu-kvm: extboot: Keep variables in RAM Jan Kiszka
2010-02-18 20:27 ` Anthony Liguori
2010-02-18 22:56 ` H. Peter Anvin
2010-02-19 10:06 ` Jan Kiszka
2010-02-19 16:50 ` H. Peter Anvin
2010-02-19 17:03 ` Jan Kiszka
2010-02-19 17:24 ` H. Peter Anvin
2010-02-19 17:44 ` Jan Kiszka
2010-02-19 18:10 ` Anthony Liguori
2010-02-19 18:17 ` Jan Kiszka [this message]
2010-02-19 19:37 ` H. Peter Anvin
2010-02-20 3:21 ` Kevin O'Connor
2010-02-22 10:03 ` Stefan Hajnoczi
[not found] ` <4B82DE3F.5090306@linux.intel.com>
2010-02-23 9:30 ` Stefan Hajnoczi
2010-02-22 9:40 ` Avi Kivity
2010-02-22 9:59 ` Jan Kiszka
2010-02-22 10:03 ` Jan Kiszka
2010-02-22 11:02 ` Avi Kivity
2010-04-06 8:50 ` Jan Kiszka
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=4B7ED5BE.8030706@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=hpa@linux.intel.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=stefan.hajnoczi@uk.ibm.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