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