diff options
| author | Vitaly Cheptsov | 2021-03-01 20:59:18 +0100 |
|---|---|---|
| committer | Michael S. Tsirkin | 2021-03-02 11:40:35 +0100 |
| commit | 0a343a5add75f9f90c65e932863d57ddbcb28f5c (patch) | |
| tree | a8753646e62b4349a21fb925a5f998d284e9465f /docs | |
| parent | Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging (diff) | |
| download | qemu-0a343a5add75f9f90c65e932863d57ddbcb28f5c.tar.gz qemu-0a343a5add75f9f90c65e932863d57ddbcb28f5c.tar.xz qemu-0a343a5add75f9f90c65e932863d57ddbcb28f5c.zip | |
i386/acpi: restore device paths for pre-5.1 vms
After fixing the _UID value for the primary PCI root bridge in
af1b80ae it was discovered that this change updates Windows
configuration in an incompatible way causing network configuration
failure unless DHCP is used. More details provided on the list:
https://lists.gnu.org/archive/html/qemu-devel/2021-02/msg08484.html
This change reverts the _UID update from 1 to 0 for q35 and i440fx
VMs before version 5.2 to maintain the original behaviour when
upgrading.
Cc: qemu-stable@nongnu.org
Cc: qemu-devel@nongnu.org
Reported-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Suggested-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Vitaly Cheptsov <cheptsov@ispras.ru>
Message-Id: <20210301195919.9333-1-cheptsov@ispras.ru>
Tested-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Fixes: af1b80ae56c9 ("i386/acpi: fix inconsistent QEMU/OVMF device paths")
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions