From: Cole Robinson <crobinso@redhat.com>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Dov Murik <dovmurik@linux.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Singh, Brijesh" <brijesh.singh@amd.com>
Subject: adding 'official' way to dump SEV VMSA
Date: Wed, 13 Apr 2022 09:36:23 -0400 [thread overview]
Message-ID: <a713533d-c4c5-2237-58d0-57b812a56ba4@redhat.com> (raw)
Hi all,
SEV-ES and SEV-SNP attestation require a copy of the initial VMSA to
validate the launch measurement. For developers dipping their toe into
SEV-* work, the easiest way to get sample VMSA data for their machine is
to grab it from a running VM.
There's two techniques I've seen for that: patch some printing into
kernel __sev_launch_update_vmsa, or use systemtap like danpb's script
here: https://gitlab.com/berrange/libvirt/-/blob/lgtm/scripts/sev-vmsa.stp
Seems like this could be friendlier though. I'd like to work on this if
others agree.
Some ideas I've seen mentioned in passing:
- debugfs entry in /sys/kernel/debug/kvm/.../vcpuX/
- new KVM ioctl
- something with tracepoints
- some kind of dump in dmesg that doesn't require a patch
Thoughts?
Thanks,
Cole
next reply other threads:[~2022-04-13 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 13:36 Cole Robinson [this message]
2022-04-14 8:19 ` adding 'official' way to dump SEV VMSA Dov Murik
2022-04-14 8:25 ` Dr. David Alan Gilbert
2022-04-19 13:33 ` Cole Robinson
2022-04-19 14:23 ` Dr. David Alan Gilbert
2022-04-19 17:04 ` Daniel P. Berrangé
2022-04-19 16:59 ` Daniel P. Berrangé
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=a713533d-c4c5-2237-58d0-57b812a56ba4@redhat.com \
--to=crobinso@redhat.com \
--cc=berrange@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=dgilbert@redhat.com \
--cc=dovmurik@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas.lendacky@amd.com \
/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;
as well as URLs for NNTP newsgroup(s).