From: "Michał Zegan" <webczat@outlook.com>
To: kvm@vger.kernel.org
Subject: Fwd: Windows 11 guest crashing supposedly in smm after some time of use
Date: Thu, 16 Feb 2023 19:06:41 +0100 [thread overview]
Message-ID: <BYAPR12MB301441A16CE6CFFE17147888A0A09@BYAPR12MB3014.namprd12.prod.outlook.com> (raw)
In-Reply-To: <c0bf0011-a697-da29-c2d2-8c16e9df21cf@outlook.com>
Resending to kvm mailing list, in case someone here might help... Also
will try again with newer ovmf, but assume it happens.
--- Treść przekazanej wiadomości ---
Temat: Windows 11 guest crashing supposedly in smm after some time of use
Data: Fri, 10 Feb 2023 15:48:56 +0100
Nadawca: Michał Zegan <webczat@outlook.com>
Adresat: qemu-devel@nongnu.org
Hello.
I have windows11 installed on a vm. This vm generally works properly,
but then might crash unexpectedly at any point, this includes situation
like logging onto the system and leaving it intact for like an hour or
less. This can be reproduced by waiting long enough but there is no
single known action causing it.
What could be the problem?
Configuration and error details:
My host is a msi vector gp76 laptop with intel core i7 12700h, 32gb of
memory, host os is fedora linux 37 with custom compiled linux kernel
(fedora patches). Current kernel version is 6.1.10 but when I installed
the vm it was 6.0 or less, don't quite remember exactly, and this bug
was present. Not sure if bios is up to date, but microcode is, if that
matters.
Hardware virtualization enabled, nested virtualization enabled in module
params for kvm_intel.
For vm using libvirt, qemu 7.0.0. Virtual machine is q35, smm enabled,
processor model set to host, firmware is uefi with secureboot and
preenrolled keys, tpm is enabled. Most/all hyperv enlightenments are
enabled.
Using virtio for what I can including virtio-scsi, virtio-input,
virtio-net, virtio-balloon, etc... installed windows drivers for all of
these things.
Guest is windows 11 pro 64 bit.
What crashes is qemu itself, not that the guest is bsod'ing.
Below is the link containing libvirt qemu log, containing the full qemu
command line and also the crash messages. Note virtualization is
disabled in vm even though nested virtualization enabled on host, and
hyperv not installed on windows, so it's likely not the cause.
https://gist.github.com/webczat/1f224e7ecdc17c5c26316e0121f4ed43
next prev parent reply other threads:[~2023-02-16 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c0bf0011-a697-da29-c2d2-8c16e9df21cf@outlook.com>
2023-02-13 14:58 ` Windows 11 guest crashing supposedly in smm after some time of use Michał Zegan
2023-02-16 18:06 ` Michał Zegan [this message]
2023-02-16 18:29 ` Fwd: " Sean Christopherson
2023-02-16 18:32 ` Michał Zegan
2023-02-16 18:37 ` Sean Christopherson
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=BYAPR12MB301441A16CE6CFFE17147888A0A09@BYAPR12MB3014.namprd12.prod.outlook.com \
--to=webczat@outlook.com \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.