On Thu, Nov 10, 2011 at 11:43 AM, Avi Kivity <avi@xxxxxxxxxx> wrote: > On 11/10/2011 11:34 AM, Sasha Levin wrote: >> On Thu, Nov 10, 2011 at 11:23 AM, Avi Kivity <avi@xxxxxxxxxx> 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). What about devices? You let the guest read and write to devices as well (/dev/kvm for example, or network devices). -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
