pve-faq.adoc

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