shinji at elite-systems.org
Wed Oct 19 15:51:16 UTC 2011
On Wed, Oct 19, 2011 at 3:01 AM, Papp Tamas <tompos at martos.bme.hu> wrote:
> On 10/19/2011 12:36 AM, Derek Simkowiak wrote:
>> But actually I think, lxc-virt.org sounds better.
> I disagree with lxc-virt.org.
> The difference between "container" and "virtual machine" is already
> confusing enough. There is no virtualization layer in LXC, so I don't
> "virt" should be part of the official name.
> What is the definition of the virtualization layer?
For me I have 3 terms for guest environments that have defined meanings
behind them (at least mentally)
Virtual machine = An isolated environment that provides emulated hardware to
a guest OS. This guest OS is largely unaware of the host but may gain
performance improvements from host features like Intel-VTx or AMD-V.
Virtualization Layer = An application that allows code written for one
platform to run on another or provides transparent translation of one
platform's codes or functions to another platforms equivalent. An example
is like Wine or Qemu when it is translating binary instructions. i.e -
Running ARM compiled code on x86 platform.
Container = An isolated environment that provides direct hardware access and
emulates little to no components. Access to the hardware may be restricted
by the container implementation for security or isolation purposes. Some
container implementations require a custom kernel and guest containers may
run their own kernel depending on how it is implemented.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lxc-users