From: Peter Maydell <peter.maydell@linaro.org>
To: Juan Quintela <quintela@redhat.com>
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
QEMU Developer <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] KVM call for 2017-03-14
Date: Mon, 13 Mar 2017 11:02:01 +0100 [thread overview]
Message-ID: <CAFEAcA978SJemCfYJPa8jwtuhhi6JGh9pEDGYNJ1npJA3nvEQA@mail.gmail.com> (raw)
In-Reply-To: <87tw6y8bs8.fsf@secure.mitica>
On 12 March 2017 at 21:45, Juan Quintela <quintela@redhat.com> wrote:
>
>
> Hi
>
> Please, send any topic that you are interested in covering.
>
> So far the agenda is:
>
> - Direction of QEMU and toolstack in light of Google Cloud blog:
> https://cloudplatform.googleblog.com/2017/01/7-ways-we-harden-our-KVM-hypervisor-at-Google-Cloud-security-in-plaintext.html
Ah, I'd forgotten that this was on the call agenda. I actually
had an interesting conversation with Alex Graf last week about
some similar topics, which I guess you could generally summarize
as "what are the issues we need to address as a project in order
to not become irrelevant in five years time". Since I wrote them
up for an internal "what I did on my holi^Wconference trip" report
I might as well repost them here:
- on the "VM support" side, QEMU is more used because it's the only
production-quality option in this space, rather than because its
users love it. (cf the Google choice to replace it.) It's also got
a pretty poor security record. It wouldn't be too surprising if
some time in the next five years somebody writes a replacement in
a safer language (perhaps also targeting only the VM support role)
and it got enough mindshare and takeup to eclipse QEMU.
[Is it too early/daft to think about prototyping being able to
write QEMU device emulation in Rust ?]
If the "VM support" usecase moves to another project then QEMU
will become a very quiet backwater...
- on the "emulation" side, nobody is clearly articulating a purpose
for QEMU, a reason why you should use it rather than other modelling
technologies (or rather than using real hardware). As a result the
efforts applied to QEMU are somewhat unfocused. Are we trying to be:
. a dev platform before easy h/w availability?
[not easy for QEMU for several reasons]
. a dev tool that provides better introspection into guest
behaviour than running on h/w?
[if so we should put more work into improving our introspection
and guest tracing capabilities!]
. primarily a tool for doing automated CI testing and one-off
developer smoke-testing that's easier to set up and scale than
trying to test on real h/w?
. something else?
[your idea goes here!]
- in all areas our legacy code and back-compatibility requirements
are threatening to choke forward progress if we don't make serious
efforts to get on top of them
- there's no easy way for people to use parts of QEMU like the CPU
emulation, or to add their own devices without having to write lots
of C code (we're firmly in a "one monolithic blob of code" setup
right now and disentangling and setting clear API dividing lines
will be a lot of work)
[Making QEMU more modular would help with defeating the legacy
and back-compat dragons, though]
thanks
-- PMM
next prev parent reply other threads:[~2017-03-13 10:02 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 20:45 KVM call for 2017-03-14 Juan Quintela
2017-03-12 20:45 ` [Qemu-devel] " Juan Quintela
2017-03-13 10:02 ` Peter Maydell [this message]
2017-03-13 12:50 ` Alex Bennée
2017-03-13 14:12 ` Juan Quintela
2017-03-13 14:12 ` [Qemu-devel] " Juan Quintela
2017-03-13 14:17 ` Peter Maydell
2017-03-13 14:17 ` [Qemu-devel] " Peter Maydell
2017-03-14 8:03 ` Stefan Hajnoczi
2017-03-14 8:13 ` Stefan Hajnoczi
2017-03-14 8:37 ` Peter Maydell
2017-03-14 8:59 ` Juan Quintela
2017-03-14 8:59 ` [Qemu-devel] " Juan Quintela
2017-03-14 10:56 ` Peter Maydell
2017-03-14 10:56 ` [Qemu-devel] " Peter Maydell
2017-03-15 8:39 ` Christian Borntraeger
2017-03-15 8:39 ` [Qemu-devel] " Christian Borntraeger
2017-03-15 10:29 ` Greg Kurz
2017-03-15 11:25 ` Laurent Vivier
2017-03-15 11:25 ` Laurent Vivier
2017-03-15 16:35 ` Greg Kurz
2017-03-14 16:01 ` Dr. David Alan Gilbert
2017-03-14 16:20 ` Daniel P. Berrange
2017-03-14 16:54 ` Obsolete QEMU host environments (was: Re: KVM call for 2017-03-14) Thomas Huth
2017-03-14 16:54 ` [Qemu-devel] " Thomas Huth
2017-03-14 17:07 ` Peter Maydell
2017-03-14 17:07 ` [Qemu-devel] " Peter Maydell
2017-03-14 21:09 ` Obsolete QEMU host environments Richard Henderson
2017-03-14 21:09 ` [Qemu-devel] " Richard Henderson
2017-03-15 9:40 ` Daniel P. Berrange
2017-03-15 9:40 ` [Qemu-devel] " Daniel P. Berrange
2017-03-15 10:02 ` Thomas Huth
2017-03-15 10:02 ` [Qemu-devel] " Thomas Huth
2017-03-15 15:46 ` Aurelien Jarno
2017-03-15 15:46 ` [Qemu-devel] " Aurelien Jarno
2017-03-14 17:14 ` [Qemu-devel] KVM call for 2017-03-14 Paolo Bonzini
2017-03-14 17:18 ` Peter Maydell
2017-03-14 17:29 ` Dr. David Alan Gilbert
2017-03-15 8:30 ` Gerd Hoffmann
2017-03-14 9:33 ` Markus Armbruster
2017-03-14 8:53 ` Juan Quintela
2017-03-14 8:53 ` [Qemu-devel] " Juan Quintela
2017-03-14 10:39 ` Peter Maydell
2017-03-14 10:44 ` Paolo Bonzini
2017-03-14 9:24 ` Thomas Huth
2017-03-14 10:13 ` Kevin Wolf
2017-03-14 12:20 ` Markus Armbruster
2017-03-14 12:35 ` Kevin Wolf
2017-03-14 10:32 ` Peter Maydell
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=CAFEAcA978SJemCfYJPa8jwtuhhi6JGh9pEDGYNJ1npJA3nvEQA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.