By: rwessel (rwessel.delete@this.yahoo.com), May 24, 2022 7:40 am
Room: Moderated Discussions
Christian Bornträger (borntraeger.delete@this.linux.ibm.com) on May 24, 2022 8:06 am wrote:
> Even the s390 case is not a counter-example. What rwessel described was mostly cpu baselining
> done by the z/VM hypervisor. In essence make sure that after life migration things still
> work. This is pretty much the same as cpu-baselining in openstack/kvm.
It's not just across (potential) VM migration targets, but across machines in a Sysplex (cluster) as well (where migration can happen on a process level). The latter tending to be much larger configurations. Of course on Z, LPARS (partitions), VM, and Sysplex (clustering) are all joined at the hip.
> Even the s390 case is not a counter-example. What rwessel described was mostly cpu baselining
> done by the z/VM hypervisor. In essence make sure that after life migration things still
> work. This is pretty much the same as cpu-baselining in openstack/kvm.
It's not just across (potential) VM migration targets, but across machines in a Sysplex (cluster) as well (where migration can happen on a process level). The latter tending to be much larger configurations. Of course on Z, LPARS (partitions), VM, and Sysplex (clustering) are all joined at the hip.
