Re: [edk2-devel] Error when launching SEV-ES guest with OvmfPkg/AmdSev build

["Dov Murik" <dovmurik@linux.ibm.com>]

(for the mailing list archives:)

This bug was fixed by commit 36b561623a4b ("OvmfPkg/AmdSev: update the
fdf to use new workarea PCD" by Brijesh Singh).

The fix was merged to edk2 master branch on 2021-10-19:
https://github.com/tianocore/edk2/pull/2080

Thanks Brijesh, Min, Gerd, and Jiewen for your help with this issue.

-Dov


On 13/10/2021 12:35, Dov Murik wrote:
> Hello,
> 
> I encountered the following problem when trying to launch SEV-ES
> (policy=0x5) guests with the OvmfPkg/AmdSev/AmdSevX64 package build:
> 
> 
> $ sudo /home/dmurik/git/qemu/build/qemu-system-x86_64 -enable-kvm
> -machine q35 -smp 1 -m 2G -machine confidential-guest-support=sev0
> -object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1,policy=0x5
> -drive
> if=pflash,format=raw,unit=0,file=/home/dmurik/git/edk2/Build/AmdSev/DEBUG_GCC5/FV/OVMF.fd,readonly=on
> -nographic -global isa-debugcon.iobase=0x402 -debugcon file:ovmf-1.log
> -monitor pty
> 
> char device redirected to /dev/pts/6 (label compat_monitor0)
> error: kvm run failed Invalid argument
> EAX=0000000a EBX=0000006f ECX=00000000 EDX=00000000
> ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000
> EIP=0000fff0 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
> ES =0000 00000000 00000000 00000000
> CS =0000 00000000 00000000 00000000
> SS =0000 00000000 00000000 00000000
> DS =0000 00000000 00000000 00000000
> FS =0000 00000000 00000000 00000000
> GS =0000 00000000 00000000 00000000
> LDT=0000 00000000 00000000 00000000
> TR =0000 00000000 00000000 00000000
> GDT=     00000000 00000000
> IDT=     00000000 00000000
> CR0=c0000033 CR2=00000000 CR3=00000000 CR4=00000660
> DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
> DR3=0000000000000000
> DR6=00000000ffff0ff0 DR7=0000000000000400
> EFER=0000000000000100
> Code=?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? <??> ??
> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
> ?? ?? ?? ??
> 
> 
> ovmf-1.log is empty (even though OVMF is compiled with debug flags).
> 
> 
> Plain SEV (no -ES) guests work OK.
> 
> 
> The error is "kvm run failed Invalid argument", so I first tried
> switching kernels, but 5.11.0, 5.13.0, and 5.14.0 all gave the same result.
> 
> Then I tried an older OVMF release (edk2-stable202108) -- and it worked
> OK. So I started a git bisect session and found this first bad commit:
> 
> 
> commit ab77b6031b03733c28fa5f477d802fd67b3f3ee0
> Author: Brijesh Singh <brijesh.singh@amd.com>
> Date:   Tue Aug 17 21:46:50 2021 +0800
> 
>     OvmfPkg/ResetVector: update SEV support to use new work area format
> 
>     BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=3429
> 
>     Update the SEV support to switch to using the newer work area format.
> 
> 
> I wonder if any change in this series should have also touched files in
> OvmfPkg/AmdSev and missed them.
> 
> Any other ideas on how to debug this are welcome.
> 
> Let me know if this should be reported/discussed somewhere else.
> 
> 
> Thanks,
> -Dov
> 
> 
> 
> 
>