diff options
| author | Thomas Huth <thuth@redhat.com> | 2024-10-24 15:04:05 +0200 |
|---|---|---|
| committer | Thomas Huth <thuth@redhat.com> | 2024-11-04 14:16:11 +0100 |
| commit | bc9da794cc4cec9dc04bae40e416b37ca71869cf (patch) | |
| tree | ebe36eca365fe69a65d6a7ef7f637058365a8e56 | |
| parent | e6a401d7a696d9e89c82e51f9b923addcbf879b6 (diff) | |
| download | qemu-bc9da794cc4cec9dc04bae40e416b37ca71869cf.zip qemu-bc9da794cc4cec9dc04bae40e416b37ca71869cf.tar.gz qemu-bc9da794cc4cec9dc04bae40e416b37ca71869cf.tar.bz2 | |
hw/s390x: Re-enable the pci-bridge device on s390x
Commit e779e5c05a ("hw/pci-bridge: Add a Kconfig switch for the
normal PCI bridge") added a config switch for the pci-bridge, so
that the device is not included in the s390x target anymore (since
the pci-bridge is not really useful on s390x).
However, it seems like libvirt is still adding pci-bridge devices
automatically to the guests' XML definitions (when adding a PCI
device to a non-zero PCI bus), so these guests are now broken due
to the missing pci-bridge in the QEMU binary.
To avoid disruption of the users, let's re-enable the pci-bridge
device on s390x for the time being.
Message-ID: <20241024130405.62134-1-thuth@redhat.com>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Reviewed-by: Boris Fiuczynski <fiuczy@linux.ibm.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Thomas Huth <thuth@redhat.com>
| -rw-r--r-- | hw/s390x/Kconfig | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/hw/s390x/Kconfig b/hw/s390x/Kconfig index 3bbf4ae..82afdaa 100644 --- a/hw/s390x/Kconfig +++ b/hw/s390x/Kconfig @@ -7,6 +7,7 @@ config S390_CCW_VIRTIO imply VFIO_AP imply VFIO_CCW imply WDT_DIAG288 + imply PCI_BRIDGE imply PCIE_DEVICES imply IOMMUFD select PCI_EXPRESS |