[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m3fwhws6ci.fsf@blackfin.pond.sub.org>
Date: Thu, 10 Nov 2011 09:57:01 +0100
From: Markus Armbruster <armbru@...hat.com>
To: Sasha Levin <levinsasha928@...il.com>
Cc: Pekka Enberg <penberg@...nel.org>,
Anthony Liguori <anthony@...emonkey.ws>,
Pekka Enberg <penberg@...helsinki.fi>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Avi Kivity <avi@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, Christoph Hellwig <hch@....de>
Subject: Re: [RFC/GIT PULL] Linux KVM tool for v3.2
Sasha Levin <levinsasha928@...il.com> writes:
> On Thu, Nov 10, 2011 at 9:57 AM, Markus Armbruster <armbru@...hat.com> wrote:
[...]
>> Start with a clean read/write raw image. Probing declares it raw.
>> Guest writes QCOW signature to it, with a backing file of its choice.
>>
>> Restart with the same image. Probing declares it QCOW2. Guest can read
>> the backing file. Oops.
>
> Thats an excellent scenario why you'd want to have 'Secure KVM' with
> seccomp filters :)
Yup.
For what it's worth, sVirt (use SELinux to secure virtualization)
mitigates the problem. Doesn't mean we couldn't use "Secure KVM".
> I'm actually not sure why KVM tool got QCOW support in the first
> place. You can have anything QCOW provides if you use btrfs (among
> several other FSs).
Maybe it's just me, but isn't it weird to have a filesystem (QCOW2)
sitting in the kernel sources that you can't mount(2)?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists