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, 23 May 2023 07:38:53 +0000 [thread overview]
Message-ID: <bug-217307-28872-EXFXpGLVtg@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 #5 from Michał Zegan (webczat@outlook.com) ---
Hello.
It's sad that it's not that easy to figure out what the ... is going on here.
The problem with using qemu debugger is that it probably? doesn't really allow
me to break anywhere. but even with a non qemu debugger, I am unsure how would
I debug that usefully, that is stop at the right moment to capture anything
useful...? of course the best would be if someone with necessary skills could
repro it.
--
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-05-23 7:39 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 [this message]
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-EXFXpGLVtg@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