Re: pkvm boot failures

[Marc Zyngier <maz@kernel.org>]

On Mon, 09 Jun 2025 14:23:40 +0100,
"Aneesh Kumar K.V" <aneesh.kumar@kernel.org> wrote:
> 
> I am hitting the below failure with v6.15 (I tried other kernel versions
> with similar results). I disabled CONFIG_PROTECTED_NVHE_STACKTRACE
> because with CONFIG_NVHE_EL2_DEBUG, the stack was pointing at
> hyp_assert_lock_held() .

Why do you get different results based on the backtrace support?

> 
> [    0.664457] kvm [1]: nVHE hyp panic at: [<ffff80008050b10c>] __kvm_nvhe_handle_trap+0x34/0x10c!
> [    0.664538] kvm [1]: Cannot dump pKVM nVHE stacktrace: !CONFIG_PROTECTED_NVHE_STACKTRACE
> [    0.664566] kvm [1]: Hyp Offset: 0xffff000007c00000
> [    0.664631] Kernel panic - not syncing: HYP panic:
> [    0.664631] PS:614023c9 PC:000080007890b10c ESR:0000000096000007

ESR_EL2 shows that this is a S1 translation fault, level 3, from
EL2. This is consistent with hitting the BUG() in handle_trap(().

What is at this PC?

> [    0.664631] FAR:0000800078c252f0 HPFAR:0000000000000000 PAR:0000000000000000

FAR_EL2 is valid (as per the above), so what is EL2 trying to access
at this address?

> I was able to locate a .config that make the pkvm work, But i am not
> able to identify which config dependency is making the difference. I am
> attaching below the working and non working kernel configs. I am using
> FVP to test this.

If you're using a model, it should be pretty easy to track all of the
above.

Thanks,

	M.

-- 
Jazz isn't dead. It just smells funny.