From: Avi Kivity <avi@redhat.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Sasha Levin <levinsasha928@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-next@vger.kernel.org
Subject: Re: linux next: Native Linux KVM tool inclusion request
Date: Wed, 24 Aug 2011 11:31:30 +0300 [thread overview]
Message-ID: <4E54B6E2.2030203@redhat.com> (raw)
In-Reply-To: <CAOJsxLEgm_-N6297kHqSjFLCtX-Vd204S=+4Q=+GW9HYiWj1eg@mail.gmail.com>
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.
next prev parent reply other threads:[~2011-08-24 8:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 20:29 linux next: Native Linux KVM tool inclusion request Sasha Levin
2011-08-23 0:39 ` Christoph Hellwig
2011-08-23 5:08 ` Pekka Enberg
2011-08-23 6:58 ` Stephen Rothwell
2011-08-23 7:02 ` Pekka Enberg
2011-08-24 8:31 ` Avi Kivity [this message]
2011-08-24 9:19 ` Pekka Enberg
2011-08-24 9:33 ` Avi Kivity
2011-08-24 9:38 ` Pekka Enberg
2011-08-24 1:52 ` Stephen Rothwell
2011-08-24 4:33 ` Sasha Levin
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=4E54B6E2.2030203@redhat.com \
--to=avi@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).