[pve-docs.git] / pve-faq.adoc

Frequently Asked Questions
==========================
include::attributes.txt[]

NOTE: New FAQs are appended to the bottom of this section.

/////////////////////////////////////////////////////////////////
ADD NEW FAQS TO THE BOTTOM OF THIS SECTION TO MAINTAIN NUMBERING
/////////////////////////////////////////////////////////////////

[qanda]

What distribution is {pve} based on?::

{pve} is based on http://www.debian.org[Debian GNU/Linux]

What license does the {pve} project use?::

{pve} code is licensed under the GNU Affero General Public License,
version 3.

Will {pve} run on a 32bit processor?::

{pve} works only on 64-bit CPU´s (AMD or Intel). There is no plan
for 32-bit for the platform.
+
NOTE: VMs and Containers can be both 32-bit and/or 64-bit.

Does my CPU support virtualization?::

To check if your CPU is virtualization compatible, check for the "vmx"
or "svm" tag in this command output:
+
----
egrep '(vmx|svm)' /proc/cpuinfo
----

Supported Intel CPUs::

64-bit processors with
http://en.wikipedia.org/wiki/Virtualization_Technology#Intel_virtualization_.28VT-x.29[Intel
Virtualization Technology (Intel VT-x)] support. (http://ark.intel.com/search/advanced/?s=t&VTX=true&InstructionSet=64-bit[List of processors with Intel VT and 64-bit])

Supported AMD CPUs::

64-bit processors with
http://en.wikipedia.org/wiki/Virtualization_Technology#AMD_virtualization_.28AMD-V.29[AMD
Virtualization Technology (AMD-V)] support.

What is a container, CT, VE, Virtual Private Server, VPS?::

Operating-system-level virtualization is a server-virtualization
method where the kernel of an operating system allows for multiple
isolated user-space instances, instead of just one. We call such
instances containers. As containers use the host's kernel they are
limited to Linux guests.

What is a QEMU/KVM guest (or VM)?::

A QEMU/KVM guest (or VM) is a guest system running virtualized under
{pve} using QEMU and the Linux KVM kernel module.

What is QEMU?::

QEMU is a generic and open source machine emulator and
virtualizer. QEMU uses the Linux KVM kernel module to achieve near
native performance by executing the guest code directly on the host
CPU.
It is not limited to Linux guests but allows arbitrary operating systems
to run.

How long will my {pve} version be supported?::

{pve} versions are supported at least as long as the corresponding
Debian Version is
https://wiki.debian.org/DebianOldStable[oldstable]. {pve} uses a
rolling release model and using the latest stable version is always
recommended.
+
[width="100%",cols="5*d",options="header"]
|===========================================================
| {pve} Version | Debian Version    | First Release | Debian EOL | Proxmox EOL
| {pve} 4.x     | Debian 8 (Jessie) | 2015-10       | 2018-05    | tba
| {pve} 3.x     | Debian 7 (Wheezy) | 2013-05       | 2016-04    | 2017-02
| {pve} 2.x     | Debian 6 (Squeeze)| 2012-04       | 2014-05    | 2014-05
| {pve} 1.x     | Debian 5 (Lenny)  | 2008-10       | 2012-03    | 2013-01
|===========================================================

LXC vs LXD vs Docker::

