Il 18/07/2014 15:06, Riccardo Brunetti ha scritto: > > > 1) Assign vCPUs so that vCPU(VM1) + vCPU(VM2) = total number of physical > cores (12) (both VMs have < 12 vCPUs) (ie. 8+4) > 2) Assign vCPUs so that vCPU(VM1) + vCPU(VM2) > total number of physical > cores (12) (both VMs have <= 12 vCPUs) (ie. 12+8) > 3) Assign vCPUs so that vCPU(VM1) + vCPU(VM2) > total number of physical > cores (12) (one VM has > 12 vCPUs) (ie. 16+8) > 4) Assign vCPUs so that vCPU(VM1) + vCPU(VM2) > total number of physical > cores (12) (both VMs have > 12 vCPUs) (ie. 16+16) The last two are usually bad ideas. The first two should be okay. Overcommitting works best if the VM are I/O bound (disk or network). If you're overcommitting, hyperthreading should in general be enabled. Answers for very specific scenarios are hard to give though, so you should also benchmark your deployment with realistic workloads. Paolo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
