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: Tue, 27 Jun 2023 08:28:19 +0000 [thread overview]
Message-ID: <bug-217307-28872-kMkFtlkZcH@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 #7 from vkuznets@redhat.com ---
Assuming this is not a KVM/QEMU regression, I'd suggest to explore two options:
1) Change "-cpu host" to a named CPU model. I don't see "alderlake" CPU models
in QEMU so I'd start with something like "Skylake-Client-v4". Remove all other
CPU options you have, like "rtm=off,mpx=off,host-cache-info=on,l3-cache=off".
Try to find the exact CPU option which breaks things. There were similar but
reversed (works with '-cpu host', doesn't work with a named model) issues in
the past, e.g.
https://lore.kernel.org/qemu-devel/20220308113445.859669-21-pbonzini@redhat.com/
2) Try disabling certain Hyper-V enlightenments, start with "hv-evmcs". In
theory, things should work (slowly, but still) without any Hyper-V
enlightenments.
--
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-06-27 8:29 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 [this message]
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
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-kMkFtlkZcH@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