From: "Alexey Eremenko" <al4321@gmail.com>
To: "Rusty Russell" <rusty@rustcorp.com.au>
Cc: "lkml - Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andi Kleen" <ak@muc.de>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH] Move KVM, paravirt, lguest, VMI and Xen under arch-level Virtualization option
Date: Fri, 20 Jul 2007 06:31:55 +0200 [thread overview]
Message-ID: <7fac565a0707192131t1af0982aq5a75fef2fe014762@mail.gmail.com> (raw)
In-Reply-To: <1184905342.10380.263.camel@localhost.localdomain>
On 7/20/07, Rusty Russell <rusty@rustcorp.com.au> wrote:
> Any objections?
>
> Rusty.
> ===
> Having KVM appear in the middle of "drivers" is kinda strange, and
> having it alone under a menu called "virtualization" doubly so.
>
Hi Rusty !
Very good move, that I have thought about too... I believe that since
we're creating a Virtualization Menu, we should add
OS-level-virtualization there as well (aka containerization) - the
following things: IPC virtualization (aka IPC namespaces), PID
virtualization, UTS virtualization. Those are 3 basic components that
went mainline into 2.6.19.
Article from OpenVZ:
http://www.linux.com/articles/59150?tid=136&tid=91
P.S. maybe rename those components from "IPC namespaces" to "IPC
virtualization" or even to "IPC containerization" it better reflect
it's internals?
--
-Alexey Eremenko "Technologov"
next prev parent reply other threads:[~2007-07-20 4:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 4:22 Rusty Russell
2007-07-20 4:31 ` Alexey Eremenko [this message]
2007-07-20 5:24 ` Avi Kivity
2007-07-20 6:02 ` Rusty Russell
2007-07-20 6:10 ` Zachary Amsden
2007-07-20 14:09 ` Jeff Dike
2007-07-21 15:49 ` Jan Engelhardt
2007-07-23 5:09 ` Rusty Russell
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=7fac565a0707192131t1af0982aq5a75fef2fe014762@mail.gmail.com \
--to=al4321@gmail.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.org \
--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®