From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 217307] windows guest entering boot loop when nested virtualization enabled and hyperv installed
Date: Mon, 10 Jul 2023 19:47:04 +0000 [thread overview]
Message-ID: <bug-217307-28872-zb32orXLA7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217307-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217307
--- Comment #18 from Sean Christopherson (seanjc@google.com) ---
> it seems that my problem is something that exclusively affects 12th gen and
> above
Can you try running a single vCPU VM, and pin that vCPU to a pCPU on a P-Core?
If this is indeed specific to 12th gen CPUs, then my guess is that hybrid CPUs
are to blame. E.g. KVM already disables vPMU (commit 4d7404e5ee00 "KVM:
x86/pmu: Disable vPMU support on hybrid CPUs (host PMUs)"), I wouldn't be at
all surprised if there are more problems lurking.
--
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:[~2023-07-10 19:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 10:39 [Bug 217307] New: windows guest entering boot loop when nested virtualization enabled and hyperv installed bugzilla-daemon
2023-04-06 10:58 ` [Bug 217307] " bugzilla-daemon
2023-04-06 11:00 ` bugzilla-daemon
2023-04-06 11:14 ` bugzilla-daemon
2023-05-22 22:14 ` bugzilla-daemon
2023-05-23 7:38 ` bugzilla-daemon
2023-06-25 19:12 ` bugzilla-daemon
2023-06-27 8:28 ` bugzilla-daemon
2023-06-27 16:39 ` bugzilla-daemon
2023-06-27 18:20 ` bugzilla-daemon
2023-06-27 21:37 ` bugzilla-daemon
2023-07-01 9:44 ` bugzilla-daemon
2023-07-05 14:57 ` bugzilla-daemon
2023-07-05 15:05 ` bugzilla-daemon
2023-07-05 15:15 ` bugzilla-daemon
2023-07-05 15:18 ` bugzilla-daemon
2023-07-05 15:23 ` bugzilla-daemon
2023-07-05 15:27 ` bugzilla-daemon
2023-07-10 19:47 ` bugzilla-daemon [this message]
2023-07-10 19:49 ` bugzilla-daemon
2023-07-10 19:50 ` 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-217307-28872-zb32orXLA7@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.