Bug 1559832 - [RFE] Fine-grained API to validate if a given CPU model and flags are supported by QEMU / KVM
Summary: [RFE] Fine-grained API to validate if a given CPU model and flags are support...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jiri Denemark
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1559835
TreeView+ depends on / blocked
 
Reported: 2018-03-23 11:36 UTC by Kashyap Chamarthy
Modified: 2019-03-22 11:46 UTC (History)
3 users (show)

Fixed In Version: libvirt-4.4.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1559835 (view as bug list)
Environment:
Last Closed: 2018-05-29 07:02:01 UTC
Embargoed:

Attachments (Terms of Use)

Description Kashyap Chamarthy 2018-03-23 11:36:50 UTC 
There is no existing way (near as I know) way to validate if a given libvirt CPU model and a set of extra CPU flags (e.g. IvyBridge with 'pcid' and 'pdpe1gb') are supported by KVM and a given specific QEMU binary.

This is an RFC requesting to add such an API.


Additional info:
----------------

However, what does exist today is a way to check if a given CPU + extra CPU feature flags are supported by the *host* CPU via the libvirt API virConnectCompareCPU().
Comment 1 Jiri Denemark 2018-05-16 09:50:45 UTC 
Patches sent upstream for review: https://www.redhat.com/archives/libvir-list/2018-May/msg01204.html
Comment 2 Jiri Denemark 2018-05-28 14:33:14 UTC 
This API is now implemented upstream by a series of patches ending with

commit 75e7ab1ef5f391252685f7a7a0da324f6e2a2ebd
Refs: 4.3.0-356-g75e7ab1ef5
Author:     Jiri Denemark <jdenemar>
AuthorDate: Wed May 16 10:05:57 2018 +0200
Commit:     Jiri Denemark <jdenemar>
CommitDate: Mon May 28 16:00:20 2018 +0200

    news: Mention new CPU related APIs

    Signed-off-by: Jiri Denemark <jdenemar>
    Reviewed-by: Ján Tomko <jtomko>
Note You need to log in before you can comment on or make changes to this bug.