Arvid E. Picciani

> qemu-system-x86_64: qemu: SNP_LAUNCH_UPDATE (VMPL0) - SVSM binary @ 8000000000 > qemu-system-x86_64: qemu: SNP_LAUNCH_UPDATE (VMPL1) - OVMF binary @ ffc84000 maybe it's just me misunderstanding how this works, but isnt...

> Even though the guest is running at VMPL1 it gets the measurement for the full launch, which will contain the SVSM info. yes, see the comment after that. the...

OVMF contains bringup that's specific to the CSP, so it's very inconvenient to ask the customer to verify each new revision. see this specific comment for details (https://github.com/google/go-sev-guest/issues/20#issuecomment-1285927684) we're a...

> The VMPL level is there so that you can know which level created the report. this makes sense. thanks for all the explanations. If i understand correctly, the only...

> A friendly reminder that this issue had no activity for 30 days. Not stale

I'm interested in this for commercial reasons so we can definitely help with contributions if there's a consensus. I don't think an "native app" really is required tho. In my...

Fully agree on the systray. That's a thing windows users expect. Not sure about the wrapper app yet, but if someone else wants to pick that up why not. Currently...

@ThaUnknown

is there any hack to get `privileged:true` and `privileged_without_host_devices = false` working? we need to access `/dev/snp-guest` from the vm kernel, and this wont work with a regular bind mount

snp is upstream now in linux 6.11, qemu 9.1. libvirt has announced official support, but it still requires specific quirks in the xml. i'm going to try (if audio permits)...