GPU-remoting latency aware virtual machine migration

A non-transitory computer-readable medium, comprising executable instructions, wherein the instructions, when executed by at least one processor, cause at least one computing device to at least:

• monitor resources of a plurality of hosts of a datacenter cluster;
• identify a host executing a plurality of virtual machines (VM) including a plurality of non-GPU-workload-based virtual machines and a graphics processing unit (GPU)-remoting client virtual machine (VM), the GPU-remoting client VM comprising a GPU workload;
• determine that the GPU-remoting client VM is to be migrated in response to an identification that:
• the GPU-remoting client VM is currently co-located with a GPU remoting server VM, resource utilization of the host is greater than a threshold utilization, and the host lacks migratable non-GPU-remoting virtual machines, wherein the host is identified to lack migratable non-GPU-remoting virtual machines in an instance in which a respective one of the plurality of non-GPU-workload-based virtual machines executed by the host comprise at least one affinity rule with the host or a VM executed using the host;
• determine GPU-remoting latencies for at least a subset of the plurality of hosts, a respective GPU-remoting latency corresponding to a host-to-host network latency between:
• a particular host executing the GPU remoting server VM, and a respective host of the at least the subset of the plurality of hosts, wherein the GPU remoting server VM enables access to a GPU resource using compute unified device architecture call execution;
• identify, based on the monitored resources, a destination host comprising a lower GPU-remoting latency than the host;
• and
• migrate the GPU-remoting client VM from the host to the destination host based on the destination host comprising the lower GPU-remoting latency than the host.

A method performed by instructions executed by at least one processor, the method comprising:

• monitoring resources of a plurality of hosts of a datacenter cluster;
• identifying a host executing a plurality of virtual machines (VM) including a plurality of non-GPU-workload-based virtual machines and a graphics processing unit (GPU)-remoting client virtual machine (VM), the GPU-remoting client VM comprising a GPU workload;
• determining that the GPU-remoting client VM is to be migrated in response to an identification that:
• the GPU-remoting client VM is currently co-located with a GPU remoting server VM, resource utilization of the host is greater than a threshold utilization, and the host lacks migratable non-GPU-remoting virtual machines, wherein the host is identified to lack migratable non-GPU-remoting virtual machines in an instance in which a respective one of the plurality of non-GPU-workload-based virtual machines executed by the host comprise at least one affinity rule with the host or a VM executed using the host;
• determining GPU-remoting latencies for at least a subset of the plurality of hosts, a respective GPU-remoting latency corresponding to a host-to-host network latency between:
• a particular host executing the GPU remoting server VM, and a respective host of the at least the subset of the plurality of hosts, wherein the GPU remoting server VM enables access to a GPU resource using compute unified device architecture call execution;
• identifying, based on the monitored resources, a destination host comprising a lower GPU-remoting latency than the host;
• and
• migrating the GPU-remoting client VM from the host to the destination host based on the destination host comprising the lower GPU-remoting latency than the host.