public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, Dominik Csapak <d.csapak@proxmox.com>
Subject: applied: [PATCH qemu-server v3 0/8] pci: bridges: cleanup and hotplug fix
Date: Thu, 10 Sep 2026 11:41:23 +0200	[thread overview]
Message-ID: <178903326515.71590.5328285538446790547.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260908135729.3869365-1-d.csapak@proxmox.com>

On Tue, 08 Sep 2026 15:52:00 +0200, Dominik Csapak wrote:
> Main motivation for this series was a defect in how we handle
> hotplugging certain devices:
> 
> When e.g. adding scsi15 on a vm with i440fx + lsi controller, we'd need
> scsihw2 (since only 7 devices can live on scsihw0 and scsihw1
> respectively) which sits on bus pci.4. This itself is not added by
> default to the config, so we tried to hotplug the bridge. This works,
> but without SHPC (which is neither the default, nor does it work
> reliably in all guests) one cannot hot-plug anything into a hot-plugged
> bridge. So when hotplugging scsi15 in this example, we'd hot-plug
> pci.4, but adding scsihw2 would fail and leave the disk in 'pending'.
> 
> [...]

Applied, thanks!

[1/8] tests: cfg2cmd: add test for ivshmem with q35
      commit: 2b3375f38583e859d97d4ca890bb8afafe85ed9a
[2/8] tests: cfg2cmd: add q35 + win7 + hostpci test
      commit: ece685a9731e3bbbe2a75cad534005d440b7007e
[3/8] code cleanup: pci: don't export print_pcie_root_port
      commit: 7a6b07426ebeef53f51d820a51d3a8fbbb7ac3b3
[4/8] code cleanup: hot-plug: simplify getting bridge for device
      commit: 98e60cd029eb84f6640cc51c442f6af84d4da4c0
[5/8] hotplug: don't try to hotplug bridges
      commit: cf5be37cbfa6e77e8cce4b1b9fe17a5ad7156bbc
[6/8] cfg2cmd: reject guests with machine version below 5.0
      commit: 313ba2cf8cbb216b7d999c2e5b5a934f33738a93
[7/8] cfg2cmd: pci: add bridges to device list up front
      commit: 8a1a62253ada60454265c4953fff9d2bd89771aa
[8/8] cfg2cmd: pci: add pci.4 by default starting with machine version 11.1
      commit: ad4d2f5afa479364f7fec953eed97040f59358b5




      parent reply	other threads:[~2026-09-10  9:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 13:52 [PATCH qemu-server v3 0/8] pci: bridges: cleanup and hotplug fix Dominik Csapak
2026-09-08 13:52 ` [PATCH qemu-server v3 1/8] tests: cfg2cmd: add test for ivshmem with q35 Dominik Csapak
2026-09-08 13:52 ` [PATCH qemu-server v3 2/8] tests: cfg2cmd: add q35 + win7 + hostpci test Dominik Csapak
2026-09-08 13:52 ` [PATCH qemu-server v3 3/8] code cleanup: pci: don't export print_pcie_root_port Dominik Csapak
2026-09-08 13:52 ` [PATCH qemu-server v3 4/8] code cleanup: hot-plug: simplify getting bridge for device Dominik Csapak
2026-09-08 13:52 ` [PATCH qemu-server v3 5/8] hotplug: don't try to hotplug bridges Dominik Csapak
2026-09-08 13:52 ` [PATCH qemu-server v3 6/8] cfg2cmd: reject guests with machine version below 5.0 Dominik Csapak
2026-09-08 13:52 ` [PATCH qemu-server v3 7/8] cfg2cmd: pci: add bridges to device list up front Dominik Csapak
2026-09-08 13:52 ` [PATCH qemu-server v3 8/8] cfg2cmd: pci: add pci.4 by default starting with machine version 11.1 Dominik Csapak
2026-09-10  9:41 ` Fiona Ebner [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=178903326515.71590.5328285538446790547.b4-ty@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=d.csapak@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