LXC is a userspace interface for the Linux kernel containment
features. Through a powerful API and simple tools, it lets Linux users easily
create and manage system containers.
+
LXD is building on top of LXC to provide a new, better user experience. Under
the hood, LXD uses LXC through liblxc and its Go binding to create and manage
the containers. It's basically an alternative to LXC's tools and distribution
template system with the added features that come from being controllable over
the network.
+
LXC, as well as the former OpenVZ, aims at *system virtualization*, ie
allows you to run a complete OS inside a container, where you log in as ssh,
add users, run apache, etc...
+
Docker aims at running a *single* application running in a contained
environment. Hence you're managing a docker instance from the host with the
docker toolkit.
+
NOTE: Proxmox VE aims at system virtualization, and thus uses LXC as the basis
of its own container offer. You can however perfectly install and use docker
inside a VM, and thus getting the benefit of software containerization
with the very strong isolation that VMs provide.
Commit	Line	Data
	1	Frequently Asked Questions
	2	==========================
	3	include::attributes.txt[]
	4
	5	NOTE: New FAQs are appended to the bottom of this section.
	6
	7	/////////////////////////////////////////////////////////////////
	8	ADD NEW FAQS TO THE BOTTOM OF THIS SECTION TO MAINTAIN NUMBERING
	9	/////////////////////////////////////////////////////////////////
	10
	11	[qanda]
	12
	13	What distribution is {pve} based on?::
	14
	15	{pve} is based on http://www.debian.org[Debian GNU/Linux]
	16
	17	What license does the {pve} project use?::
	18
	19	{pve} code is licensed under the GNU Affero General Public License,
	20	version 3.
	21
	22	Will {pve} run on a 32bit processor?::
	23
	24	{pve} works only on 64-bit CPU´s (AMD or Intel). There is no plan
	25	for 32-bit for the platform.
	26	+
	27	NOTE: VMs and Containers can be both 32-bit and/or 64-bit.
	28
	29	Does my CPU support virtualization?::
	30
	31	To check if your CPU is virtualization compatible, check for the "vmx"
	32	or "svm" tag in this command output:
	33	+
	34	----
	35	egrep '(vmx\|svm)' /proc/cpuinfo
	36	----
	37
	38	Supported Intel CPUs::
	39
	40	64-bit processors with
	41	http://en.wikipedia.org/wiki/Virtualization_Technology#Intel_virtualization_.28VT-x.29[Intel
	42	Virtualization Technology (Intel VT-x)] support. (http://ark.intel.com/search/advanced/?s=t&VTX=true&InstructionSet=64-bit[List of processors with Intel VT and 64-bit])
	43
	44	Supported AMD CPUs::
	45
	46	64-bit processors with
	47	http://en.wikipedia.org/wiki/Virtualization_Technology#AMD_virtualization_.28AMD-V.29[AMD
	48	Virtualization Technology (AMD-V)] support.
	49
	50	What is a container, CT, VE, Virtual Private Server, VPS?::
	51
	52	Operating-system-level virtualization is a server-virtualization
	53	method where the kernel of an operating system allows for multiple
	54	isolated user-space instances, instead of just one. We call such
	55	instances containers. As containers use the host's kernel they are
	56	limited to Linux guests.
	57
	58	What is a QEMU/KVM guest (or VM)?::
	59
	60	A QEMU/KVM guest (or VM) is a guest system running virtualized under
	61	{pve} using QEMU and the Linux KVM kernel module.
	62
	63	What is QEMU?::
	64
	65	QEMU is a generic and open source machine emulator and
	66	virtualizer. QEMU uses the Linux KVM kernel module to achieve near
	67	native performance by executing the guest code directly on the host
	68	CPU.
	69	It is not limited to Linux guests but allows arbitrary operating systems
	70	to run.
	71
	72	How long will my {pve} version be supported?::
	73
	74	{pve} versions are supported at least as long as the corresponding
	75	Debian Version is
	76	https://wiki.debian.org/DebianOldStable[oldstable]. {pve} uses a
	77	rolling release model and using the latest stable version is always
	78	recommended.
	79	+
	80	[width="100%",cols="5*d",options="header"]
	81	\|===========================================================
	82	\| {pve} Version \| Debian Version \| First Release \| Debian EOL \| Proxmox EOL
	83	\| {pve} 4.x \| Debian 8 (Jessie) \| 2015-10 \| 2018-05 \| tba
	84	\| {pve} 3.x \| Debian 7 (Wheezy) \| 2013-05 \| 2016-04 \| 2017-02
	85	\| {pve} 2.x \| Debian 6 (Squeeze)\| 2012-04 \| 2014-05 \| 2014-05
	86	\| {pve} 1.x \| Debian 5 (Lenny) \| 2008-10 \| 2012-03 \| 2013-01
	87	\|===========================================================
	88
	89	LXC vs LXD vs Docker::
	90
	91	LXC is a userspace interface for the Linux kernel containment
	92	features. Through a powerful API and simple tools, it lets Linux users easily
	93	create and manage system containers.
	94	+
	95	LXD is building on top of LXC to provide a new, better user experience. Under
	96	the hood, LXD uses LXC through liblxc and its Go binding to create and manage
	97	the containers. It's basically an alternative to LXC's tools and distribution
	98	template system with the added features that come from being controllable over
	99	the network.
	100	+
	101	LXC, as well as the former OpenVZ, aims at system virtualization, ie
	102	allows you to run a complete OS inside a container, where you log in as ssh,
	103	add users, run apache, etc...
	104	+
	105	Docker aims at running a single application running in a contained
	106	environment. Hence you're managing a docker instance from the host with the
	107	docker toolkit.
	108	+
	109	NOTE: Proxmox VE aims at system virtualization, and thus uses LXC as the basis
	110	of its own container offer. You can however perfectly install and use docker
	111	inside a VM, and thus getting the benefit of software containerization
	112	with the very strong isolation that VMs provide.