Hyper-V also provides the same types of CPU resource allocation methods. As with Microsoft Virtual Server, these settings are defined per-server. There’s a slight difference, though, if you’re using multiple virtual CPUs (which MSVS did not support). You can access the CPU settings in the properties of a VM, and the settings can be changed while the VM is running (very useful for troubleshooting and quickly resolving issues with “stuck” VMs). Weight-based resource allocation allows you to use a single set of relative numbers for deciding which VMs should have priority when processing limits are reached on the host server. Reserved levels are “hard limits” on the least and most amount of overall CPU power a specific VM can use. You can use both methods at the same time, but it’s important to verify that you’re not leaving potential CPU power untapped.

Hyper-V also provides the same types of CPU resource allocation methods. As with Microsoft Virtual Server, these settings are defined per-server. There’s a slight difference, though, if you’re using multiple virtual CPUs (which MSVS did not support). You can access the CPU settings in the properties of a VM, and the settings can be changed while the VM is running (very useful for troubleshooting and quickly resolving issues with “stuck” VMs). Weight-based resource allocation allows you to use a single set of relative numbers for deciding which VMs should have priority when processing limits are reached on the host server. Reserved levels are “hard limits” on the least and most amount of overall CPU power a specific VM can use. You can use both methods at the same time, but it’s important to verify that you’re not leaving potential CPU power untapped.