From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 23B2ABAB1 for ; Mon, 3 Jul 2023 14:04:53 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0C8CB1CEF2 for ; Mon, 3 Jul 2023 14:04:53 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Mon, 3 Jul 2023 14:04:52 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id B991F43857 for ; Mon, 3 Jul 2023 14:04:51 +0200 (CEST) From: Noel Ullreich To: pve-devel@lists.proxmox.com Date: Mon, 3 Jul 2023 14:04:32 +0200 Message-Id: <20230703120436.74646-3-n.ullreich@proxmox.com> X-Mailer: git-send-email 2.39.2 In-Reply-To: <20230703120436.74646-1-n.ullreich@proxmox.com> References: <20230703120436.74646-1-n.ullreich@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.061 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pve-devel] [PATCH pve-docs v2 2/4] Consistency: change mainboard to motherboard X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2023 12:04:53 -0000 To be consistent, replaced all instances of mainboard/main board with motherboard. Signed-off-by: Noel Ullreich --- ha-manager.adoc | 2 +- pve-system-requirements.adoc | 2 +- qm-pci-passthrough.adoc | 2 +- qm.adoc | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/ha-manager.adoc b/ha-manager.adoc index 3724ab3..8773552 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -63,7 +63,7 @@ usually at higher price. * Eliminate single point of failure (redundant components) ** use an uninterruptible power supply (UPS) -** use redundant power supplies on the main boards +** use redundant power supplies in your servers ** use ECC-RAM ** use redundant network hardware ** use RAID for local storage diff --git a/pve-system-requirements.adoc b/pve-system-requirements.adoc index bb474ac..bc3689d 100644 --- a/pve-system-requirements.adoc +++ b/pve-system-requirements.adoc @@ -20,7 +20,7 @@ used in production. * CPU: 64bit (Intel EMT64 or AMD64) -* Intel VT/AMD-V capable CPU/Mainboard for KVM full virtualization support +* Intel VT/AMD-V capable CPU/motherboard for KVM full virtualization support * RAM: 1 GB RAM, plus additional RAM needed for guests diff --git a/qm-pci-passthrough.adoc b/qm-pci-passthrough.adoc index b90a0b9..4daa5b3 100644 --- a/qm-pci-passthrough.adoc +++ b/qm-pci-passthrough.adoc @@ -23,7 +23,7 @@ some requirements to check and preparations to be done to make it work. Hardware ^^^^^^^^ Your hardware needs to support `IOMMU` (*I*/*O* **M**emory **M**anagement -**U**nit) interrupt remapping, this includes the CPU and the mainboard. +**U**nit) interrupt remapping, this includes the CPU and the motherboard. Generally, Intel systems with VT-d, and AMD systems with AMD-Vi support this. But it is not guaranteed that everything will work out of the box, due diff --git a/qm.adoc b/qm.adoc index ca1dfa2..83f6c53 100644 --- a/qm.adoc +++ b/qm.adoc @@ -60,7 +60,7 @@ and PCI devices. Emulated devices and paravirtualized devices -------------------------------------------- -The PC hardware emulated by QEMU includes a mainboard, network controllers, +The PC hardware emulated by QEMU includes a motherboard, network controllers, SCSI, IDE and SATA controllers, serial ports (the complete list can be seen in the `kvm(1)` man page) all of them emulated in software. All these devices are the exact software equivalent of existing hardware devices, and if the OS -- 2.39.2