From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 2/4] qm: hard disk controllers: recommend VirtIO controllers
Date: Fri, 17 Feb 2023 17:08:34 +0100 [thread overview]
Message-ID: <20230217160836.142368-3-f.ebner@proxmox.com> (raw)
In-Reply-To: <20230217160836.142368-1-f.ebner@proxmox.com>
Quoting from [0]:
> In general, I advise against using AHCI in production as better
> performance (and dev support) can be achieved through virtio.
[0]: https://lists.nongnu.org/archive/html/qemu-devel/2023-02/msg03915.html
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
qm.adoc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/qm.adoc b/qm.adoc
index 629e913..6fc6f5e 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -155,6 +155,9 @@ Bus/Controller
^^^^^^^^^^^^^^
QEMU can emulate a number of storage controllers:
+TIP: It is highly recommended to use the *VirtIO SCSI* or *VirtIO Block*
+controller for performance reasons and because they are better maintained.
+
* the *IDE* controller, has a design which goes back to the 1984 PC/AT disk
controller. Even if this controller has been superseded by recent designs,
each and every OS you can think of has support for it, making it a great choice
--
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 ` [pve-devel] [PATCH docs 1/4] qm: hard disk controllers: reword and update section Fiona Ebner
2023-02-17 16:08 ` Fiona Ebner [this message]
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-3-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