From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Vitaly Cheptsov <cheptsov@ispras.ru>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] i386/acpi: restore device paths for pre-5.1 vms
Date: Tue, 2 Mar 2021 08:05:06 +0100 [thread overview]
Message-ID: <f90f6a34-0c8b-c620-6906-18c12f2332d0@proxmox.com> (raw)
In-Reply-To: <20210301195919.9333-1-cheptsov@ispras.ru>
On 01.03.21 20:59, Vitaly Cheptsov wrote:
> 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>
Thanks for sending this! Works as advertised and can be cleanly cherry-picked
on top of the v5.2.0 tag.
Tested-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
next prev parent reply other threads:[~2021-03-02 7:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 19:59 [PATCH] i386/acpi: restore device paths for pre-5.1 vms Vitaly Cheptsov
2021-03-01 19:59 ` [PATCH] target/ppc: fix icount support on Book-e vms accessing SPRs Vitaly Cheptsov
2021-03-02 7:05 ` Thomas Lamprecht [this message]
2021-03-02 8:48 ` [PATCH] i386/acpi: restore device paths for pre-5.1 vms Igor Mammedov
2021-03-02 10:14 ` Michael S. Tsirkin
2021-03-22 15:43 ` Michael S. Tsirkin
2021-03-22 15:49 ` Vitaly Cheptsov
2021-03-23 14:48 ` Michael S. Tsirkin
2021-03-23 14:55 ` Vitaly Cheptsov
2021-03-23 15:04 ` Thomas Lamprecht
2021-03-23 16:54 ` Ways to deal with broken machine types Igor Mammedov
2021-03-23 17:40 ` Daniel P. Berrangé
2021-03-23 19:40 ` Michael S. Tsirkin
2021-03-30 11:21 ` David Edmondson
2021-03-30 11:53 ` Michael S. Tsirkin
2021-03-26 0:48 ` Igor Mammedov
2021-03-29 14:46 ` Dr. David Alan Gilbert
2021-03-29 20:32 ` Igor Mammedov
2021-03-23 19:32 ` [PATCH] i386/acpi: restore device paths for pre-5.1 vms Michael S. Tsirkin
2021-03-26 0:12 ` Igor Mammedov
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=f90f6a34-0c8b-c620-6906-18c12f2332d0@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=cheptsov@ispras.ru \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).