[Bug 219602] New: Default of kvm.enable_virt_at_load breaks other virtualization solutions (by default)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxxxxxx
          Reporter: acmelab@xxxxxxxxx
        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.




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux