From: Juan Quintela <quintela@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: QEMU Developer <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Fwd: Re: KVM call for 2016-02-14
Date: Wed, 22 Feb 2017 13:48:37 +0100 [thread overview]
Message-ID: <87poiamlwa.fsf@emacs.mitica> (raw)
In-Reply-To: <20170215152010.GE16064@stefanha-x1.localdomain> (Stefan Hajnoczi's message of "Wed, 15 Feb 2017 15:20:10 +0000")
Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Tue, Feb 14, 2017 at 02:59:14PM +0100, Juan Quintela wrote:
>> 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
>
> This is an interesting topic. I guess everyone missed the call. Will
> this topic be discussed in the next call?
Yeap. Will send it on the agenda later.
Thanks, Juan.
prev parent reply other threads:[~2017-02-22 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 13:59 [Qemu-devel] Fwd: Re: KVM call for 2016-02-14 Juan Quintela
2017-02-15 15:20 ` Stefan Hajnoczi
2017-02-22 12:48 ` Juan Quintela [this message]
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=87poiamlwa.fsf@emacs.mitica \
--to=quintela@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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;
as well as URLs for NNTP newsgroup(s).