From: Noel Ullreich <n.ullreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve_docs 1/1] raise min ram requirements to 2 GiB and specify min disk space
Date: Mon, 10 Jul 2023 15:49:50 +0200 [thread overview]
Message-ID: <20230710134951.79263-4-n.ullreich@proxmox.com> (raw)
In-Reply-To: <20230710134951.79263-1-n.ullreich@proxmox.com>
Raise the minimum ram required for a PVE instance.
Also specify the minimum and recommended disk space for a PVE instance in GiB.
Signed-off-by: Noel Ullreich <n.ullreich@proxmox.com>
---
pve-system-requirements.adoc | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/pve-system-requirements.adoc b/pve-system-requirements.adoc
index bb474ac..4e789a4 100644
--- a/pve-system-requirements.adoc
+++ b/pve-system-requirements.adoc
@@ -22,9 +22,9 @@ used in production.
* Intel VT/AMD-V capable CPU/Mainboard for KVM full virtualization support
-* RAM: 1 GB RAM, plus additional RAM needed for guests
+* RAM: 2 GiB RAM, plus additional RAM needed for guests
-* Hard drive
+* Disk Space: a hard drive with at least a 16 GiB capacity
* One network card (NIC)
@@ -35,14 +35,14 @@ Recommended System Requirements
* 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
- guests. For Ceph and ZFS, additional memory is required; approximately 1GB of
- memory for every TB of used storage.
+* Memory: Minimum 4 GiB for the OS and {pve} services, plus designated memory for
+ guests. For Ceph and ZFS, additional memory is required; approximately 1 GiB of
+ memory for every TiB 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).
+ or non-RAID with ZFS (optional SSD for ZIL) with at least a 32 GiB capacity.
* VM storage:
** For local storage, use either a hardware RAID with battery backed write cache
--
2.39.2
next prev parent reply other threads:[~2023-07-10 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 13:49 [pve-devel] [PATCH pve-installer; pve-docs; pmg-docs; proxmox-backup/docs 0/4] Update min RAM and min disk size for pve Noel Ullreich
2023-07-10 13:49 ` [pve-devel] [PATCH pve-installer 1/1] raise the minimum ram requirements to 2 GiB Noel Ullreich
2023-07-10 13:49 ` [pve-devel] [PATCH pmg_docs 1/1] Consistency of GB and GiB pmg Noel Ullreich
2024-01-22 17:58 ` [pve-devel] applied: " Stoiko Ivanov
2024-02-06 12:20 ` Thomas Lamprecht
2024-02-13 10:37 ` Stoiko Ivanov
2023-07-10 13:49 ` Noel Ullreich [this message]
2023-07-10 13:49 ` [pve-devel] [PATCH proxmox-backup/docs 1/1] Consistency of GB and GiB pbs Noel Ullreich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230710134951.79263-4-n.ullreich@proxmox.com \
--to=n.ullreich@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox