On Thu, Feb 08, 2018 at 10:17:28AM -0600, Brijesh Singh wrote:
> Anyway, the main issue is event emitted before "qmp_capabilities" are
> dropped silently , see [1] . In our case, the measurement event is emitted
> during the machine creation time, libvirt was still waiting to reconnect
> the monitor when event was emitted hence libvirt never gets the event.
> Because of this, I am not able to see any strong reason to emit the event.
> Do you see any issue with libvirt issuing a  'query-sev-launch-measure' to
> get the measurement on reconnect ?

Hmm, yes, I see so there can be a race between SEV emitting the event and
libvirtd making the initial monitor connection. In that case, we definitely
to have a QMP command to let libvirt explicitly query it. 

|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

Reply via email to