public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 219602] New: Default of kvm.enable_virt_at_load breaks other virtualization solutions (by default)
Date: Mon, 16 Dec 2024 09:15:22 +0000	[thread overview]
Message-ID: <bug-219602-28872@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 219602
           Summary: Default of kvm.enable_virt_at_load breaks other
                    virtualization solutions (by default)
           Product: Virtualization
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: acmelab@proton.me
        Regression: No

Previously (kernel 6.11 and lower) VMs of other virtualization solutions such
as VirtualBox could be started with the KVM module enabled.

Since 6.12 setting kvm.enable_virt_at_load=0 needs to be set at boot if the KVM
module is enabled, if you want to use other virtualization solution beside KVM. 

The commit that introduced the new behavior is
https://github.com/torvalds/linux/commit/b4886fab6fb620b96ad7eeefb9801c42dfa91741.
To be clear it is not about the feature itself, but the default. I am also
aware that this might be intentional; but given it deviates from
previous/expected behavior, it seems like a regression.

The fix would be to set the feature to be off by default. This would be
trivial, but first I need to know for sure that this is considered a bug.

-- 
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:[~2024-12-16  9:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16  9:15 bugzilla-daemon [this message]
2024-12-16  9:22 ` [Bug 219602] Default of kvm.enable_virt_at_load breaks other virtualization solutions (by default) 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

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@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