Back on this for a bit.
After some abstraction levels the probing is in libvirt around:
virQEMUDriverGetDomainCapabilities
-> virQEMUCapsFillDomainCaps
...
-> virQEMUCapsGetCPUModels
...
-> virQEMUCapsGetAccel(qemuCaps, type)->cpuModels
That is of the kvm struct that represents qemu-kvm
The struct contains mostly what we see in domcaps:
1106 struct _qemuMonitorCPUDefInfo {
1107 virDomainCapsCPUUsable usable;
1108 char *name;
1109 char *type;
1110 char **blockers; /* NULL-terminated string list */
1111 };
This is filled formerly by:
virQEMUCapsFetchCPUModels
-> virQEMUCapsFetchCPUDefinitions
-> qemuMonitorGetCPUDefinitions - pokes qemu monitor to get info
-> virQEMUCapsCPUDefsToModels - adds probed models to structure
And that uses the common QMP query-cpu-definitions
So libvirt reports what qemu tells it ... oh I get a feeling I actually know
this case ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861643
Title:
libvirt CPU model selection missing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
