From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 1/4] qm: hard disk controllers: reword and update section
Date: Fri, 17 Feb 2023 17:08:33 +0100 [thread overview]
Message-ID: <20230217160836.142368-2-f.ebner@proxmox.com> (raw)
In-Reply-To: <20230217160836.142368-1-f.ebner@proxmox.com>
Most importantly, mention that VirtIO SCSI single in combination with
IO thread is the new recommendation and default. The controller type
used for the QEMU commandline is still the same (but one for each
disk), so information about when OSes started supporting it should be
accurate.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
qm.adoc | 17 ++++++++---------
1 file changed, 8 insertions(+), 9 deletions(-)
diff --git a/qm.adoc b/qm.adoc
index 8a49283..629e913 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -169,16 +169,15 @@ connected. You can connect up to 6 devices on this controller.
hardware, and can connect up to 14 storage devices. {pve} emulates by default a
LSI 53C895A controller.
+
-A SCSI controller of type _VirtIO SCSI_ is the recommended setting if you aim for
-performance and is automatically selected for newly created Linux VMs since
-{pve} 4.3. Linux distributions have support for this controller since 2012, and
-FreeBSD since 2014. For Windows OSes, you need to provide an extra iso
-containing the drivers during the installation.
+A SCSI controller of type _VirtIO SCSI single_ and enabling the
+xref:qm_hard_disk_iothread[IO Thread] setting for the attached disks is
+recommended if you aim for performance. This is the default for newly created
+Linux VMs since {pve} 7.3. Each disk will have its own _VirtIO SCSI_ controller,
+and QEMU will handle the disks IO in a dedicated thread. Linux distributions
+have support for this controller since 2012, and FreeBSD since 2014. For Windows
+OSes, you need to provide an extra ISO containing the drivers during the
+installation.
// https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows#During_windows_installation.
-If you aim at maximum performance, you can select a SCSI controller of type
-_VirtIO SCSI single_ which will allow you to select the *IO Thread* option.
-When selecting _VirtIO SCSI single_ QEMU will create a new controller for
-each disk, instead of adding all disks to the same controller.
* The *VirtIO Block* controller, often just called VirtIO or virtio-blk,
is an older type of paravirtualized controller. It has been superseded by the
--
2.30.2
next prev parent reply other threads:[~2023-02-17 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 16:08 [pve-devel] [PATCH docs 0/4] qm: more visible recommendations for virtio devices/controllers Fiona Ebner
2023-02-17 16:08 ` Fiona Ebner [this message]
2023-02-17 16:08 ` [pve-devel] [PATCH docs 2/4] qm: hard disk controllers: recommend VirtIO controllers Fiona Ebner
2023-02-17 16:08 ` [pve-devel] [PATCH docs 3/4] qm: emulated devices: mention that virtio devices are better maintained Fiona Ebner
2023-02-17 16:08 ` [pve-devel] [PATCH docs 4/4] qm: emulated devices: make recommendation for virtio devices more visible Fiona Ebner
2023-02-24 15:41 ` [pve-devel] applied-series: [PATCH docs 0/4] qm: more visible recommendations for virtio devices/controllers Thomas Lamprecht
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=20230217160836.142368-2-f.ebner@proxmox.com \
--to=f.ebner@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