5
0
mirror of git://git.proxmox.com/git/pve-docs.git synced 2025-01-03 01:17:49 +03:00
pve-docs/pve-system-requirements.adoc
Thomas Lamprecht d0cf82da04 system requirements: use correct and modern acronym for Intel 64-bit
Intel EMT64 is not a thing, the correct variant would be Extended
Memory 64 Technology, which is shortened to EM64T [0].

But the `Intel EM64T` term was replace a long time ago by `Intel 64`
[1], so just go with that.

[0]: https://www.intel.com/content/www/us/en/support/articles/000005898/processors.html
[1]: "[...] in March 2004 unveiled the "official" name EM64T (Extended
      Memory 64 Technology). In late 2006 Intel began instead using
      the name Intel 64 for its implementation [...]"
     -- https://en.wikipedia.org/wiki/X86-64#Intel_64

Reported-by: Alexander P. Inzinger-Zrock
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2024-09-30 11:41:30 +02:00

83 lines
2.7 KiB
Plaintext

System Requirements
-------------------
ifdef::wiki[]
:pve-toplevel:
endif::wiki[]
We recommend using high quality server hardware, when running {pve} in
production. To further decrease the impact of a failed host, you can run {pve} in
a cluster with highly available (HA) virtual machines and containers.
{pve} can use local storage (DAS), SAN, NAS, and distributed storage like Ceph
RBD. For details see xref:chapter_storage[chapter storage].
[[install_minimal_requirements]]
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)
[[install_recommended_requirements]]
Recommended System Requirements
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* Intel 64 or AMD64 with Intel VT/AMD-V CPU flag.
* Memory: Minimum 2 GB for the OS and {pve} 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 {pve}
system, run the included `pveperf` tool.
NOTE: 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, {pve} will show a lightweight, touch-based
interface.