From: Igor Mammedov <imammedo@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Reinoud Zandijk <reinoud@netbsd.org>,
qemu-devel@nongnu.org, Isaku Yamahata <isaku.yamahata@gmail.com>
Subject: Re: Windows 10 won't run on default x86_64 machine anymore
Date: Tue, 16 Mar 2021 14:04:49 +0100 [thread overview]
Message-ID: <20210316140449.5e6695f9@redhat.com> (raw)
In-Reply-To: <YFCnPEvCDdbHRl/o@redhat.com>
On Tue, 16 Mar 2021 12:40:28 +0000
Daniel P. Berrangé <berrange@redhat.com> wrote:
> On Tue, Mar 16, 2021 at 01:33:54PM +0100, Igor Mammedov wrote:
> > On Mon, 15 Mar 2021 15:05:26 -0700
> > Isaku Yamahata <isaku.yamahata@gmail.com> wrote:
> >
> > > On Mon, Mar 15, 2021 at 05:58:04PM +0100,
> > > Reinoud Zandijk <reinoud@NetBSD.org> wrote:
> > >
> > > > I think its better to revert this and fix Linux ;) or make it a selectable
> > > > feature as a workaround that's by default OFF :)
> > >
> > > Anyway here is a patch to flip the default.
> > > At the moment, this is compile-only tested to provide the change quickly
> > > and make discussion progress.
> > >
> > > From 50deeed38832ceccfb68f78dd66de5a1741b2897 Mon Sep 17 00:00:00 2001
> > > Message-Id: <50deeed38832ceccfb68f78dd66de5a1741b2897.1615845421.git.isaku.yamahata@intel.com>
> > > From: Isaku Yamahata <isaku.yamahata@intel.com>
> > > Date: Mon, 15 Mar 2021 14:42:33 -0700
> > > Subject: [PATCH] ich9, piix4: flip default value for smm-compat
> > >
> > > Make default value for smm-compat of ich9, piix4 true to keep old
> > > behavior.
> > > To get new (and more conformance to ACPI spec) behavior, explicitly
> > > set "-global ICH9-LPC.smm-compat=off" or
> > > "-global PIIX4_PM.smm-compat=off".
> >
> > I'm not sure we should do that,
> > it's fine for non-versioned/new machine type to change in incompatible way with old images,
> > it's the job of old versioned machines types to maintain compatibility.
> > It's of cause pain for users if they use are unable to boot old image
> > on newest machine type, but we never promised that and if we made such
> > promise we would never be able to fix bugs.
>
> If this incompatibility with Windows 10 is confirmed though, I don't
> think it is viable for QEMU to ship the default machine type with
> settings that break Windows 10.
Choice is Windows vs Linux kernel
the later behaves correctly (as spec dictates) and 'offending' commit
fixes QEMU deviation from spec. It might be hard to convince kernel
side to merge a hack for Windows sake that goes against spec.
As for Windows, if new install works fine then that's all fine,
users really should use version-ed machine types or instead of
pushing old broken 'features' to [new] default machine types.
>
>
>
> Regards,
> Daniel
prev parent reply other threads:[~2021-03-16 13:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 16:58 Windows 10 won't run on default x86_64 machine anymore Reinoud Zandijk
2021-03-15 17:19 ` Daniel P. Berrangé
2021-03-15 21:32 ` Isaku Yamahata
2021-03-15 17:53 ` Igor Mammedov
2021-03-15 22:27 ` Reinoud Zandijk
2021-03-16 1:55 ` Isaku Yamahata
2021-03-16 12:13 ` Igor Mammedov
2021-03-16 12:49 ` Paolo Bonzini
2021-03-16 13:10 ` Igor Mammedov
2021-03-16 16:49 ` Igor Mammedov
2021-03-16 17:33 ` Paolo Bonzini
2021-03-16 18:49 ` Igor Mammedov
2021-03-16 16:27 ` Reinoud Zandijk
2021-03-16 17:38 ` Paolo Bonzini
2021-03-16 16:20 ` Reinoud Zandijk
2021-03-16 16:41 ` Reinoud Zandijk
2021-03-16 12:53 ` Igor Mammedov
2021-03-16 16:28 ` Reinoud Zandijk
2021-03-16 17:17 ` Igor Mammedov
2021-03-16 20:34 ` Igor Mammedov
2021-03-17 8:58 ` Reinoud Zandijk
2021-03-17 9:54 ` Igor Mammedov
2021-03-17 15:10 ` Reinoud Zandijk
2021-03-17 15:13 ` Reinoud Zandijk
2021-03-15 21:59 ` Michael S. Tsirkin
2021-03-15 22:05 ` Isaku Yamahata
2021-03-16 12:33 ` Igor Mammedov
2021-03-16 12:40 ` Daniel P. Berrangé
2021-03-16 13:04 ` Igor Mammedov [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=20210316140449.5e6695f9@redhat.com \
--to=imammedo@redhat.com \
--cc=berrange@redhat.com \
--cc=isaku.yamahata@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=reinoud@netbsd.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).