public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
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	[thread overview]
Message-ID: <177496799451.4007206.11636342415787354322.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260330110954.82174-1-f.ebner@proxmox.com>

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




      parent reply	other threads:[~2026-03-31 18:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 11:09 Fiona Ebner
2026-03-30 11:09 ` [PATCH qemu-server 1/2] hotplug pending: only check if USB devices are left when one was unplugged Fiona Ebner
2026-03-30 11:09 ` [PATCH qemu-server 2/2] hotplug pending: only check for USB hoptplug support when actually needed Fiona Ebner
2026-03-31 14:29 ` [PATCH-SERIES qemu-server 0/2] hotplug pending: only issue QMP commands related to USB hotplug if " Manuel Federanko
2026-03-31 18:40 ` Thomas Lamprecht [this message]

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=177496799451.4007206.11636342415787354322.b4-ty@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal