New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the ability to configure the CPU model exposed to KVM virtual machines. #756
Comments
Original Redmine Comment Thanks for the patch! :) Scheduling this 4.8 |
Original Redmine Comment Is it working now in OpenNebula 4.12? I tried to add
/etc/one/vmm_exec_kvm.conf
|
Original Redmine Comment Have found solution for CPU host-passthrough. If need to to expose the underlying physical CPU to the virtual machine. To do this, you need to modify your VM’s template to include the following raw attributes:
You can add these attributes by following these steps:
|
- new kvm monitor probe to gather model and machine types from hosts - generate cpu element in deployment file
* F #756: Add support for CPU_MODEL. - new kvm monitor probe to gather model and machine types from hosts - generate cpu element in deployment file * F #756: Added machine-models to install.sh * F #756: Rename 'OS Booting' to 'OS & CPU' * F #756: Rename 'libvirt machine' to 'machine type' * F #756: Change 'machine type' to a drop-down * F #756: KVM IM machines probe prioritize kvm/kqemu/qemu domain types * F #756: Added CPU Model section
* F #756: Add support for CPU_MODEL. - new kvm monitor probe to gather model and machine types from hosts - generate cpu element in deployment file * F #756: Added machine-models to install.sh * F #756: Rename 'OS Booting' to 'OS & CPU' * F #756: Rename 'libvirt machine' to 'machine type' * F #756: Change 'machine type' to a drop-down * F #756: KVM IM machines probe prioritize kvm/kqemu/qemu domain types * F #756: Added CPU Model section
Author Name: Vladislav Gorbunov (Vladislav Gorbunov)
Original Redmine Issue: 2869, https://dev.opennebula.org/issues/2869
Original Date: 2014-05-06
One of the most important missing features was the ability to configure the CPU model exposed to KVM virtual machines. There are a couple of reasons for wanting to specify the CPU model
In libvirt, the CPU is specified by providing a base CPU model name (which is a shorthand for a set of feature flags), a set of additional feature flags, and the topology (sockets/cores/threads). The libvirt KVM driver provides a number of standard CPU model names (defined in /usr/share/libvirt/cpu_map.xml):
"486", "pentium", "pentium2", "pentiumpro", "coreduo", "n270", "pentiumpro", "qemu32", "kvm32", "cpu64-rhel5", "cpu64-rhel5", "kvm64", "pentiumpro", "Conroe" "Penryn", "Nehalem", "Westmere", "pentiumpro", "cpu64-rhel5", "cpu64-rhel5", "Opteron_G1", "Opteron_G2", "Opteron_G3, "Opteron_G4"
It is also possible to request the host CPU model in two ways
This path is add CPUMODEL support:
OS = [ CPUMODEL="host" ] for host-passthrough
or for example
OS = [ CPUMODEL="core2duo" ] for custom CPU model. Full list of supported cpu shown by the command:
kvm -cpu ?
The text was updated successfully, but these errors were encountered: