From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 1EE581FF137 for ; Tue, 31 Mar 2026 20:39:49 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 920134E14; Tue, 31 Mar 2026 20:40:15 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Fiona Ebner Subject: applied: [PATCH-SERIES qemu-server 0/2] hotplug pending: only issue QMP commands related to USB hotplug if actually needed Date: Tue, 31 Mar 2026 20:40:02 +0200 Message-ID: <177496799451.4007206.11636342415787354322.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260330110954.82174-1-f.ebner@proxmox.com> References: <20260330110954.82174-1-f.ebner@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1774982353501 X-SPAM-LEVEL: Spam detection results: 0 AWL -1.506 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 1 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 1 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 1 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. 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: W3N6GYN53PZABLM4BBLYF56XPJPXI7NQ X-Message-ID-Hash: W3N6GYN53PZABLM4BBLYF56XPJPXI7NQ X-MailFrom: t.lamprecht@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 Mon, 30 Mar 2026 13:09:42 +0200, Fiona Ebner wrote: > There is a report in the enterprise support about Veeam failing to set > the 'lock' property in the VM configuration, because they are blocking > the QMP socket. The proper fix would be for them to not block the QMP > socket (at least not while interacting with our API), but there still > is an improvement to be made on the Proxmox VE side, which is to avoid > doing QMP commands related to USB hotplug if they are not actually > needed. > > [...] Applied, thanks! [1/2] hotplug pending: only check if USB devices are left when one was unplugged commit: a23bab5178ecbe2df7d6d425bbd5e0a7005b8c7e [2/2] hotplug pending: only check for USB hoptplug support when actually needed commit: ebe5f14c50d938a654eebf72a1bfb006caeceaff