[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BA68063.2050800@redhat.com>
Date: Sun, 21 Mar 2010 22:24:03 +0200
From: Avi Kivity <avi@...hat.com>
To: Antoine Martin <antoine@...afix.co.uk>
CC: Olivier Galibert <galibert@...ox.com>, Ingo Molnar <mingo@...e.hu>,
Anthony Liguori <anthony@...emonkey.ws>,
Pekka Enberg <penberg@...helsinki.fi>,
"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 03/21/2010 10:18 PM, Antoine Martin wrote:
>> That includes the guest kernel. If you can deploy a new kernel in
>> the guest, presumably you can deploy a userspace package.
>
> That's not always true.
> The host admin can control the guest kernel via "kvm -kernel" easily
> enough, but he may or may not have access to the disk that is used in
> the guest. (think encrypted disks, service agreements, etc)
There is a matching -initrd argument that you can use to launch a
daemon. I believe that -kernel use will be rare, though. It's a lot
easier to keep everything in one filesystem.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
--
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