Bug 1689195 - RFE: report limit on number of SEV guests in domain capabilities XML
Summary: RFE: report limit on number of SEV guests in domain capabilities XML
Keywords:
Status: CLOSED DUPLICATE of bug 1689202
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: libvirt
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.1
Assignee: Pavel Hrdina
QA Contact: Luyao Huang
URL:
Whiteboard:
Depends On: 1689202
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-15 12:01 UTC by Daniel Berrangé
Modified: 2020-10-15 12:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-15 12:55:12 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Daniel Berrangé 2019-03-15 12:01:07 UTC
Description of problem:
It was said that when using SEV, there is a limit of 15 guests that are able to use the feature concurrently.

https://www.redhat.com/archives/libvir-list/2019-January/msg00652.html

This kind of limit is important for a mgmt application to know about, so that it can place VMs on hosts which have suitable resource available, but this is not yet exposed anywhere.

It needs to be reported in the libvirt capabilities XML. Probably we would get this information from QEMU via QMP when querying SEV support.

Version-Release number of selected component (if applicable):
libvirt-5.0.0-6.el8

How reproducible:
Always

Steps to Reproduce:
1. Run  'virsh domcapabilities kvm'

Actual results:
SEV feature is reported, but with no mention of the guest limit:

     <domainCapabilities>
          ...
          <features>
            ...
            <sev supported='yes'/>
              ...
            </sev>
          </features>
        </domainCapabilities>

Expected results:
Above XML includes the guest limit

Comment 1 Jaroslav Suchanek 2020-10-15 12:55:12 UTC
Can be done as part of bug 1689202.

*** This bug has been marked as a duplicate of bug 1689202 ***


Note You need to log in before you can comment on or make changes to this bug.