proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-06-15 03:40:54 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

system requirements: minor language fixup

Browse Source 
Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
This commit is contained in:
Dylan Whyte 2020-10-07 10:48:13 +02:00 committed by Thomas Lamprecht
parent 52f30c6551
commit 3f7218b5bf
1 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
pve-system-requirements.adoc
View File

@ -4,8 +4,8 @@ ifdef::wiki[]
:pve-toplevel: :pve-toplevel:
endif::wiki[] endif::wiki[]
We recommend to use high quality server hardware when running {pve} in 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 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. a cluster with highly available (HA) virtual machines and containers.
{pve} can use local storage (DAS), SAN, NAS, and distributed storage like Ceph {pve} can use local storage (DAS), SAN, NAS, and distributed storage like Ceph
@ -22,11 +22,11 @@ used in production.
* Intel VT/AMD-V capable CPU/Mainboard for KVM full virtualization support * 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 needed for guests
* Hard drive * Hard drive
* One NIC * One network card (NIC)
[[install_recommended_requirements]] [[install_recommended_requirements]]
@ -35,8 +35,8 @@ 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 the OS and {pve} services. Plus designated memory for * 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 guests. For Ceph and ZFS, additional memory is required; approximately 1GB of
memory for every TB of used storage. memory for every TB of used storage.
* Fast and redundant storage, best results are achieved with SSDs. * Fast and redundant storage, best results are achieved with SSDs.
@ -45,12 +45,12 @@ Recommended System Requirements
or non-RAID with ZFS (optional SSD for ZIL). or non-RAID with ZFS (optional SSD for ZIL).
* VM storage: * VM storage:
** For local storage use either a hardware RAID with battery backed write cache ** 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 (BBU) or non-RAID for ZFS and Ceph. Neither ZFS nor Ceph are compatible with a
hardware RAID controller. hardware RAID controller.
** Shared and distributed storage is possible. ** Shared and distributed storage is possible.
* Redundant (Multi-)Gbit NICs with additional NICs depending on the preferred * Redundant (Multi-)Gbit NICs, with additional NICs depending on the preferred
storage technology and cluster setup. storage technology and cluster setup.
* For PCI(e) passthrough the CPU needs to support the VT-d/AMD-d flag. * For PCI(e) passthrough the CPU needs to support the VT-d/AMD-d flag.
@ -68,13 +68,13 @@ recommended, especially regarding the I/O performance of your system.
Supported Web Browsers for Accessing the Web Interface Supported Web Browsers for Accessing the Web Interface
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To access the web-based user interface one of the following browsers is To access the web-based user interface, we recommend using one of the following
recommended: browsers:
* Firefox, a release of the current year, or the latest Extended Support Release * Firefox, a release from the current year, or the latest Extended Support Release
* Chrome, a release of the current year * Chrome, a release from the current year
* Microsoft's currently supported version of Edge * Microsoft's currently supported version of Edge
* Safari, a release of the current year * Safari, a release from the current year
When used on a mobile device, {pve} will show a lightweight touch-based When accessed from a mobile device, {pve} will show a lightweight, touch-based
interface. interface.