[pve-devel] adding a vm workload scheduler feature

Martin Waschbüsch service at waschbuesch.it
Tue Nov 17 14:56:39 CET 2015

> Am 17.11.2015 um 14:20 schrieb Alexandre DERUMIER <aderumier at odiso.com>:
>>> Unless all cluster nodes have identical hardware, how do you determine if a given node is a suitable target for a vm?
> I think we could add a manual "host cpu weight" option, because it's difficult to compare cpus performance. (frequencies/nb cores/intel|amd).

Good point. Though, I was more thinking about situations where the cpu-type is not set to default (kvm64, I think?) but to something like 'IvyBridge' or Opteron_G5. (The primary use I had for using non-default cpu types was to expose features such as AES-NI to a vm.)

Another thing that just occurred to me: Backup schedules and settings are not necessarily the same for each node, which means auto-migration could lead to double, or (worse!) no backup for a vm that was moved around?

Dunno if these are just corner cases?


More information about the pve-devel mailing list