From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC/GIT PULL] Linux KVM tool for v3.2 Date: Thu, 10 Nov 2011 11:43:00 +0200 Message-ID: <4EBB9CA4.3050606@redhat.com> References: <4EBB4A21.20707@codemonkey.ws> <4EBB94D9.30906@redhat.com> <4EBB9809.1080603@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Markus Armbruster , Pekka Enberg , Anthony Liguori , Pekka Enberg , Linus Torvalds , Andrew Morton , Ingo Molnar , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Christoph Hellwig To: Sasha Levin Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 11/10/2011 11:34 AM, Sasha Levin wrote: > On Thu, Nov 10, 2011 at 11:23 AM, Avi Kivity wrote: > > On 11/10/2011 11:14 AM, Sasha Levin wrote: > >> > Trying and failing. sVirt will deny access to all files except those > >> > explicitly allowed by libvirt. > >> > >> It still allows the guest to read more than enough files which it > >> shouldn't be reading. > >> > >> Unless you configure sVirt on a per-guest basis... > > > > sVirt is per-guest. > > It still would mean that the guest can access any file (actually, even > device, no?) the hypervisor can access. It does, but the hypervisor can only access the guest's images, and a few internal files (like the qemu-kvm executable and its libraries). -- error compiling committee.c: too many arguments to function