You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
We gather KVM_MACHINES and KVM_CPU_MODELS to get supported (virtual) hardware specifications by the libvirt/QEMU. Regarding the KVM_CPU_MODELS, it's just a list of all available models, not the ones which can actually run on the machines.
It might be good to get also the actual hardware CPU model, which is closest to one of the available libvirt/QEMU CPU models:
Description
We gather
KVM_MACHINES
andKVM_CPU_MODELS
to get supported (virtual) hardware specifications by the libvirt/QEMU. Regarding theKVM_CPU_MODELS
, it's just a list of all available models, not the ones which can actually run on the machines.It might be good to get also the actual hardware CPU model, which is closest to one of the available libvirt/QEMU CPU models:
the item is under
CAPABILITIES/HOST/CPU/MODEL
path.Proposed parameter could be
KVM_CPU_MODEL
(without trailings
).The extended machine models monitoring would look like:
Use case
Better insight into what CPU model to choose (when not using the host passthrough).
Additional Context
Reference support ticket:
https://opennebula.zendesk.com/agent/tickets/11889
Progress Status
__
The text was updated successfully, but these errors were encountered: