From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 219602] By default kvm.enable_virt_at_load breaks other virtualization solutions
Date: Tue, 17 Dec 2024 17:50:59 +0000 [thread overview]
Message-ID: <bug-219602-28872-W7n2wWgZ6r@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219602-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219602
Pinky (acmelab@proton.me) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |ANSWERED
--- Comment #4 from Pinky (acmelab@proton.me) ---
(In reply to Sean Christopherson from comment #3)
> FWIW, Paolo and I do want to get to a state where out-of-tree hypervisors
> don't need to do weird things, but it'll take some time to get to that state.
>
> https://lore.kernel.org/all/ZwQjUSOle6sWARsr@google.com
Thanks for the longer explanation (including the link's content). Given that
this was discussed already, I am going to close this then.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2024-12-17 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 9:15 [Bug 219602] New: Default of kvm.enable_virt_at_load breaks other virtualization solutions (by default) bugzilla-daemon
2024-12-16 9:22 ` [Bug 219602] " bugzilla-daemon
2024-12-16 9:30 ` [Bug 219602] By default kvm.enable_virt_at_load breaks other virtualization solutions bugzilla-daemon
2024-12-17 4:19 ` [Bug 219602] New: Default of kvm.enable_virt_at_load breaks other virtualization solutions (by default) Christoph Hellwig
2024-12-17 4:20 ` [Bug 219602] By default kvm.enable_virt_at_load breaks other virtualization solutions bugzilla-daemon
2024-12-17 15:52 ` bugzilla-daemon
2024-12-17 16:46 ` bugzilla-daemon
2024-12-17 17:50 ` bugzilla-daemon [this message]
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-219602-28872-W7n2wWgZ6r@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