From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Pekka Enberg <penberg@kernel.org>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, mtosatti@redhat.com,
kvm@vger.kernel.org, joro@8bytes.org, penberg@cs.helsinki.fi,
asias.hejun@gmail.com, gorcunov@gmail.com
Subject: Re: [ANNOUNCE] Native Linux KVM tool
Date: Sun, 10 Apr 2011 11:05:06 +0300 [thread overview]
Message-ID: <4DA164B2.5000504@redhat.com> (raw)
In-Reply-To: <4D9F9359.20708@codemonkey.ws>
On 04/09/2011 01:59 AM, Anthony Liguori wrote:
>
> Yeah, if that's the goal, skip all the mini-BIOS junk and just rely on
> a PV kernel in the guest.
>
> I think a mini userspace that assumes that we can change the guest
> kernel and avoids having a ton of complexity to do things like CMOS
> emulation would be a really interesting thing to do.
>
Changing the guest kernel is a lot more complicated than writing a full
BIOS or the legacy devices needed to support it. See Xen for an example.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-04-10 8:05 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 17:30 [ANNOUNCE] Native Linux KVM tool Pekka Enberg
[not found] ` <1B1AE097-4524-4026-85EC-F9A0E274FFF2@suse.de>
2011-04-01 7:07 ` Carsten Otte
2011-04-01 7:37 ` Cyrill Gorcunov
2011-04-01 14:26 ` Steven Rostedt
2011-04-02 20:38 ` Anthony Liguori
2011-04-03 6:21 ` Ingo Molnar
2011-04-03 8:24 ` Avi Kivity
2011-04-03 8:53 ` Pekka Enberg
2011-04-03 9:06 ` Cyrill Gorcunov
2011-04-03 9:37 ` CaT
2011-04-04 10:31 ` Ingo Molnar
2011-04-03 8:51 ` Pekka Enberg
2011-04-03 9:17 ` Avi Kivity
2011-04-03 8:23 ` Avi Kivity
2011-04-03 9:59 ` Pekka Enberg
2011-04-03 10:11 ` Avi Kivity
2011-04-03 10:17 ` Pekka Enberg
2011-04-03 10:22 ` Avi Kivity
2011-04-03 10:32 ` Pekka Enberg
2011-04-03 13:09 ` Anthony Liguori
2011-04-03 13:19 ` Avi Kivity
2011-04-06 9:33 ` Ingo Molnar
2011-04-06 9:36 ` Gleb Natapov
2011-04-06 9:46 ` Ingo Molnar
2011-04-06 9:49 ` Avi Kivity
2011-04-06 9:51 ` Gleb Natapov
2011-04-06 10:14 ` Olivier Galibert
2011-04-06 10:55 ` Ingo Molnar
2011-04-08 2:04 ` Anthony Liguori
2011-04-08 2:14 ` Anthony Liguori
2011-04-08 5:14 ` Pekka Enberg
2011-04-08 6:19 ` Cyrill Gorcunov
2011-04-08 6:47 ` Takuya Yoshikawa
2011-04-08 6:51 ` Pekka Enberg
2011-04-08 7:10 ` Takuya Yoshikawa
2011-04-08 7:39 ` Jan Kiszka
2011-04-08 8:27 ` Pekka Enberg
2011-04-08 9:11 ` Jan Kiszka
2011-04-08 9:32 ` Cyrill Gorcunov
2011-04-08 10:42 ` Jan Kiszka
2011-04-08 12:27 ` Alexander Graf
2011-04-08 12:33 ` Cyrill Gorcunov
2011-04-08 14:39 ` Ted Ts'o
2011-04-08 14:00 ` Anthony Liguori
2011-04-08 19:20 ` Andrea Arcangeli
2011-04-08 22:59 ` Anthony Liguori
2011-04-10 8:05 ` Avi Kivity [this message]
2011-04-09 7:40 ` Ingo Molnar
2011-04-12 0:58 ` Andrea Arcangeli
2011-04-09 18:23 ` Olivier Galibert
2011-04-10 2:54 ` Anthony Liguori
2011-04-08 15:59 ` Scott Wood
2011-04-08 19:41 ` gene heskett
2011-04-08 22:58 ` Anthony Liguori
2011-04-06 8:59 ` Markus Armbruster
2011-04-06 9:29 ` Gleb Natapov
2011-04-03 9:01 ` Alon Levy
2011-04-03 10:01 ` Pekka Enberg
2011-04-03 10:15 ` Alon Levy
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=4DA164B2.5000504@redhat.com \
--to=avi@redhat.com \
--cc=aarcange@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=penberg@cs.helsinki.fi \
--cc=penberg@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox