From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 218267] [Sapphire Rapids][Upstream]Boot up multiple Windows VMs hang
Date: Tue, 24 Dec 2024 06:44:02 +0000 [thread overview]
Message-ID: <bug-218267-28872-QUWXv7CQCD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218267-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218267
shu.info.oss@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |shu.info.oss@gmail.com
--- Comment #10 from shu.info.oss@gmail.com ---
Hi Gao,
(In reply to Chao Gao from comment #7)
> I just checked the microcode release
> https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases.
> The microcode fix hasn't been released yet, but the erratum is already in
> SPR/EMR specification. e.g., for SPR,
>
> SPR141. VM Exit Following MOV to CR8 Instruction May Lead to Unexpected
> IDT Vectoring-Information
> Problem: Under certain conditions, a VM exit following execution of the MOV
> to CR8
> instruction may unexpectedly result in setting the Valid bit (bit 31) of the
> IDTVectoring Information Field in the Virtual Machine Control Structure
> (VMCS).
> Implication: Depending on the operation of the virtual-machine monitor
> (VMM), this
> may result in unexpected VM behavior.
> Workaround: It may be possible for the BIOS to contain a workaround for this
> erratum
Can we resolve this bug with only BIOS updates if a update patch includes a fix
for this bug?
If so, what is ticket number for a update patch of BIOS? it is SPR141?
Thanks,
Hidehiko Matsumoto
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-12-24 6:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 8:23 [Bug 218267] New: [Sapphire Rapids][Upstream]Boot up multiple Windows VMs hang bugzilla-daemon
2023-12-18 17:54 ` Sean Christopherson
2023-12-18 17:54 ` [Bug 218267] " bugzilla-daemon
2024-03-27 11:59 ` bugzilla-daemon
2024-04-08 5:21 ` bugzilla-daemon
2024-04-08 17:22 ` bugzilla-daemon
2024-12-13 17:25 ` Maxim Levitsky
2024-08-06 11:02 ` bugzilla-daemon
2024-12-13 17:25 ` bugzilla-daemon
2024-12-14 1:33 ` bugzilla-daemon
2024-12-16 19:08 ` bugzilla-daemon
2025-01-22 16:43 ` Maxim Levitsky
2024-12-17 3:13 ` bugzilla-daemon
2024-12-24 6:44 ` bugzilla-daemon [this message]
2025-01-22 16:43 ` bugzilla-daemon
2025-01-27 18:32 ` bugzilla-daemon
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=bug-218267-28872-QUWXv7CQCD@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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.