]>
Commit | Line | Data |
---|---|---|
1 | System Requirements | |
2 | ------------------- | |
3 | ifdef::wiki[] | |
4 | :pve-toplevel: | |
5 | endif::wiki[] | |
6 | ||
7 | We recommend to use high quality server hardware when running {pve} in | |
8 | production. To further decrease the impact of a failed host you can run {pve} in | |
9 | a cluster with highly available (HA) virtual machines and containers. | |
10 | ||
11 | {pve} can use local storage (DAS), SAN, NAS, and distributed storage like Ceph | |
12 | RBD. For details see xref:chapter_storage[chapter storage]. | |
13 | ||
14 | [[install_minimal_requirements]] | |
15 | Minimum Requirements, for Evaluation | |
16 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
17 | ||
18 | These minimum requirements are for evaluation purposes only and should not be | |
19 | used in production. | |
20 | ||
21 | * CPU: 64bit (Intel EMT64 or AMD64) | |
22 | ||
23 | * Intel VT/AMD-V capable CPU/Mainboard for KVM full virtualization support | |
24 | ||
25 | * RAM: 1 GB RAM, plus additional RAM used for guests | |
26 | ||
27 | * Hard drive | |
28 | ||
29 | * One NIC | |
30 | ||
31 | ||
32 | [[install_recommended_requirements]] | |
33 | Recommended System Requirements | |
34 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
35 | ||
36 | * Intel EMT64 or AMD64 with Intel VT/AMD-V CPU flag. | |
37 | ||
38 | * Memory, minimum 2 GB for the OS and {pve} services. Plus designated memory for | |
39 | guests. For Ceph and ZFS additional memory is required; approximately 1GB of | |
40 | memory for every TB of used storage. | |
41 | ||
42 | * Fast and redundant storage, best results are achieved with SSDs. | |
43 | ||
44 | * OS storage: Use a hardware RAID with battery protected write cache (``BBU'') | |
45 | or non-RAID with ZFS (optional SSD for ZIL). | |
46 | ||
47 | * VM storage: | |
48 | ** For local storage use either a hardware RAID with battery backed write cache | |
49 | (BBU) or non-RAID for ZFS and Ceph. Neither ZFS nor Ceph are compatible with a | |
50 | hardware RAID controller. | |
51 | ** Shared and distributed storage is possible. | |
52 | ||
53 | * Redundant (Multi-)Gbit NICs with additional NICs depending on the preferred | |
54 | storage technology and cluster setup. | |
55 | ||
56 | * For PCI(e) passthrough the CPU needs to support the VT-d/AMD-d flag. | |
57 | ||
58 | ||
59 | Simple Performance Overview | |
60 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
61 | ||
62 | To get an overview of the CPU and hard disk performance on an installed {pve} | |
63 | system, run the included `pveperf` tool. | |
64 | ||
65 | NOTE: This is just a very quick and general benchmark. More detailed tests are | |
66 | recommended, especially regarding the I/O performance of your system. | |
67 | ||
68 | Supported Web Browsers for Accessing the Web Interface | |
69 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
70 | ||
71 | To access the web-based user interface one of the following browsers is | |
72 | recommended: | |
73 | ||
74 | * Firefox, a release of the current year, or the latest Extended Support Release | |
75 | * Chrome, a release of the current year | |
76 | * Microsoft's currently supported version of Edge | |
77 | * Safari, a release of the current year | |
78 | ||
79 | When used on a mobile device, {pve} will show a lightweight touch-based | |
80 | interface. |