From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 218267] [Sapphire Rapids][Upstream]Boot up multiple Windows VMs hang
Date: Fri, 13 Dec 2024 17:25:47 +0000 [thread overview]
Message-ID: <bug-218267-28872-7E0jDCZcud@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218267-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218267
--- Comment #6 from mlevitsk@redhat.com ---
On Mon, 2024-04-08 at 17:22 +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=218267
>
> --- Comment #4 from Sean Christopherson (seanjc@google.com) ---
> On Mon, Apr 08, 2024, bugzilla-daemon@kernel.org wrote:
> > This is not considered a Linux/KVM issue.
>
> Can you elaborate? E.g. if this an SPR ucode/CPU bug, it would be nice to
> know
> what's going wrong, so that at the very least we can more easily triage
> issues.
>
Hi!
Any update on this? We seem to hit this bug as well but so far I don't have new
details on what is going on.
Best regards,
Maxim Levitsky
--
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-13 17:25 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 [this message]
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
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-7E0jDCZcud@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox