From 95ef9ceea44d3672e0adc644839bd7422a3e0b8b Mon Sep 17 00:00:00 2001 From: Jiri Denemark Date: Fri, 11 May 2018 16:24:44 +0200 Subject: [PATCH] Improve documentation of virConnectGetCPUModelNames MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Jiri Denemark Reviewed-by: Collin Walling Reviewed-by: Kashyap Chamarthy Reviewed-by: Ján Tomko --- src/libvirt-host.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/libvirt-host.c b/src/libvirt-host.c index 76087badd8..9cd7fa4425 100644 --- a/src/libvirt-host.c +++ b/src/libvirt-host.c @@ -1003,7 +1003,13 @@ virConnectCompareCPU(virConnectPtr conn, * NULL if only the list length is needed. * @flags: extra flags; not used yet, so callers should always pass 0. * - * Get the list of supported CPU models for a specific architecture. + * Get the list of CPU models supported by libvirt for a specific architecture. + * + * The returned list limits CPU models usable with libvirt (empty list means + * there's no limit imposed by libvirt) and it does not reflect capabilities of + * any particular hypervisor. See the XML returned by + * virConnectGetDomainCapabilities() for a list of CPU models supported by + * libvirt for domains created on a specific hypervisor. * * Returns -1 on error, number of elements in @models on success (0 means * libvirt accepts any CPU model).