]>
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 CPUs (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 Proxmox Containers 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 | |
93 | easily create and manage system containers. LXC, as well as the former | |
94 | OpenVZ, aims at *system virtualization*, i.e. allows you to run a | |
95 | complete OS inside a container, where you log in as ssh, add users, | |
96 | run apache, etc... | |
97 | + | |
98 | LXD is building on top of LXC to provide a new, better user | |
99 | experience. Under the hood, LXD uses LXC through `liblxc` and its Go | |
100 | binding to create and manage the containers. It's basically an | |
101 | alternative to LXC's tools and distribution template system with the | |
102 | added features that come from being controllable over the network. | |
103 | + | |
104 | Proxmox Containers also aims at *system virtualization*, and thus uses | |
105 | LXC as the basis of its own container offer. The Proxmox Container | |
106 | Toolkit is called `pct`, and is tightly coupled with {pve}. That means | |
107 | that it is aware of the cluster setup, and it can use the same network | |
108 | and storage resources as fully virtualized VMs. You can even use the | |
109 | {pve} firewall, create and restore backups, or manage containers using | |
110 | the HA framework. Everything can be controlled over the network using | |
111 | the {pve} API. | |
112 | + | |
113 | Docker aims at running a *single* application running in a contained | |
114 | environment. Hence you're managing a docker instance from the host with the | |
115 | docker toolkit. It is not recommended to run docker directly on your | |
116 | {pve} host. | |
117 | + | |
118 | NOTE: You can however perfectly install and use docker inside a Proxmox Qemu | |
119 | VM, and thus getting the benefit of software containerization with the very | |
120 | strong isolation that VMs provide. |