libvirt also assumes that the set of features on each model is always the same on all machine-types, which is not true.īenefits of changing: cpu_map.xml and QEMU won't need to match exactly, anymore. Requirement: libvirt uses the predefined CPU models from QEMU, but it needs to be able to query for CPU model details, to find out how it can create a VM that matches what was requested by the user.Ĭurrent problem: libvirt has a copy of the CPU model definitions on its cpu_map.xml file, and the copy can be out of sync in case CPU models in QEMU change. Would be interesting to get rid of the requirement for a live QEMU process to be started, just to list CPU models? Unanswered question: we may have separated subclasses for KVM and TCG CPU models. Requirements: CPU class/model list should not depend on any other command-line option (e.g. Example: Caveat: the CPU class name for -cpu model will in the format model- arch-cpu or model-kvm- arch-cpu. Limitation: needs a live QEMU process for the query. Proposed solution (TODO): use QMP qom-list-types command.ĭependency: X86CPU subclasses. See "Getting information about CPU models" section. Limitation: it can only list CPU model names and nothing else. ![]() Requirement: libvirt needs to know which CPU models are available to be used with the "-cpu" option.Ĭurrent solution: libvirt uses QMP query-cpu-definitions command. See Also: Disabling features that were always disabled on KVM Listing CPU models New solution in 1.5: check if "filtered-features" property on CPU object is all zeroes. Workaround: See "querying for host capabilities" below. Limitation: no proper machine-friendly interface to report which features are missing. Old solution: use the "enforce" flag on the "-cpu" option. Requirement: libvirt needs to ensure all features required on the command-line are present and exposed to the guest.Ĭurrent problem: libvirt doesn't use the "enforce" flag so it can't guarantee that a given feature will be actually exposed to the guest. Interfaces/requirements for libvirt Ensuring predictable set of guest features
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |