From: Stefan Sterz <s.sterz@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 2/2] qm: add documentation on configuring multiqueue for windows guests
Date: Thu, 21 Mar 2024 16:50:44 +0100 [thread overview]
Message-ID: <20240321155044.190520-2-s.sterz@proxmox.com> (raw)
In-Reply-To: <20240321155044.190520-1-s.sterz@proxmox.com>
Signed-off-by: Stefan Sterz <s.sterz@proxmox.com>
---
qm.adoc | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/qm.adoc b/qm.adoc
index 8630419..711fa3f 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -780,6 +780,16 @@ ethtool command:
where X is the number of the number of vCPUs of the VM.
+To configure a Windows guest for Multiqueue install the
+https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso[
+Redhat VirtIO Ethernet Adapter drivers], then adapt the NIC's configuration as
+follows. Open the device manager, right click the NIC under "Network adapters",
+and select "Properties". Then open the "Advanced" tab and select "Receive Side
+Scaling" from the list on the left. Make sure it is set to "Enabled". Next,
+navigate to "Maximum number of RSS Queues" in the list and set it to the number
+of vCPUs of your VM. Once you verified that the settings are correct, click "OK"
+to confirm them.
+
You should note that setting the Multiqueue parameter to a value greater
than one will increase the CPU load on the host and guest systems as the
traffic increases. We recommend to set this option only when the VM has to
--
2.39.2
next prev parent reply other threads:[~2024-03-21 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 15:50 [pve-devel] [PATCH docs 1/2] qm: multiqueue specify that it needs to be vCPUs not cores Stefan Sterz
2024-03-21 15:50 ` Stefan Sterz [this message]
2024-03-21 16:48 ` [pve-devel] applied: " Aaron Lauterer
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=20240321155044.190520-2-s.sterz@proxmox.com \
--to=s.sterz@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