]>
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. |