From: Isaku Yamahata <isaku.yamahata@gmail.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Isaku Yamahata <isaku.yamahata@intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Reinoud Zandijk <reinoud@netbsd.org>,
Igor Mammedov <imammedo@redhat.com>,
isaku.yamahata@gmail.com
Subject: Re: Windows 10 won't run on default x86_64 machine anymore
Date: Mon, 15 Mar 2021 14:32:52 -0700 [thread overview]
Message-ID: <20210315213252.GA1004959@private.email.ne.jp> (raw)
In-Reply-To: <YE+XFQ9MUcp9QHs6@redhat.com>
On Mon, Mar 15, 2021 at 05:19:17PM +0000,
"Daniel P. Berrangé" <berrange@redhat.com> wrote:
> On Mon, Mar 15, 2021 at 05:58:04PM +0100, Reinoud Zandijk wrote:
> > Hi,
> >
> > with the introduction of the following patch from 17th of February, Win10
> > won't boot anymore without explicitly setting the machine to be 5.2 compatible
> > like pc-1440fx-5.2. The default 6.0 will cause it to panic and gives as reason
> > only "ACPI error".
> >
> > It might work to counter a bug in Linux but this is not the place to do the
> > patch. The BSDs don't care and will boot fine with full ACPI regardless of the
> > machine chosen. Windows 10 however DOES care and gets confused.
> >
> > I think its better to revert this and fix Linux ;) or make it a selectable
> > feature as a workaround that's by default OFF :)
>
> I'm copying the people involved in creating/reviewing the commit you
> mention below.
>
> I've also added this regression to the 6.0 issues list, since being
> able to boot current Windows guests with the default machine type
> should be considered a release blocker IMHO.
>
> https://wiki.qemu.org/Planning/6.0#Not_fixed_yet
It's about ACPI spec conformance. What qemu command line is used?
Smi is explicitly disabled (property smm=off), but guest requires legacy bios mode?
What about enabling smm mode? or "-global PIIX4_PM.smm-compat=on"
(or "-global ICH9-LPC.smm-compat=on" if you use q35)
Thanks,
Isaku Yamahata
--
Isaku Yamahata <isaku.yamahata@gmail.com>
next prev parent reply other threads:[~2021-03-15 21:34 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 [this message]
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
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=20210315213252.GA1004959@private.email.ne.jp \
--to=isaku.yamahata@gmail.com \
--cc=berrange@redhat.com \
--cc=imammedo@redhat.com \
--cc=isaku.yamahata@intel.com \
--cc=mst@redhat.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).