From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: linux next: Native Linux KVM tool inclusion request Date: Wed, 24 Aug 2011 11:31:30 +0300 Message-ID: <4E54B6E2.2030203@redhat.com> References: <1314044960.3668.9.camel@lappy> <20110823003925.GA30253@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.redhat.com ([209.132.183.28]:8288 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752104Ab1HXIcO (ORCPT ); Wed, 24 Aug 2011 04:32:14 -0400 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Pekka Enberg Cc: Christoph Hellwig , Sasha Levin , Stephen Rothwell , linux-kernel , Ingo Molnar , Andrew Morton , Linus Torvalds , linux-next@vger.kernel.org On 08/23/2011 08:08 AM, Pekka Enberg wrote: > As for changes, we've implemented rootfs over 9p with "kvm run" > booting to host filesystem "/bin/sh" by default. Isn't this dangerous? Users expect virtualization to land them in sandbox, but here an rm -rf / in the guest will happily junk the host filesystem. > It still needs some > work and we hope to enable networking too. We also have patches to use > overlayfs so that the guest is able to use host filesystem in > copy-on-write manner. > Still dangerous (but just to the guest), since it's not a true snapshot. If the host filesystem changes underneath the guest, it will see partial and incoherent updates. Copy-on-write only works if the host filesystem doesn't change. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.