From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Charles N Wyble <charles@thewybles.com>
Cc: Zachary Amsden <zach@vmware.com>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 2/3] Consolidate host virtualization support under Virtualization menu
Date: Mon, 17 Sep 2007 17:18:26 -0700 [thread overview]
Message-ID: <46EF1952.3010604@goop.org> (raw)
In-Reply-To: <46EF0E0A.2000804@thewybles.com>
Charles N Wyble wrote:
>
>
> Zachary Amsden wrote:
> <snip>>
> > Virtualization is completely different, and probably needs separate
> > server (kvm, lguest) and client (kvm, lguest, xen, vmware) sections in
> > it's menu.
>
>
> So what is the differentiation between client and server above? Just
> curious what makes kvm and lguest server and client.
"Host" and "guest" are better terms, I think. Kvm is all host, since
guests need no modification. lguest turns the kernel into both host and
guest. Xen Linux kernels are all guest, since the Xen hypervisor is the
host.
J
next prev parent reply other threads:[~2007-09-18 0:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 5:17 [PATCH 1/3] Normalize config options for guest support Rusty Russell
2007-09-14 5:18 ` [PATCH 2/3] Consolidate host virtualization support under Virtualization menu Rusty Russell
2007-09-14 5:21 ` [PATCH 3/3] Time to make CONFIG_PARAVIRT non-experimental Rusty Russell
2007-09-18 10:57 ` Andi Kleen
2007-09-18 20:04 ` Charles N Wyble
2007-09-18 20:20 ` Andi Kleen
2007-09-18 20:27 ` Charles N Wyble
2007-09-18 20:41 ` Andi Kleen
2007-09-20 15:45 ` Satyam Sharma
2007-09-20 16:09 ` Charles N Wyble
2007-09-20 16:47 ` Satyam Sharma
2007-09-18 21:34 ` Rusty Russell
2007-09-18 21:52 ` Andi Kleen
2007-09-19 1:53 ` Rusty Russell
2007-09-19 3:59 ` Jeremy Fitzhardinge
2007-09-19 10:43 ` Ian Campbell
2007-09-14 16:19 ` [PATCH 2/3] Consolidate host virtualization support under Virtualization menu Randy Dunlap
2007-09-14 20:01 ` Jan Engelhardt
2007-09-15 3:05 ` Rusty Russell
2007-09-15 8:49 ` Alexey Eremenko
2007-09-16 7:43 ` Rusty Russell
2007-09-16 14:56 ` Jeremy Fitzhardinge
2007-09-17 19:31 ` Zachary Amsden
2007-09-17 23:30 ` Charles N Wyble
2007-09-18 0:18 ` Jeremy Fitzhardinge [this message]
2007-09-18 20:11 ` Charles N Wyble
2007-09-19 9:38 ` Alexey Eremenko
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=46EF1952.3010604@goop.org \
--to=jeremy@goop.org \
--cc=charles@thewybles.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=zach@vmware.com \
/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).