Re: KVM planes branches

Carlos López <[email protected]> Mon, 19 Jan 2026 12:22:40 +0100
Newsgroups dev.linux.lists.coconut-svsm
Message-ID <[email protected]>
Hi,

On 1/7/26 3:02 PM, Oliver Steffen wrote:
> Hi everyone,
> happy new year!
> 
> I am curious about the state of the KVM planes effort and want
> to experiment with it a bit.
> I tried out the KVM planes branches we have in our GitHub org.
> I built Qemu and the host kernel from there and I am able to launch
> the current SVSM with that. QEMU just needed the patch for MADT-via-IGVM.
> But the OVMF does not seem to start. All I see is
> 
> ...
> [SVSM] VTPM: TPM 2.0 Reference Implementation initialized
> [SVSM] [CPU 0] Virtual memory pages used: 0 * 4K, 0 * 2M
> [SVSM] VMSA PA: 0x8000f49000
> [SVSM] Launching Firmware
> [init] COCONUT-SVSM init process starting
> [SVSM] Terminating task init, exit_code 0
> [SVSM] Launching request-processing task on CPU 1
> [SVSM] Launching request-processing task on CPU 2
> [SVSM] Launching request-processing task on CPU 0
> [SVSM] Launching request-processing task on CPU 3
> 
> and then it seems to hang forever.
> Is that expected? Do I need a specific commit of SVSM or EDK2?

I managed to track down the issue to an infinite loop within KVM. Please
try the following fix:

    https://github.com/coconut-svsm/linux/pull/19

In my environment this allows edk2 to make progress and reach the grub
menu. As mentioned in a previous email, you will need to revert
539624271cb8 ("sev: require the debug register virtualization feature")
temporarily in the SVSM.

Best,
Carlos