Wiki

User Tools

Site Tools

Trace:
kvm:set_cpu_shares_for_live_running_instance_permanently

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
kvm:set_cpu_shares_for_live_running_instance_permanently [2020/08/19 11:51] – 192.168.1.1kvm:set_cpu_shares_for_live_running_instance_permanently [2020/08/19 12:01] (current) – 192.168.1.1
Line 1: Line 1:
-====== KVM - Set CPU Shares For Live Running Instance Permanently ======+====== KVM - Set CPU Shares for Live Running Instance Permanently ======
  
 <code bash> <code bash>
Line 15: Line 15:
 **NOTE:**  KVM represents each virtual CPU as a thread in the host Linux system, actually as a thread in the QEMU process. **NOTE:**  KVM represents each virtual CPU as a thread in the host Linux system, actually as a thread in the QEMU process.
  
-On Linux, you can use **taskset** to force specific threads onto specific CPUs.  So that will let you assign one VCPU to one physical CPU and two VCPUs to another. See, for example, https://groups.google.com/forum/#!topic/linuxkernelnewbies/qs5IiIA4xnw.+On Linux, you can use **taskset** to force specific threads onto specific CPUs.  So that will let you assign one VCPU to one physical CPU and two VCPUs to another.
  
  
  
-A virtual CPU equates to 1 physical core, but when your VM attempts to process something, it can potentially run on any of the cores that happen to be available at that moment. The scheduler handles this, and the VM is not aware of it. You can assign multiple vCPUs to a VM which allows it to run concurrently across several cores.+A virtual CPU equates to 1 physical core, but when your VM attempts to process something, it can potentially run on any of the actual cores that happen to be available at that moment. The scheduler handles this, and the VM is not aware of it. You can assign multiple vCPUs to a VM which allows it to run concurrently across several cores.
  
 Cores are shared between all VMs as needed, so you could have a 4-core system, and 10 VMs running on it with 2 vCPUs assigned to each. VMs share all the cores in your system quite efficiently as determined by the scheduler. This is one of the main benefits of virtualization - making the most use of under-subscribed resources to power multiple OS instances. Cores are shared between all VMs as needed, so you could have a 4-core system, and 10 VMs running on it with 2 vCPUs assigned to each. VMs share all the cores in your system quite efficiently as determined by the scheduler. This is one of the main benefits of virtualization - making the most use of under-subscribed resources to power multiple OS instances.
Line 46: Line 46:
  
 Let’s look at both options for manipulating your kvm virtual machines processes. Let’s look at both options for manipulating your kvm virtual machines processes.
 +
 +----
  
 ==== Start a VM with specific CPU affinity ==== ==== Start a VM with specific CPU affinity ====
Line 148: Line 150:
  
 ===== References ===== ===== References =====
 +
 +[[http://www.linux-kvm.com/content/virsh-kvm-cpu-affinity-problems|virsh kvm CPU affinity problems]]
 +
 +[[http://www.linux-kvm.com/content/some-new-kvm-options-boot-order-and-process-name|Some new kvm options: boot order and process name]]
  
 https://stackoverflow.com/questions/47621257/kvm-cpu-share-priority-overselling https://stackoverflow.com/questions/47621257/kvm-cpu-share-priority-overselling
kvm/set_cpu_shares_for_live_running_instance_permanently.1597837875.txt.gz · Last modified: 2020/08/19 11:51 by 192.168.1.1
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki