I wonder if I can hear any feedback about the change.
# This is my first time to propose a change to libvirt and I appreciate
# any comments in case I made something wrong.
On 2/20/24 15:31, Takashi Kajinami wrote:
This introduces the new "model" field in sev elements so that clients
This introduces the new "model" field in sev elements, returned by
domain capabilities API, so that client can ensure SEV-ES is available
in this hypervisor.
Signed-off-by: Takashi Kajinami
---
docs/formatdomaincaps.rst | 5 ++
src/conf/domain_capabilities.c | 2 +
enabled in KVM.
Takashi Kajinami (1):
Expose available AMD SEV models in domain capabilities
Changes since v1:
* Fixed one code path where available models are not added
* Fixed missing update of "report" flag
* Updated the documentation to explain the new model field in
; approach is likely needed for SEV-SNP, which shares
the same ASID pool with SEV-ES by default. (though the implementation
is still actively updated by AMD and is not yet merged into kernel or
qemu now).
On 2/19/24 18:58, Daniel P. Berrangé wrote:
On Mon, Feb 19, 2024 at 02:54:59PM +0900, Takash
Please ignore the current patch set. During further testing I noticed that
further changes are needed to actually get the source flags set. I'll propose
a fixed versions later.
Sorry for the noise.
On 2/19/24 14:54, Takashi Kajinami wrote:
This introduces the new "model" field
This introduces the new "model" field in sev elements so that clients can
check whether SEV-ES, the 2nd generation of AMD SEV, is available in
the taget hyprvisor.
Takashi Kajinami (1):
Expose available AMD SEV models in domain capabilities
src/conf/domain_capabilities.c | 2 +
This introduces the new "model" field in sev elements, returned by
domain capabilities API, so that client can ensure SEV-ES is available
in this hypervisor.
Signed-off-by: Takashi Kajinami
---
src/conf/domain_capabilities.c | 2 +
src/conf/domain_capabilities.h | 1 +
src/conf/dom
