[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v6 18/23] sev: emit the SEV_MEASUREMENT event
From: |
Brijesh Singh |
Subject: |
Re: [Qemu-devel] [PATCH v6 18/23] sev: emit the SEV_MEASUREMENT event |
Date: |
Tue, 30 Jan 2018 16:13:13 -0600 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 |
On 1/30/18 2:08 PM, Dr. David Alan Gilbert wrote:
> * Brijesh Singh (address@hidden) wrote:
>> During machine creation we encrypted the guest bios image, the
>> LAUNCH_MEASURE command can be used to retrieve the measurement of
>> the encrypted memory region. Emit the SEV_MEASUREMENT event so that
>> libvirt can grab the measurement value as soon as we are done with
>> creating the encrypted machine.
> Can you ust clarify what happens if the libvirt has disconnected and
> reconnected to qemu and so didn't see the event? Can the reconnecting
> libvirt query it and find out it's ready/not ready yet?
Dave,
I have not looked into details between libvirt and qemu interaction to
comment how and when the events will be delivered. Recently, one of my
colleague was implementing libvirt interface for the SEV guest and ran
into somewhat a similar challenge and posted question on libvirt mailing
list [1].
In previous discussion on qemu mailing list, we agreed to implement SEV
MEASUREMENT event which can be seen by libvirt. That's what this patch
is doing.
But during the libvirt implementation it seems that qemu monitor
silently drops all the events before it get the first qmp_capabilities
command. At a quick glance it seems on reconnect, libvirt issues
qmp_capabilities command and any event issued before the
qmp_capabilities command will never to delivered to libvirt. we are
looking forĀ help from libvirt/qemu monitor experts on how we solve this
problem. Our goal is to provide the measurement to libvirt before
libvirt issues "continue" command. Since event can't be seen by libvirt
before it resumes the guest hence I was wondering if we should we should
drop the SEV measurement event and consider adding a new QMP command to
query the SEV measurement.
[1] https://www.redhat.com/archives/libvir-list/2018-January/msg00602.html
> Dave
>
>> Cc: Daniel P. Berrange <address@hidden>
>> Cc: Paolo Bonzini <address@hidden>
>> Cc: address@hidden
>> Signed-off-by: Brijesh Singh <address@hidden>
>> ---
>> accel/kvm/sev.c | 58
>> ++++++++++++++++++++++++++++++++++++++++++++++++++
>> accel/kvm/trace-events | 1 +
>> include/sysemu/sev.h | 1 +
>> 3 files changed, 60 insertions(+)
>>
>> diff --git a/accel/kvm/sev.c b/accel/kvm/sev.c
>> index 1f757df725df..b78cf3144b1d 100644
>> --- a/accel/kvm/sev.c
>> +++ b/accel/kvm/sev.c
>> @@ -19,11 +19,13 @@
>> #include "sysemu/sev.h"
>> #include "sysemu/sysemu.h"
>> #include "trace.h"
>> +#include "qapi-event.h"
>>
>> #define DEFAULT_GUEST_POLICY 0x1 /* disable debug */
>> #define DEFAULT_SEV_DEVICE "/dev/sev"
>>
>> static int sev_fd;
>> +static SEVState *sev_state;
>>
>> #define SEV_FW_MAX_ERROR 0x17
>>
>> @@ -418,6 +420,59 @@ err:
>> return ret;
>> }
>>
>> +static void
>> +sev_launch_get_measure(Notifier *notifier, void *unused)
>> +{
>> + int ret, error;
>> + guchar *data;
>> + SEVState *s = sev_state;
>> + struct kvm_sev_launch_measure *measurement;
>> +
>> + measurement = g_malloc0(sizeof(*measurement));
>> + if (!measurement) {
>> + return;
>> + }
>> +
>> + /* query the measurement blob length */
>> + ret = sev_ioctl(KVM_SEV_LAUNCH_MEASURE, measurement, &error);
>> + if (!measurement->len) {
>> + error_report("%s: LAUNCH_MEASURE ret=%d fw_error=%d '%s'",
>> + __func__, ret, error, fw_error_to_str(errno));
>> + goto free_measurement;
>> + }
>> +
>> + data = g_malloc(measurement->len);
>> + if (s->measurement) {
>> + goto free_data;
>> + }
>> +
>> + measurement->uaddr = (unsigned long)data;
>> +
>> + /* get the measurement blob */
>> + ret = sev_ioctl(KVM_SEV_LAUNCH_MEASURE, measurement, &error);
>> + if (ret) {
>> + error_report("%s: LAUNCH_MEASURE ret=%d fw_error=%d '%s'",
>> + __func__, ret, error, fw_error_to_str(errno));
>> + goto free_data;
>> + }
>> +
>> + sev_set_guest_state(SEV_STATE_SECRET);
>> +
>> + /* encode the measurement value and emit the event */
>> + s->measurement = g_base64_encode(data, measurement->len);
>> + trace_kvm_sev_launch_measurement(s->measurement);
>> + qapi_event_send_sev_measurement(s->measurement, &error_abort);
>> +
>> +free_data:
>> + g_free(data);
>> +free_measurement:
>> + g_free(measurement);
>> +}
>> +
>> +static Notifier sev_machine_done_notify = {
>> + .notify = sev_launch_get_measure,
>> +};
>> +
>> void *
>> sev_guest_init(const char *id)
>> {
>> @@ -461,6 +516,9 @@ sev_guest_init(const char *id)
>> }
>>
>> ram_block_notifier_add(&sev_ram_notifier);
>> + qemu_add_machine_init_done_notifier(&sev_machine_done_notify);
>> +
>> + sev_state = s;
>>
>> return s;
>> err:
>> diff --git a/accel/kvm/trace-events b/accel/kvm/trace-events
>> index c55546f36a25..51df5113ad07 100644
>> --- a/accel/kvm/trace-events
>> +++ b/accel/kvm/trace-events
>> @@ -20,3 +20,4 @@ kvm_memcrypt_unregister_region(void *addr, size_t len)
>> "addr %p len 0x%lu"
>> kvm_sev_change_state(char *old, char *new) "%s -> %s"
>> kvm_sev_launch_start(int policy, void *session, void *pdh) "policy 0x%x
>> session %p pdh %p"
>> kvm_sev_launch_update_data(void *addr, uint64_t len) "addr %p len 0x%"
>> PRIu64
>> +kvm_sev_launch_measurement(const char *value) "data %s"
>> diff --git a/include/sysemu/sev.h b/include/sysemu/sev.h
>> index 839800efdbbf..572120c865ea 100644
>> --- a/include/sysemu/sev.h
>> +++ b/include/sysemu/sev.h
>> @@ -63,6 +63,7 @@ typedef enum {
>>
>> struct SEVState {
>> QSevGuestInfo *sev_info;
>> + gchar *measurement;
>> };
>>
>> typedef struct SEVState SEVState;
>> --
>> 2.9.5
>>
> --
> Dr. David Alan Gilbert / address@hidden / Manchester, UK
- [Qemu-devel] [PATCH v6 07/23] kvm: update kvm.h to include memory encryption ioctls, (continued)
- [Qemu-devel] [PATCH v6 07/23] kvm: update kvm.h to include memory encryption ioctls, Brijesh Singh, 2018/01/29
- [Qemu-devel] [PATCH v6 11/23] sev: register the guest memory range which may contain encrypted data, Brijesh Singh, 2018/01/29
- [Qemu-devel] [PATCH v6 13/23] hmp: display memory encryption support in 'info kvm', Brijesh Singh, 2018/01/29
- [Qemu-devel] [PATCH v6 12/23] kvm: introduce memory encryption APIs, Brijesh Singh, 2018/01/29
- [Qemu-devel] [PATCH v6 15/23] sev: add command to encrypt guest memory region, Brijesh Singh, 2018/01/29
- [Qemu-devel] [PATCH v6 14/23] sev: add command to create launch memory encryption context, Brijesh Singh, 2018/01/29
- [Qemu-devel] [PATCH v6 10/23] sev: add command to initialize the memory encryption context, Brijesh Singh, 2018/01/29
- [Qemu-devel] [PATCH v6 18/23] sev: emit the SEV_MEASUREMENT event, Brijesh Singh, 2018/01/29
- [Qemu-devel] [PATCH v6 17/23] qapi: add SEV_MEASUREMENT event, Brijesh Singh, 2018/01/29
- [Qemu-devel] [PATCH v6 16/23] target/i386: encrypt bios rom, Brijesh Singh, 2018/01/29
- [Qemu-devel] [PATCH v6 20/23] hw: i386: set ram_debug_ops when memory encryption is enabled, Brijesh Singh, 2018/01/29
- [Qemu-devel] [PATCH v6 19/23] sev: Finalize the SEV guest launch flow, Brijesh Singh, 2018/01/29
- [Qemu-devel] [PATCH v6 21/23] sev: add debug encrypt and decrypt commands, Brijesh Singh, 2018/01/29
- [Qemu-devel] [PATCH v6 23/23] sev: add migration blocker, Brijesh Singh, 2018/01/29
- [Qemu-devel] [PATCH v6 22/23] target/i386: clear C-bit when walking SEV guest page table, Brijesh Singh, 2018/01/29
- Re: [Qemu-devel] [PATCH v6 00/23] x86: Secure Encrypted Virtualization (AMD), no-reply, 2018/01/29
- Re: [Qemu-devel] [PATCH v6 00/23] x86: Secure Encrypted Virtualization (AMD), no-reply, 2018/01/29