From: Pekka Enberg <penberg@kernel.org>
To: Avi Kivity <avi@redhat.com>
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 12:38:43 +0300 [thread overview]
Message-ID: <4E54C6A3.3070606@kernel.org> (raw)
In-Reply-To: <4E54C55A.7010109@redhat.com>
On 8/24/11 12:33 PM, Avi Kivity wrote:
> Well, just trashing /home/penberg would be bad too, no? (my recent
> experience indicates it's not that catastrophic - anything important
> sits on a server somewhere and the local data is just a cache).
Sure. We actually are planning something like this:
Private to guest:
/dev
/etc
/home
/proc
/sys
/var
Shared from host rootfs:
/bin
/lib
/sbin
/usr
Full host rootfs mounted at:
/host/
And no, we're not planning to boot full distro init. The only thing we
really want in addition to /bin/sh is to enable networking.
Pekka
next prev parent reply other threads:[~2011-08-24 9:38 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
2011-08-24 9:19 ` Pekka Enberg
2011-08-24 9:33 ` Avi Kivity
2011-08-24 9:38 ` Pekka Enberg [this message]
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=4E54C6A3.3070606@kernel.org \
--to=penberg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--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=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).