System Requirements: Difference between revisions
No edit summary |
No edit summary |
||
Line 4: | Line 4: | ||
[[Category:Reference Documentation]] | [[Category:Reference Documentation]] | ||
<pvehide> | <pvehide> | ||
We recommend to use high quality server hardware when running Proxmox VE in | |||
production. To further decrease the impact of a failed host you can run Proxmox VE in | |||
a cluster with highly available (HA) virtual machines and containers. | |||
Proxmox VE can use local storage (DAS), SAN, NAS, and distributed storage like Ceph | |||
RBD. For details see chapter storage. | |||
Proxmox VE can use local storage (DAS), SAN, NAS and | |||
storage | |||
Minimum Requirements, for Evaluation | Minimum Requirements, for Evaluation | ||
These minimum requirements are for evaluation purposes only and should not be | |||
used in production. | |||
CPU: 64bit (Intel EMT64 or AMD64) | CPU: 64bit (Intel EMT64 or AMD64) | ||
Intel VT/AMD-V capable CPU/Mainboard for KVM | Intel VT/AMD-V capable CPU/Mainboard for KVM full virtualization support | ||
RAM: 1 GB RAM, plus additional RAM used for guests | RAM: 1 GB RAM, plus additional RAM used for guests | ||
Hard drive | Hard drive | ||
Line 19: | Line 19: | ||
Recommended System Requirements | Recommended System Requirements | ||
Intel EMT64 or AMD64 with Intel VT/AMD-V CPU flag. | Intel EMT64 or AMD64 with Intel VT/AMD-V CPU flag. | ||
Memory, minimum 2 GB for OS and Proxmox VE services. Plus designated memory | Memory, minimum 2 GB for the OS and Proxmox VE services. Plus designated memory for | ||
guests. For Ceph and ZFS additional memory is required; approximately 1GB of | |||
memory for every TB used storage. | memory for every TB of used storage. | ||
Fast and redundant storage, best results with | Fast and redundant storage, best results are achieved with SSDs. | ||
OS storage: | OS storage: Use a hardware RAID with battery protected write cache (“BBU”) | ||
non-RAID with ZFS | or non-RAID with ZFS (optional SSD for ZIL). | ||
VM storage: For local storage use a hardware RAID with battery backed | VM storage: | ||
For local storage use either a hardware RAID with battery backed write cache | |||
(BBU) or non-RAID for ZFS and Ceph. Neither ZFS nor Ceph are compatible with a | |||
hardware RAID controller. | |||
Redundant Gbit NICs | Shared and distributed storage is possible. | ||
technology and cluster setup | Redundant (Multi-)Gbit NICs with additional NICs depending on the preferred | ||
For PCI passthrough | storage technology and cluster setup. | ||
For PCI(e) passthrough the CPU needs to support the VT-d/AMD-d flag. | |||
Simple Performance Overview | Simple Performance Overview | ||
To get an overview of the CPU and hard disk performance on an installed Proxmox VE | |||
system, run the included pveperf tool. | |||
This is just a very quick and general benchmark. More detailed tests are | |||
recommended, especially regarding the I/O performance of your system. | |||
Supported | Supported Web Browsers for Accessing the Web Interface | ||
To | To access the web-based user interface one of the following browsers is | ||
Firefox, a release | recommended: | ||
Support Release | Firefox, a release of the current year, or the latest Extended Support Release | ||
Chrome, a release | Chrome, a release of the current year | ||
Microsoft’s currently supported version of Edge | |||
Safari, a release | Safari, a release of the current year | ||
When used on a mobile device, Proxmox VE will show a lightweight touch-based | |||
interface. | |||
</pvehide> | </pvehide> | ||
<!--PVE_IMPORT_END_MARKER--> | <!--PVE_IMPORT_END_MARKER--> |
Revision as of 17:25, 13 February 2020
We recommend using high quality server hardware, when running Proxmox VE in production. To further decrease the impact of a failed host, you can run Proxmox VE in a cluster with highly available (HA) virtual machines and containers.
Proxmox VE can use local storage (DAS), SAN, NAS, and distributed storage like Ceph RBD. For details see chapter storage.
Minimum Requirements, for Evaluation
These minimum requirements are for evaluation purposes only and should not be used in production.
-
CPU: 64bit (Intel 64 or AMD64)
-
Intel VT/AMD-V capable CPU/motherboard for KVM full virtualization support
-
RAM: 1 GB RAM, plus additional RAM needed for guests
-
Hard drive
-
One network card (NIC)
Recommended System Requirements
-
Intel 64 or AMD64 with Intel VT/AMD-V CPU flag.
-
Memory: Minimum 2 GB for the OS and Proxmox VE services, plus designated memory for guests. For Ceph and ZFS, additional memory is required; approximately 1GB of memory for every TB of used storage.
-
Fast and redundant storage, best results are achieved with SSDs.
-
OS storage: Use a hardware RAID with battery protected write cache (“BBU”) or non-RAID with ZFS (optional SSD for ZIL).
-
VM storage:
-
For local storage, use either a hardware RAID with battery backed write cache (BBU) or non-RAID for ZFS and Ceph. Neither ZFS nor Ceph are compatible with a hardware RAID controller.
-
Shared and distributed storage is possible.
-
SSDs with Power-Loss-Protection (PLP) are recommended for good performance. Using consumer SSDs is discouraged.
-
-
Redundant (Multi-)Gbit NICs, with additional NICs depending on the preferred storage technology and cluster setup.
-
For PCI(e) passthrough the CPU needs to support the VT-d/AMD-d flag.
Simple Performance Overview
To get an overview of the CPU and hard disk performance on an installed Proxmox VE system, run the included pveperf tool.
This is just a very quick and general benchmark. More detailed tests are recommended, especially regarding the I/O performance of your system. |
Supported Web Browsers for Accessing the Web Interface
To access the web-based user interface, we recommend using one of the following browsers:
-
Firefox, a release from the current year, or the latest Extended Support Release
-
Chrome, a release from the current year
-
Microsoft’s currently supported version of Edge
-
Safari, a release from the current year
When accessed from a mobile device, Proxmox VE will show a lightweight, touch-based interface.