From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 7B6871FF0E1 for ; Thu, 27 Aug 2026 09:40:01 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 572F8214C4; Thu, 27 Aug 2026 09:39:56 +0200 (CEST) From: Aaron Lauterer To: pve-devel@lists.proxmox.com, Maximiliano Sandoval In-Reply-To: <20260819083214.115093-1-m.sandoval@proxmox.com> References: <20260819083214.115093-1-m.sandoval@proxmox.com> Subject: Re: [PATCH docs 1/1] qm: clarify when the iothreads options takes into effect Message-Id: <178781639220.4012408.2552824349594396034.b4-ty@proxmox.com> Date: Thu, 27 Aug 2026 09:39:52 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.14.2 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1787816383663 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.842 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: EZU37Z3B5AGQRZMDEZVW24C6GWAERG6Y X-Message-ID-Hash: EZU37Z3B5AGQRZMDEZVW24C6GWAERG6Y X-MailFrom: a.lauterer@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Wed, 19 Aug 2026 10:32:11 +0200, Maximiliano Sandoval wrote: > The main point addressed is that the "VirtIO Block" bus controller type was > referred as "VirtIO". This can be a source of confusion since the are multiple > controllers for different components provided by VirtIO. > > VirtIO SCSI is listed before VirtIO Block as a soft-recommendation. > > We use the same terms as the web UI, modulo capitalization for "Bus/Device" and > "SCSI Controller". > > [...] Applied, thanks! [1/1] qm: clarify when the iothreads options takes into effect commit: d25fc274de5ce3aceebd829b52ee13b3739dc12b