All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: Windows 11 guest crashing supposedly in smm after some time of use
       [not found] <c0bf0011-a697-da29-c2d2-8c16e9df21cf@outlook.com>
@ 2023-02-13 14:58 ` Michał Zegan
  2023-02-16 18:06 ` Fwd: " Michał Zegan
  1 sibling, 0 replies; 5+ messages in thread
From: Michał Zegan @ 2023-02-13 14:58 UTC (permalink / raw)
  To: qemu-devel

ping?

W dniu 10.02.2023 o 15:48, Michał Zegan pisze:
> 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
>


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Fwd: Windows 11 guest crashing supposedly in smm after some time of use
       [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
  2023-02-16 18:29   ` Sean Christopherson
  1 sibling, 1 reply; 5+ messages in thread
From: Michał Zegan @ 2023-02-16 18:06 UTC (permalink / raw)
  To: kvm

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Fwd: Windows 11 guest crashing supposedly in smm after some time of use
  2023-02-16 18:06 ` Fwd: " Michał Zegan
@ 2023-02-16 18:29   ` Sean Christopherson
  2023-02-16 18:32     ` Michał Zegan
  0 siblings, 1 reply; 5+ messages in thread
From: Sean Christopherson @ 2023-02-16 18:29 UTC (permalink / raw)
  To: Michał Zegan; +Cc: kvm

On Thu, Feb 16, 2023, Michał Zegan wrote:
> Resending to kvm mailing list, in case someone here might help... Also will
> try again with newer ovmf, but assume it happens.
> 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.

...

> Guest is windows 11 pro 64 bit.
> 
> What crashes is qemu itself, not that the guest is bsod'ing.

Can you try a 6.2 or later kernel?  E.g. Linus' HEAD, linux-next, kvm/queue, etc.
KVM had a pile of SMM fixes[*] merged for 6.2 specifically aimed at fixing issues
with secure boot of Windows 11 guest.  They aren't likely to be backported to LTS
kernels as they aren't easily consumable (though I'm guessing software vendors
will end up backporting to their supported kernels).

[*] https://lore.kernel.org/all/20221025124741.228045-1-mlevitsk@redhat.com

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Fwd: Windows 11 guest crashing supposedly in smm after some time of use
  2023-02-16 18:29   ` Sean Christopherson
@ 2023-02-16 18:32     ` Michał Zegan
  2023-02-16 18:37       ` Sean Christopherson
  0 siblings, 1 reply; 5+ messages in thread
From: Michał Zegan @ 2023-02-16 18:32 UTC (permalink / raw)
  To: Sean Christopherson; +Cc: kvm

What these issues were? I don't have a quick ability to test kernel 6.2, 
but fedora will receive it, so I will definitely get a chance. Can you 
give me any pointers so that I can see whether it could be related?

W dniu 16.02.2023 o 19:29, Sean Christopherson pisze:
> On Thu, Feb 16, 2023, Michał Zegan wrote:
>> Resending to kvm mailing list, in case someone here might help... Also will
>> try again with newer ovmf, but assume it happens.
>> 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.
> ...
>
>> Guest is windows 11 pro 64 bit.
>>
>> What crashes is qemu itself, not that the guest is bsod'ing.
> Can you try a 6.2 or later kernel?  E.g. Linus' HEAD, linux-next, kvm/queue, etc.
> KVM had a pile of SMM fixes[*] merged for 6.2 specifically aimed at fixing issues
> with secure boot of Windows 11 guest.  They aren't likely to be backported to LTS
> kernels as they aren't easily consumable (though I'm guessing software vendors
> will end up backporting to their supported kernels).
>
> [*] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Fall%2F20221025124741.228045-1-mlevitsk%40redhat.com&data=05%7C01%7C%7Ced887369e7a446c55aa208db104bc18f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638121689771499220%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=oTa%2BDEScxiIn%2Fqd3KRUtqiegCv2J8p6RpZ%2Flnm%2F1f1I%3D&reserved=0

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Fwd: Windows 11 guest crashing supposedly in smm after some time of use
  2023-02-16 18:32     ` Michał Zegan
@ 2023-02-16 18:37       ` Sean Christopherson
  0 siblings, 0 replies; 5+ messages in thread
From: Sean Christopherson @ 2023-02-16 18:37 UTC (permalink / raw)
  To: Michał Zegan; +Cc: kvm, Maxim Levitsky

+Maxim

On Thu, Feb 16, 2023, Michał Zegan wrote:
> What these issues were? I don't have a quick ability to test kernel 6.2, but
> fedora will receive it, so I will definitely get a chance. Can you give me
> any pointers so that I can see whether it could be related?

I don't know the details, we (Google) don't rely on emulating SMM to support secure
boot.

Maxim, do you have any pointers for determining whether or not the KVM SMM issues
might be related?

> W dniu 16.02.2023 o 19:29, Sean Christopherson pisze:
> > On Thu, Feb 16, 2023, Michał Zegan wrote:
> > > Resending to kvm mailing list, in case someone here might help... Also will
> > > try again with newer ovmf, but assume it happens.
> > > 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.
> > ...
> > 
> > > Guest is windows 11 pro 64 bit.
> > > 
> > > What crashes is qemu itself, not that the guest is bsod'ing.
> > Can you try a 6.2 or later kernel?  E.g. Linus' HEAD, linux-next, kvm/queue, etc.
> > KVM had a pile of SMM fixes[*] merged for 6.2 specifically aimed at fixing issues
> > with secure boot of Windows 11 guest.  They aren't likely to be backported to LTS
> > kernels as they aren't easily consumable (though I'm guessing software vendors
> > will end up backporting to their supported kernels).
> > 
> > [*] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Fall%2F20221025124741.228045-1-mlevitsk%40redhat.com&data=05%7C01%7C%7Ced887369e7a446c55aa208db104bc18f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638121689771499220%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=oTa%2BDEScxiIn%2Fqd3KRUtqiegCv2J8p6RpZ%2Flnm%2F1f1I%3D&reserved=0
> 

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2023-02-16 18:37 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [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 ` Fwd: " Michał Zegan
2023-02-16 18:29   ` Sean Christopherson
2023-02-16 18:32     ` Michał Zegan
2023-02-16 18:37       ` Sean Christopherson

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.