Copyless numa balancing hypervisor memory migration

A host computing system, the system comprising:

• at least one processor;
• and
• at least one memory storing instructions that, when executed by the at least one processor, are effective to program the at least one processor to:
• run an at least one virtual machine on the host computing system, wherein virtual memory nodes (vNodes) of the at least one virtual machine are pinned to corresponding memory nodes (nodes) on the host computing system,
• run a hypervisor, on the host computing system, the hypervisor able to interface between the host computing system and the at least one virtual machine, and wherein the hypervisor may control functions of the at least one virtual machine;
• export, via the hypervisor, one or more data objects, from the host computing system to the at least one virtual machine, wherein the data objects include references to pages that have been migrated from a physical source memory node (source node) on the host machine to a new source location on the host computing system;
• inspect, the data objects, by the at least one virtual machine;
• detect, by the at least one virtual machine, the pages that have been migrated to the new source location;
• send a request, by the at least one virtual machine, to the host computing system via the hypervisor, to undertake at least one data migration operation;
• and
• undertake the at least one data migration operation.

A non-transitory computer-readable storage medium having embodied thereon a program, the program being executable by a processor to perform a method comprising:

• exporting one or more data objects, from a host machine to at least one virtual machine, via a hypervisor, wherein the data objects include references to pages that have been migrated from a physical source memory node (source node) on the host machine to a new source location on the host machine;
• inspecting, the data objects, by the at least one virtual machine;
• detecting, by the at least one virtual machine, the pages that have been migrated to the new source location;
• sending a request, by the at least one virtual machine, to the host machine via the hypervisor, to undertake;
• and
• undertaking the at least one efficient data migration operation, wherein the at least one efficient data migration operation comprises one or more of:
• mapping the pages to a physical destination memory node (destination node) corresponding to a desired virtual destination memory node (destination vNode), removing mapping of the pages from the source node to the destination node, mapping, via the hypervisor, the new source location to the destination node, wherein the mapping allows data to be migrated from the new source location instead of from the source node, migrating the data from the new source location to the destination node, mapping the destination node to the destination vNode, wherein the destination node contains the pages, and migrating data from the new source location to the destination node prior to any implementation of mapping operations between the new source location and the destination node.