[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84144f021003220550g6420b659kefaf2a31dc9144b7@mail.gmail.com>
Date: Mon, 22 Mar 2010 14:50:50 +0200
From: Pekka Enberg <penberg@...helsinki.fi>
To: Avi Kivity <avi@...hat.com>
Cc: Ingo Molnar <mingo@...e.hu>,
Antoine Martin <antoine@...afix.co.uk>,
Olivier Galibert <galibert@...ox.com>,
Anthony Liguori <anthony@...emonkey.ws>,
"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Sheng Yang <sheng@...ux.intel.com>,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
Marcelo Tosatti <mtosatti@...hat.com>,
oerg Roedel <joro@...tes.org>,
Jes Sorensen <Jes.Sorensen@...hat.com>,
Gleb Natapov <gleb@...hat.com>,
Zachary Amsden <zamsden@...hat.com>, ziteng.huang@...el.com,
Arnaldo Carvalho de Melo <acme@...hat.com>,
"Fr?d?ric Weisbecker" <fweisbec@...il.com>
Subject: Re: [RFC] Unify KVM kernel-space and user-space code into a single
project
On Mon, Mar 22, 2010 at 2:36 PM, Avi Kivity <avi@...hat.com> wrote:
>> Here it is, repeated for the Nth time:
>>
>> Allow a guest to (optionally) integrate its VFS namespace with the host
>> side
>> as well. An example scheme would be:
>>
>> /guests/Fedora-G1/
>>
>
> [...]
>
> You're missing something. This sub-thread is about someone launching a
> kernel with 'qemu -kernel', the kernel lives outside the guest disk image,
> they don't want a custom initrd because it's hard to make.
Well, you know, I am missing your point here about initrd. Surely the
guest kernels need to use sys_mount() at some point at which time they
could just tell the host kernel where they can find the mount points?
But maybe we're not talking about that kind of scenario here?
Pekka
--
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