From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Alexey Eremenko <al4321@gmail.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 12:31:20 -0700 [thread overview]
Message-ID: <1190057480.5982.157.camel@bodhitayantram.eng.vmware.com> (raw)
In-Reply-To: <46ED440E.3020209@goop.org>
On Sun, 2007-09-16 at 07:56 -0700, Jeremy Fitzhardinge wrote:
> Rusty Russell wrote:
> > Well, containerization deserves its own menu, but the question is does i
> > it belong under this menu?
>
> No, I don't think so. While there are some broad similarities in
> effect, the technology is completely different, as are the capabilities
> and tradeoffs. They're pretty much orthogonal.
It seems to me containerization is much more similar a feature to SYSV
IPC, process accounting / auditing, and should be an option under
General setup, possibly with its own submenu. Nearly all the features
under general setup provide optional extensions to kernel services
available from userspace, and so it seems containerization falls
naturally into that category.
Virtualization is completely different, and probably needs separate
server (kvm, lguest) and client (kvm, lguest, xen, vmware) sections in
it's menu.
Zach
next prev parent reply other threads:[~2007-09-17 19:31 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 [this message]
2007-09-17 23:30 ` Charles N Wyble
2007-09-18 0:18 ` Jeremy Fitzhardinge
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=1190057480.5982.157.camel@bodhitayantram.eng.vmware.com \
--to=zach@vmware.com \
--cc=al4321@gmail.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.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
all inboxes | Powered by JetHome®