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 15:52:39 +0000 [thread overview]
Message-ID: <bug-219602-28872-7SvCKPgI24@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219602-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219602
--- Comment #2 from Pinky (acmelab@proton.me) ---
(In reply to hch from comment #1)
> On Mon, Dec 16, 2024 at 09:15:22AM +0000, bugzilla-daemon@kernel.org wrote:
> > Previously (kernel 6.11 and lower) VMs of other virtualization solutions
> such
> > as VirtualBox could be started with the KVM module enabled.
>
> There is no other in-tree user of the hardware virtualization
> capabilities, so this can't break anything by definition.
That sounds like a dead-end argument to me. What is the use case for this new
feature actually? What would be the disadvantage to turn this off by default?
--
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:[~2024-12-17 15:52 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 [this message]
2024-12-17 16:46 ` bugzilla-daemon
2024-12-17 17: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-219602-28872-7SvCKPgI24@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.