From: Igor Mammedov <imammedo@redhat.com>
To: Paolo Bonzini <pbonzini@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:10:44 +0100 [thread overview]
Message-ID: <20210316141044.311688bb@redhat.com> (raw)
In-Reply-To: <9e2e1d83-29c1-053a-fd43-187f6f824b39@redhat.com>
On Tue, 16 Mar 2021 13:49:57 +0100
Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 16/03/21 13:13, Igor Mammedov wrote:
> >>> Surprisingly without accelerator ie with tcg the default machine does seem to
> >>> get to the login prompt. Is the ACPI data tailored to indicate an
> >>> accelerator/VM or is it static? Could it be that the CPU reported by my
> >>> machine is causing the issue? With the NVMM accelerator it passes on the hosts
> >>
> >> I think tcg case can be explained by x86_machine_is_smm_enabled()
> >>
> >> bool x86_machine_is_smm_enabled(const X86MachineState *x86ms)
> >> ...
> >> if (tcg_enabled() || qtest_enabled()) {
> >> smm_available = true;
> >> } else if (kvm_enabled()) {
> >> smm_available = kvm_has_smm();
> >> }
> >> ...
> >>
> >> Although I don't know about nvmm case, this function also needs to be updated
> >> if smi isn't supported.
> > can you submit a patch for this please?
>
> nvmm is not part of upstream yet, so I guess it's up to Reinoud to fix
> it. Still, reproducing his testing conditions with KVM and -M smm=off
> is probably interesting because it also affects HAX, HVF and WHPX which
> are supported upstream.
I'm in process of preparing test env for it with reported Windows version,
so I'll try this case as well.
>
> Paolo
>
next prev parent reply other threads:[~2021-03-16 13:12 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 [this message]
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=20210316141044.311688bb@redhat.com \
--to=imammedo@redhat.com \
--cc=isaku.yamahata@gmail.com \
--cc=pbonzini@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).