From: Igor Mammedov <imammedo@redhat.com>
To: Reinoud Zandijk <reinoud@NetBSD.org>
Cc: qemu-devel@nongnu.org, isaku.yamahata@gmail.com
Subject: Re: Windows 10 won't run on default x86_64 machine anymore
Date: Tue, 16 Mar 2021 21:34:08 +0100 [thread overview]
Message-ID: <20210316213408.0de27ac2@redhat.com> (raw)
In-Reply-To: <20210316181750.6306bfc5@redhat.com>
On Tue, 16 Mar 2021 18:17:50 +0100
Igor Mammedov <imammedo@redhat.com> wrote:
> On Tue, 16 Mar 2021 17:28:52 +0100
> Reinoud Zandijk <reinoud@NetBSD.org> wrote:
>
> > On Tue, Mar 16, 2021 at 01:53:01PM +0100, Igor Mammedov wrote:
> > > > The image file was downloaded pre-installed from Microsoft for Edge browser
> > > > evaluation. I used it first on Qemu 5.1 IIRC and it kept working in Qemu 5.2.
> > >
> > > issue looks similar to:
> > > 0a343a5add7 i386/acpi: restore device paths for pre-5.1 vms
> > >
> > > I think that's the problem, the old Windows image (installed on old QEMU),
> > > may fail to boot if started on newest machine type of a newer QEMU.
> > > User should use versioned machine type (the same version it was installed on)
> > > to keep it working the same way otherwise there is no promise that machine ABI
> > > won't change.
> >
> > The machine setup doesn't mind changing the machine to the Q35 type; its only
> > the older machine thats failing to work.
>
> never-mind, either we have a bug on piix4 side of QEMU or Windows doesn't support
> smm less mode, probably the former since q35 works.
> I'm trying to dig out what's going wrong,
> maybe Isaku Yamahata can also look into it.
Thanks for reporting it before it was released
please test/review fix that I've just posted:
"[PATCH for-6.0] x86:acpi:piix4: reinitialize PM1.CNT on reset"
> >
> > Reinoud
> >
> >
>
>
next prev parent reply other threads:[~2021-03-16 20:35 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 [this message]
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=20210316213408.0de27ac2@redhat.com \
--to=imammedo@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).