From: Gleb Natapov <gleb@redhat.com>
To: ron minnich <rminnich@gmail.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
Pekka Enberg <penberg@kernel.org>, John Floren <john@jfloren.net>,
Anthony Liguori <aliguori@us.ibm.com>,
kvm@vger.kernel.org, Yang Bai <hamo.by@gmail.com>,
Matt Evans <matt@ozlabs.org>,
Sasha Levin <levinsasha928@gmail.com>,
Cyrill Gorcunov <gorcunov@openvz.org>,
Asias He <asias.hejun@gmail.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC/PATCH 1/2] kvm tools, seabios: Add "--bios" option to "vm run"
Date: Mon, 27 Feb 2012 19:25:37 +0200 [thread overview]
Message-ID: <20120227172537.GD22220@redhat.com> (raw)
In-Reply-To: <CAP6exYKrgCXSogMRAkkvQvicmDBpvwGoNaWt-OLSRAUoZDr70A@mail.gmail.com>
On Mon, Feb 27, 2012 at 08:46:10AM -0800, ron minnich wrote:
> On Mon, Feb 27, 2012 at 8:38 AM, Gleb Natapov <gleb@redhat.com> wrote:
>
> > Then make kvm-tool set it. Why do you need coreboot/seabios for that?
>
> First thing we looked at. For a number of reasons it seems ugly.
That is not "ugly", this is by design. Isn't it.
> Either we can pick a bunch of fixed base addresses for the kvm-tool
> resources, and track them all as new devices are added to kvm-tool
> over time (yuck), or we can replicate some of the pci BAR code in
> kvm-tool that already exists in seabios/coreboot, which also seems
> yucky.
kvm-tool design goal, as far as I can tell, was to be as much self
contained as possible. kvm-tool should be usable without seabios at
all if legacy bios functionality is not needed. To achieve that some
firmware functionality (mostly HW initialization related) is already
replicated in kvm-tool. Again, this is by design. Coreboot, when used
in conjunction with seabios on real HW, takes care of HW initialization,
so if kvm-tool want to follow its design direction it should assume role
of the coreboot and load Seabios only when legacy bios functionality is
needed.
BTW there is code duplication between coreboot and seabios too. Both of
them can be used to init QEMU HW.
>
> kvm-tool provides a more realistic environment in some ways for guests
> than qemu.
How is kvm-tool provides a more realistic environment? You get it
opposite.
> Less is initialized.
Nothing is initialized in QEMU. Every single bit of initialization is
done by a guest code. Be it Seabios/coreboot/openfirmware/tianocore or
guest OS itself. And yes, qemu can run all of the firmwares above
without single line of code to support any of them.
> Given that coreboot does the things we
> need done, and it's easy to build, I don't see a reason not to use it.
I am not very familiar with coreboot, but I think you will have to write
kvm-tool platform support for coreboot before you can run it in
kvm-tool.
--
Gleb.
next prev parent reply other threads:[~2012-02-27 17:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 15:05 [RFC/PATCH 1/2] kvm tools, seabios: Add "--bios" option to "vm run" Pekka Enberg
2012-02-24 15:05 ` [RFC/PATCH 2/2] kvm tools, seabios: Add support for SeaBIOS debugging output Pekka Enberg
2012-02-24 15:13 ` [RFC/PATCH 1/2] kvm tools, seabios: Add "--bios" option to "vm run" Cyrill Gorcunov
2012-02-24 15:23 ` Anthony Liguori
2012-02-24 16:27 ` ron minnich
2012-02-24 16:41 ` John Floren
2012-02-24 18:54 ` Pekka Enberg
2012-02-24 19:01 ` Pekka Enberg
2012-02-24 19:18 ` Pekka Enberg
2012-02-24 19:29 ` John Floren
2012-02-25 1:14 ` John Floren
2012-02-27 10:44 ` Gerd Hoffmann
2012-02-27 11:15 ` Gleb Natapov
2012-02-27 16:24 ` ron minnich
2012-02-27 16:38 ` Gleb Natapov
2012-02-27 16:46 ` ron minnich
2012-02-27 17:25 ` Gleb Natapov [this message]
2012-02-27 17:29 ` ron minnich
2012-02-27 10:37 ` Gerd Hoffmann
2012-02-24 18:00 ` Pekka Enberg
2012-02-24 19:07 ` ron minnich
2012-02-24 19:13 ` Pekka Enberg
2012-02-24 17:58 ` Pekka Enberg
2012-02-25 23:35 ` Matt Evans
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=20120227172537.GD22220@redhat.com \
--to=gleb@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@openvz.org \
--cc=hamo.by@gmail.com \
--cc=john@jfloren.net \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=matt@ozlabs.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=rminnich@gmail.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