[Bug 219602] By default kvm.enable_virt_at_load breaks other virtualization solutions

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

 



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

--- Comment #2 from Pinky (acmelab@xxxxxxxxx) ---
(In reply to hch from comment #1)
> On Mon, Dec 16, 2024 at 09:15:22AM +0000, bugzilla-daemon@xxxxxxxxxx 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.




[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