From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Glauber Costa <glommer@redhat.com>,
aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] remove pieces of source code
Date: Fri, 29 May 2009 12:20:59 +0200 [thread overview]
Message-ID: <4A1FB70B.4090808@siemens.com> (raw)
In-Reply-To: <20090529100017.GD29375@redhat.com>
Daniel P. Berrange wrote:
> On Fri, May 29, 2009 at 11:08:38AM +0200, Jan Kiszka wrote:
>> Anthony Liguori wrote:
>>
>>> o There is no alternative for non-Linux users and folks with non-VT/SVM
>>> hardware
>> The non-HVM argument will become widely irrelevant (for desktops) very
>> soon. The non-Linux issue will likely persist - unless someone feels so
>> much pain to write some KVM for those platforms. But as long as there is
>> a kqemu version that builds and works for them, I think we should keep
>> QEMU's support. But it should no longer be a first-class citizen: off by
>> default, factored out into more hooks, maybe even de-optimized where it
>> blocks development or increases the maintenance effort of QEMU.
>
> The non-HVM argument will always exist, and could actually get worse
> if lots of vendors start shipping with embedded hypervisors, such that
> your 'real' OS is already virtualized behind your back. That said I do
Nested virtualization like this would have been one nice-to-have via
kqemu. And in fact, most of our development took place inside kvm. But
the performance was worse than qemu inside kvm, at least for our use cases.
That said, there might be scenarios where kqemu inside whatever
hypervisor provides better performance than emulation, but I can only
recommend to evaluate this carefully. The overhead of virtualizing
kqemu's monitor activities can be enormous.
> agree with you - we're still better off killing/deprecating kqemu and
> using any spare effort to improve nested-SVM/VT support which is a more
> useful long term feature.
>
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-05-29 10:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 23:03 [Qemu-devel] [PATCH] remove pieces of source code Glauber Costa
2009-05-29 5:50 ` Anthony Liguori
2009-05-29 9:08 ` [Qemu-devel] " Jan Kiszka
2009-05-29 9:12 ` Anthony Liguori
2009-05-29 9:35 ` Stefan Weil
2009-06-02 20:09 ` Stuart Brady
2009-06-02 20:29 ` Avi Kivity
2009-05-29 10:00 ` Daniel P. Berrange
2009-05-29 10:20 ` Jan Kiszka [this message]
2009-05-29 11:35 ` Glauber Costa
2009-05-30 18:04 ` François Revol
2009-05-31 9:13 ` Jan Kiszka
2009-05-31 14:53 ` Jamie Lokier
2009-05-31 15:43 ` Jan Kiszka
2009-05-29 11:32 ` [Qemu-devel] " Glauber Costa
2009-05-29 11:42 ` Gerd Hoffmann
2009-05-29 15:43 ` [Qemu-devel] " Consul
2009-05-29 18:49 ` Glauber Costa
2009-05-30 10:26 ` Andreas Färber
2009-05-31 9:15 ` Jan Kiszka
2009-05-31 13:08 ` Andreas Färber
2009-05-31 13:40 ` Avi Kivity
2009-05-31 16:20 ` M. Warner Losh
2009-05-31 15:10 ` Jan Kiszka
2009-06-06 10:17 ` Andreas Färber
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=4A1FB70B.4090808@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aliguori@us.ibm.com \
--cc=berrange@redhat.com \
--cc=glommer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).