From: Avi Kivity <avi@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Ingo Molnar <mingo@elte.hu>, Pekka Enberg <penberg@kernel.org>,
Cyrill Gorcunov <gorcunov@gmail.com>,
Asias He <asias.hejun@gmail.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Rusty Russell <rusty@rustcorp.com.au>,
"Michael S. Tsirkin" <mst@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: Secure KVM
Date: Mon, 07 Nov 2011 14:51:38 +0200 [thread overview]
Message-ID: <4EB7D45A.8040000@redhat.com> (raw)
In-Reply-To: <CA+1xoqefq3crCj3+Nm2oLEH7cVmwW3J1BYLb-oet-th23++-aQ@mail.gmail.com>
On 11/07/2011 02:40 PM, Sasha Levin wrote:
> >
> > Where does the VNC server, the image formats, etc go? It would be
> > nice to confine them too.
>
> Regarding image formats, just wondering - was there ever any plan to
> merge (at least some of them) into the kernel?
Xen has/had something where (IIUC) the kernel would call out on an
unmapped cluster, let userspace figure out the mapping, then service
requests to that cluster completely in the kernel. I'm not convinced
it's worthwhile.
btw, the kernel already has support for a flexible copy-on-write format
- btrfs raw files. It makes sense to increase the integration there.
You can keep image files as ordinary files, use COW for snapshots, and
implement exporting to qcow via SEEK_HOLE.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-11-07 12:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 20:40 Secure KVM Sasha Levin
2011-11-07 0:07 ` Rusty Russell
2011-11-07 6:29 ` Sasha Levin
2011-11-07 6:37 ` Pekka Enberg
2011-11-07 6:46 ` Sasha Levin
2011-11-07 7:03 ` Pekka Enberg
2011-11-07 22:49 ` Rusty Russell
2011-11-07 9:26 ` Avi Kivity
2011-11-07 10:17 ` Sasha Levin
2011-11-07 10:27 ` Avi Kivity
2011-11-07 11:27 ` Stefan Hajnoczi
2011-11-07 12:40 ` Sasha Levin
2011-11-07 12:51 ` Avi Kivity [this message]
2011-11-07 14:56 ` Stefan Hajnoczi
2011-11-07 17:43 ` Anthony Liguori
2011-11-07 18:41 ` Avi Kivity
2011-11-07 17:39 ` Anthony Liguori
2011-11-07 18:43 ` Avi Kivity
2011-11-07 19:07 ` Anthony Liguori
2011-11-07 19:54 ` Avi Kivity
2011-11-07 22:56 ` Rusty Russell
2011-11-07 17:37 ` Anthony Liguori
2011-11-07 17:52 ` Sasha Levin
2011-11-07 18:03 ` [Qemu-devel] " Anthony Liguori
2011-11-07 23:06 ` Rusty Russell
2011-11-08 19:51 ` Will Drewry
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=4EB7D45A.8040000@redhat.com \
--to=avi@redhat.com \
--cc=aarcange@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mingo@elte.hu \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=penberg@kernel.org \
--cc=rusty@rustcorp.com.au \
--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