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] By default kvm.enable_virt_at_load breaks other virtualization solutions
Date: Tue, 17 Dec 2024 16:46:05 +0000	[thread overview]
Message-ID: <bug-219602-28872-7culb4JiXS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219602-28872@https.bugzilla.kernel.org/>

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

Sean Christopherson (seanjc@google.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |seanjc@google.com

--- Comment #3 from Sean Christopherson (seanjc@google.com) ---
From the kernel docs:

        kvm.enable_virt_at_load=[KVM,ARM64,LOONGARCH,MIPS,RISCV,X86]
                        If enabled, KVM will enable virtualization in hardware
                        when KVM is loaded, and disable virtualization when KVM
                        is unloaded (if KVM is built as a module).

                        If disabled, KVM will dynamically enable and disable
                        virtualization on-demand when creating and destroying
                        VMs, i.e. on the 0=>1 and 1=>0 transitions of the
                        number of VMs.

                        Enabling virtualization at module lode avoids potential
                        latency for creation of the 0=>1 VM, as KVM serializes
                        virtualization enabling across all online CPUs.  The
                        "cost" of enabling virtualization when KVM is loaded,
                        is that doing so may interfere with using out-of-tree
                        hypervisors that want to "own" virtualization hardware.

In addition to the latency angle, TDX support is effectively going to require
VMX to be enabled when KVM is loaded, i.e. trying to do something different
will only delay the inevitable.

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

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-12-17 16:46 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 [this message]
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-7culb4JiXS@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