All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 217307] New: windows guest entering boot loop when nested virtualization enabled and hyperv installed
Date: Thu, 06 Apr 2023 10:39:27 +0000	[thread overview]
Message-ID: <bug-217307-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=217307

            Bug ID: 217307
           Summary: windows guest entering boot loop when nested
                    virtualization enabled and hyperv installed
           Product: Virtualization
           Version: unspecified
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: high
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: webczat@outlook.com
        Regression: No

Environment:
My host is fedora 37, currently running linux 6.2.5, but this is present for a
long time.
CPU is intel alderlake, core i7 12700h.
The os has kvm_intel module loaded with nested=y parameter, so nested
virtualization is enabled.
The guest vm is a q35 x86_64 vm with cpu=host set, running on qemu version
7.0.0, accel=kvm, smm, uefi, secureboot and tpm enabled.
Command line for qemu is attached to the bug.
VM is running a windows 11 pro 64 bit os.

What happens is that the moment I install any HyperV features on the windows11
os and then reboot, it does not boot again.
Basically it self reboots once and goes into recovery. Because I am blind I
cannot really say whether it shows some blue screen of death before rebooting,
but I actually don't think so.
The only thing i can do to make it work is to disable nested virtualization.
There is no known workaround which leaves it enabled, unless i disable the vmx
cpu feature, but that's not what I want to achieve, my goal is mostly to
run/test wsl2 or to play with docker.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2023-04-06 10:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 10:39 bugzilla-daemon [this message]
2023-04-06 10:58 ` [Bug 217307] windows guest entering boot loop when nested virtualization enabled and hyperv installed 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
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@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.