Object processing method and system

Abstract

The embodiments of the present specification provide an object processing method and system, wherein the object processing method is applied to an object processing system, wherein the system includes a virtual machine management module and an object management module in a host machine, wherein the virtual machine management module sends an object deletion instruction to the object management module according to a virtual machine migration recovery task; the object management module deletes at least two initial objects corresponding to the virtual machine migration recovery task by executing the object deletion instruction, wherein the at least two initial objects are obtained by splitting a target object corresponding to the virtual machine; and upon receiving an object recovery request for the target object, the target object is restored according to historical record data corresponding to the target object.

Description

Technical Field

[0001] The embodiments of the present specification relate to the field of computer technology, and in particular to an object processing method. Background Art

[0002] With the continuous development of computer technology and virtualization technology, virtual machines can be virtualized on host machines. Virtual machines running on host machines may need to be hot migrated from the source host machine to the destination host machine. During the hot migration process, hot migration may sometimes time out or be canceled due to other reasons. In order to ensure the normal operation of the virtual machine, it is necessary to roll back the hot migration of the virtual machine at the source end.

[0003] During the hot migration process, in order to reduce the amount of data to be transmitted, the 2M page table entries created by the virtual machine will be split into multiple 4K page table entries for transmission. However, in the event of a hot migration rollback, multiple 4K page table entries will remain on the source side, causing the virtual machine's performance to degrade, resulting in reduced operating efficiency of the virtual machine. Summary of the invention

[0004] In view of this, an embodiment of this specification provides an object processing method. One or more embodiments of this specification also relate to an object processing system, a computing device, a computer-readable storage medium, and a computer program to solve the technical defects existing in the prior art.

[0005] According to a first aspect of an embodiment of this specification, there is provided an object processing method, which is applied to an object processing system, wherein the system includes a virtual machine management module and an object management module in a host machine, wherein:

[0006] The virtual machine management module sends an object deletion instruction to the object management module according to the virtual machine migration and recovery task;

[0007] The object management module deletes at least two initial objects corresponding to the virtual machine migration and recovery task by executing the object deletion instruction, wherein the at least two initial objects are obtained by segmenting the target object corresponding to the virtual machine; and

[0008] When an object recovery request for the target object is received, the target object is recovered according to the historical record data corresponding to the target object.

[0009] According to a second aspect of the embodiments of this specification, an object processing system is provided, including a virtual machine management module and an object management module in a host machine, wherein:

[0010] The virtual machine management module is configured to send an object deletion instruction to the object management module according to the virtual machine migration recovery task;

[0011] The object management module is configured to delete at least two initial objects corresponding to the virtual machine migration and recovery task by executing the object deletion instruction, wherein the at least two initial objects are obtained by segmenting the target object corresponding to the virtual machine; and

[0012] When an object recovery request for the target object is received, the target object is recovered according to the historical record data corresponding to the target object.

[0013] According to a third aspect of an embodiment of this specification, a computing device is provided, including:

[0014] Memory and processor;

[0015] The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the object processing method are implemented.

[0016] According to a fourth aspect of the embodiments of this specification, a computer-readable storage medium is provided, which stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the steps of the object processing method are implemented.

[0017] According to a fifth aspect of the embodiments of this specification, a computer program is provided, wherein when the computer program is executed in a computer, the computer is caused to execute the steps of the object processing method.

[0018] The object processing method provided in this specification comprises a system including a virtual machine management module and an object management module in a host machine, wherein the virtual machine management module sends an object deletion instruction to the object management module according to a virtual machine migration and recovery task; the object management module deletes at least two initial objects corresponding to the virtual machine migration and recovery task by executing the object deletion instruction, wherein the at least two initial objects are obtained by segmenting a target object corresponding to the virtual machine; and upon receiving an object recovery request for the target object, the target object is restored according to historical record data corresponding to the target object.

[0019] Specifically, the object processing method deletes at least two initial objects corresponding to the virtual machine migration and recovery task by the object management module upon receiving an object deletion instruction sent by the virtual machine management module, thereby avoiding the impact of the remaining initial objects on the performance of the virtual machine, and avoiding the problem of the virtual machine performance being reduced due to the two initial objects, resulting in reduced operating efficiency of the virtual machine. At the same time, upon receiving an object recovery request for the target object, the target object is recovered, thereby ensuring the normal operation of the virtual machine. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 This is a schematic diagram of an application scenario of an object processing method provided by an embodiment of this specification;

[0021] Figure 2 is a flow chart of an object processing method provided by an embodiment of this specification;

[0022] Figure 3 is a processing flow chart of an object processing method provided by an embodiment of this specification;

[0023] Figure 4 is a schematic diagram of the structure of an object processing system provided by an embodiment of this specification;

[0024] Figure 5 It is a structural block diagram of a computing device provided by an embodiment of this specification. DETAILED DESCRIPTION

[0025] Many specific details are described in the following description to facilitate a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of this specification, so this specification is not limited to the specific implementation disclosed below.

[0026] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0027] It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0028] First, the terms involved in one or more embodiments of this specification are explained.

[0029] Virtual machine hot migration: Virtual machine hot migration refers to the process of migrating a virtual machine from a host machine A to a physical node B while ensuring that the service is not interrupted. Virtual machine hot migration involves virtual machine configuration synchronization, memory copying, device status synchronization, etc.

[0030] Migration rollback: The user cancels hot migration through the console or command, so that the VM remains running on the source side, while the pausedVM (the virtual machine that stops migrating) on ​​the destination side is destroyed.

[0031] qemu: An open source virtualization simulator and virtual machine monitor that can simulate and manage virtual machines on the host machine.

[0032] KVM (Kernel Virtual Machine): is a kernel driver module of Linux, which can make the Linux host a Hypervisor (virtual machine monitor).

[0033] KVM-kmod: It is the kernel module part of KVM VMM, which is reflected as a driver module in the kernel and is mainly responsible for processing the "sensitive instructions" of the virtual machine. In actual applications, kvm is divided into two parts: qemu-kvm and kvm-kmod. Among them, qemu-kvm is the user space part of kvm, which can be regarded as a qemu virtualization simulator, which creates and starts virtual machines by using ioctl system calls. kvm-kmod is the kernel module part of kvmVMM, which is reflected as a driver module in the kernel.

[0034] Linux: An operating system.

[0035] With the continuous development of computer technology and virtualization technology, virtual machines can be virtualized on host machines, and virtual machines running on host machines may need to be hot migrated from the source host machine to the destination host machine. During the hot migration process, sometimes the hot migration timeout or other reasons will cause the migration to be cancelled. In this case, when the hot migration is initiated, in order to reduce the transmission data, the 2M page table entries when the VM is created will be broken up and divided into multiple 4K page table entries for dirty marking. If the hot migration of the virtual machine is successful, the VM (virtual machine) of the source host machine will be destroyed, and the destination host machine will create a new VM with 2M large pages. However, if the migration rolls back, multiple 4k page table entries will remain on the source side, which will cause the VM performance to deteriorate (that is, the memory latency will increase).

[0036] Based on this, in this specification, an object processing method is provided. This specification also involves an object processing system, a computing device, a computer-readable storage medium and a computer program, which are described in detail one by one in the following embodiments.

[0037] Figure 1 A schematic diagram of an application scenario of an object processing method provided according to an embodiment of this specification is shown. Figure 1 , where the object can be understood as the page table entry corresponding to the virtual machine, the page table corresponding to the virtual machine, etc., and the virtual machine management module can be understood as a module for managing the virtual machine, for example, the virtual machine management module can be qemu; the object management module can be understood as a module in the host machine for creating the target object; in the case where the object is a page table entry, the object management module can be understood as a module that can manage the page table entry corresponding to the virtual machine, and the object management module can create the page table entry corresponding to the virtual machine, delete the page table entry corresponding to the virtual machine, or split the page table entry, such as KVM-kmod in the host machine kernel. Based on this, after qemu cancels the hot migration and performs the hot migration rollback operation, it monitors the rollback status of the hot migration rollback of the virtual machine; and when it is determined that the virtual machine rollback is completed, KVM-kmod sends an object deletion instruction, wherein the object deletion instruction can be an ioctl command that instructs KVM-kmod to delete multiple 4K page table entries. In actual applications, when hot migration is initiated, in order to reduce the transmission data, the 2M page table entries when the VM is created will be broken up and split into multiple 4K for dirty marking. It should be noted that the page table entries are stored in the page table, and the page table entries are used to record the mapping relationship between the memory pages of the physical machine and the memory pages of the virtual machine. The memory pages of a physical machine can be mapped to the physical pages of one or more virtual machines.

[0038] When the KVM-kmod receives the ioctl command, it determines multiple 4K page table entries of the virtual machine from the physical storage resources of the host machine in response to the ioctl command, and deletes the multiple 4K page table entries. When the virtual machine kernel executes a task sent by the user that requires the use of the page table entry, since the page table entry does not exist, a page fault exception is triggered, thereby realizing the reconstruction of the 2M page table (i.e., 2M large page) through the page fault exception.

[0039] Among them, the method of implementing the reconstruction of the 2M page table due to a page fault exception can be:

[0040] After triggering a page fault exception, the virtual machine kernel can send a page table recovery instruction to the KVM-kmod in the host kernel. After receiving the page table recovery instruction, the KVM-kmod determines the 2M page table corresponding to the virtual machine and recovers the 2M page table based on the historical page table entry record corresponding to the 2M page table. After the 2M page table recovery is completed, a page table recovery completion notification is sent to the virtual machine kernel.

[0041] The virtual machine kernel obtains the restored 2M page table based on the page table recovery completion notification, thereby completing the reconstruction of the 2M page table.

[0042] Based on this, the object processing method provided in this specification is a method for improving the performance of a virtual machine after hot migration rollback. In the actual hot migration rollback process, it can be learned from the measured data that the memory latency of the virtual machine has changed from 90ns before the migration to about 110ns, and the performance has dropped by about 25%; based on this, the method for improving the performance of a virtual machine after hot migration rollback provided in this specification, for the hot migration rollback scenario, releases the 4k page table entries broken up by the hot migration, so that when the vm is missing a page again, it will rebuild the 2M large page, so that the memory latency of the virtual machine will not fluctuate too much, and will be basically the same as the memory latency before the hot migration, thereby ensuring the normal operation of the virtual machine and avoiding the problem of not reducing the memory latency of the virtual machine after the hot migration rollback.

[0043] Figure 2 A flowchart of an object processing method provided according to an embodiment of the present specification is shown. The object processing method is applied to an object processing system, wherein the system includes a virtual machine management module, a virtual machine kernel, and an object management module in a host machine, and specifically includes the following steps.

[0044] Step 202: The virtual machine management module sends an object deletion instruction to the object management module according to the virtual machine migration and recovery task.

[0045] Among them, the virtual machine migration recovery task can be understood as a task created to restore the virtual machine on the source host after the virtual machine hot migration fails. In actual applications, the hot migration rollback operation can be performed on the virtual machine based on the virtual machine migration recovery task.

[0046] The object deletion instruction may be understood as an instruction to instruct the object management module to delete at least two initial objects. For example, the object deletion instruction may be an ioctl command to instruct the object management module to delete multiple 4K page table entries.

[0047] Specifically, the virtual machine management module can send an object deletion instruction to the object management module according to a virtual machine migration recovery task created to restore the virtual machine on the source host machine after the virtual machine hot migration fails.

[0048] The following takes the application of the object migration method in the scenario of rebuilding the virtual machine page table entry as an example, and further explains the virtual machine management module, according to the virtual machine migration recovery task, sending the object deletion instruction to the object management module. Among them, the virtual machine management module is qemu, and the object management module is KVM-kmod in the host kernel. Based on this, the qemu can send an ioctl command to KVM-kmod based on the virtual machine hot migration recovery task, and instruct KVM-kmod to delete multiple 4K page table entries based on the ioctl command.

[0049] Furthermore, in an embodiment provided in the specification, the virtual machine management module can monitor the execution status of the virtual machine migration and recovery task, and when it is determined that the virtual machine migration and recovery task is completed, that is, the virtual machine rollback is completed, an object deletion instruction is sent to the object management module, thereby ensuring that the page table entry corresponding to the virtual machine can be deleted in time to avoid the problem of virtual machine performance degradation. The specific implementation method is as follows.

[0050] The virtual machine management module sends an object deletion instruction to the object management module according to the virtual machine migration recovery task, including:

[0051] The virtual machine management module monitors the current execution status information of the virtual machine migration recovery task, wherein the virtual machine migration recovery task is a task created when the virtual machine migration fails;

[0052] When it is determined that the virtual machine migration and recovery task is completed according to the current execution state information, an object deletion instruction is sent to the object management module.

[0053] The current execution state information may be understood as information representing the current execution state of the virtual machine migration recovery task, or may be understood as information representing the state of the hot migration rollback of the virtual machine.

[0054] Specifically, the virtual machine management module can monitor the current execution status information of the virtual machine migration recovery task. It should be noted that the virtual machine migration recovery task is a task created for the virtual machine that performs hot migration when the virtual machine hot migration fails. After obtaining the current execution status information, the virtual machine management module can determine whether the virtual machine migration recovery task has been completed based on the current execution status information. If so, it means that the virtual machine migration recovery task has been completed, and when the virtual machine migration recovery task has been completed, an object deletion instruction is sent to the object management module. If not, the current execution status information of the virtual machine migration recovery task continues to be monitored.

[0055] Step 204: the object management module deletes at least two initial objects corresponding to the virtual machine migration and recovery task by executing the object deletion instruction, wherein the at least two initial objects are obtained by segmenting the target object corresponding to the virtual machine; and

[0056] When a target object recovery request for the target object is received, the target object is recovered according to the historical record data corresponding to the target object.

[0057] Wherein, in the case where the object is a page table entry, the target object can be understood as a page table entry set for the virtual machine during the creation process. The size of the page table entry can be set according to the actual application scenario, and this specification does not impose specific restrictions on this. For example, the page table entry can be a 2M page table entry, or a page table entry larger than 2M. In actual applications, in order to improve the performance of the virtual machine, a large page is generally used for paging for a virtual machine using a memory paging method, such as a 2M BYTES memory paging method.

[0058] Correspondingly, the multiple initial objects can be understood as objects obtained by segmenting the target object. In the case where the target object is a 2M page table entry, the initial object can be understood as multiple page table entries obtained by segmenting the 2M page table entry, wherein the initial object is smaller than the target object.

[0059] In actual applications, since virtual machines generally use large pages when paging, for example, 2M BYTES memory paging, the bandwidth consumption of virtual machine hot migration increases, making virtual machine hot migration more difficult. Therefore, in order to reduce bandwidth consumption, the original 2M large page will be broken up and split into multiple page tables smaller than 2M before hot migration. For example, 4K page table.

[0060] The historical record data corresponding to the target object can be understood as data that records the address mapping relationship in the page table. In practical applications, the address mapping relationship in the page table can be understood as the mapping relationship between the virtual address of the virtual machine and the physical address of the host machine recorded in the page table. Therefore, the mapping relationship between the virtual address of the virtual machine and the physical address of the host machine can be re-determined based on the historical record data, and the deleted or segmented page table can be rebuilt based on the mapping relationship. Among them, the historical record data is determined based on EPT (Enhanced Page Table) technology.

[0061] The target object recovery request may be understood as a target object reconstruction request; when the target object is a 2M page table entry, the target object recovery request may be understood as a 2M page table reconstruction request.

[0062] Specifically, when the object management module receives an object deletion instruction sent by the virtual machine management module, in response to the instruction, the object management module deletes at least two initial objects corresponding to the virtual machine migration recovery task. Afterwards, when an object recovery request for a target object is received, the target object corresponding to the virtual machine is determined in response to the object recovery request, and the target object is recovered according to the historical record data corresponding to the target object.

[0063] Using the above example, after receiving the ioctl command sent by qemu, KVM-kmod determines multiple 4K page table entries of the virtual machine from the host machine's physical storage resources in response to the ioctl command, and deletes the multiple 4K page table entries. After that, when the virtual machine kernel triggers a page fault exception, it can send a page table recovery instruction to KVM-kmod in the host machine kernel. After receiving the page table recovery instruction, KVM-kmod determines the 2M page table corresponding to the virtual machine, and restores the 2M page table based on the historical page table entry records corresponding to the 2M page table.

[0064] In one embodiment provided in the present specification, the object processing system includes a virtual machine kernel; the virtual machine kernel can be understood as the kernel of the virtual machine after hot migration recovery. In actual applications, when the virtual machine kernel executes a task that requires the participation of page table entries, the page table entries are deleted, thereby triggering a page fault exception, so that KVM-kmod can rebuild the page table entries for it, thereby ensuring the normal operation of the virtual machine; the specific implementation method is as follows.

[0065] The object processing system includes a virtual machine kernel;

[0066] Correspondingly, after the object management module deletes at least two initial objects corresponding to the virtual machine migration recovery task by executing the object deletion instruction, the object management module further includes:

[0067] The virtual machine kernel, when executing an object execution task associated with the target object, sends a target object recovery request to the object management module.

[0068] Among them, the object execution task can be understood as a task that requires the participation of the target object during the execution process, such as a data storage task. In actual applications, the page table records the mapping relationship between the virtual address of the virtual machine and the physical address of the host machine. When the virtual machine performs a data storage task, it needs to store the data in the physical address of the host machine corresponding to the virtual address, so the participation of the page table entry is required.

[0069] Specifically, after the object management module deletes at least two initial objects, when the virtual machine kernel executes the object execution task associated with the target object, since the initial object is deleted, it sends a target object recovery request for the target object to the object management module, so that the object management module rebuilds the target object.

[0070] Furthermore, the virtual machine kernel, when executing an object execution task associated with the target object, sends a target object recovery request to the object management module, including:

[0071] The virtual machine kernel receives an object execution task associated with the target object;

[0072] In case of executing the object execution task, sending a target object recovery request to the virtual machine management module;

[0073] The virtual machine management module sends the received target object recovery request to the object management module.

[0074] Using the above example, after KVM-kmod releases multiple 4K page tables restored during the virtual machine hot migration rollback process based on the ioctl command sent by qemu, the virtual machine kernel can receive data storage tasks that require page table entries, and the virtual machine kernel needs to call page table entries during the execution of the data storage task. Since the page table entry is deleted, the virtual machine kernel cannot obtain the page table entry, so a page fault exception is triggered and a 2M page table reconstruction request is sent to KVM-kmod.

[0075] In the embodiment provided in this specification, the object management module, in response to the object recovery request, recovers the target object according to the historical record data corresponding to the target object, including:

[0076] The object management module determines the target object of the virtual machine and the historical record data corresponding to the target object based on the received target object recovery request;

[0077] Determine the virtual address of the virtual machine and the physical address corresponding to the virtual address based on the historical record data;

[0078] Based on the virtual address and the physical address, a target object corresponding to the virtual machine is created.

[0079] The physical address corresponding to the virtual address can be understood as the physical address corresponding to the virtual address in the host machine.

[0080] Specifically, when the object management module receives a target object recovery request sent by the virtual machine kernel, the object management module determines the target object of the virtual machine and the historical record data corresponding to the target object in response to the target object recovery request; and determines the virtual address of the virtual machine and the physical address corresponding to the virtual address in the host machine based on the historical record data, and recreates the target object corresponding to the virtual machine based on the virtual address and the corresponding physical address, thereby enabling the subsequent virtual machine kernel to execute the object execution task based on the target object, thereby ensuring the normal operation of the virtual machine without reducing the performance of the virtual machine.

[0081] Furthermore, in the embodiment provided in this specification, after the object creation module creates the target object, it can send a recovery completion instruction to the virtual machine kernel, and the virtual machine kernel can obtain the recovered target object based on the instruction. The specific implementation method is as follows.

[0082] After restoring the target object according to the historical record data corresponding to the target object, the method further includes:

[0083] The object management module stores the target object in the object storage module corresponding to the virtual machine, and sends a recovery completion instruction to the virtual machine kernel;

[0084] The virtual machine kernel, upon receiving the recovery completion instruction, loads the target object from the object storage module corresponding to the virtual machine and processes the object execution task according to the target object.

[0085] In actual applications, after completing the recovery of the target object, the object management module will store the target object in the object storage module, and instruct the virtual machine kernel to load the target object from the object storage module through a recovery completion instruction.

[0086] Among them, the object storage module can be understood as a module that stores the target object, for example, the memory management unit (MMU) in the host machine, or the physical storage resources corresponding to the host machine in the virtual machine memory. The physical storage resources can be the host machine memory, or the storage medium deployed on the host machine (such as disk, cache, etc.).

[0087] Using the above example, after KVM-kmod completes the re-creation of the 2M page table, it can store the 2M page table in the memory management module in the host machine. And send a page table reconstruction completion instruction to the virtual machine kernel. After receiving the page table reconstruction completion instruction, the virtual machine kernel can load the 2M page table from the memory management module. This ensures that the performance of the virtual machine does not change after the hot migration is rolled back.

[0088] In the embodiment of this specification, after completing the recovery of the target object, the object management module will send the target object to the virtual machine kernel through a recovery completion instruction. The specific implementation method is as follows.

[0089] After restoring the target object according to the historical record data corresponding to the target object, the method further includes:

[0090] The object management module generates a recovery completion instruction based on the target object, and sends the recovery completion instruction to the virtual machine kernel;

[0091] The object management module, upon receiving the recovery completion instruction, obtains the target object carried in the recovery completion instruction and processes the object execution task according to the target object.

[0092] Using the above example, after KVM-kmod completes the re-creation of the 2M page table, it can send the 2M page table to the virtual machine kernel through the page table reconstruction completion instruction. After receiving the page table reconstruction completion instruction, the virtual machine kernel can obtain the 2M page table from the page table reconstruction completion instruction. In this way, the virtual machine kernel can quickly obtain the 2M page table entry, ensuring that the performance of the virtual machine does not change after the hot migration is rolled back.

[0093] In one embodiment provided in this specification, during the hot migration of a virtual machine, sometimes the hot migration may time out or other reasons may occur, resulting in the cancellation of the migration. Therefore, the hot migration of the virtual machine needs to be rolled back to ensure the normal operation of the virtual machine. The specific implementation method is as follows.

[0094] The virtual machine management module, before sending the object deletion instruction to the object management module according to the virtual machine migration recovery task, further includes:

[0095] The virtual machine management module obtains at least two initial objects corresponding to the virtual machine from the object storage module, and performs virtual machine migration on the virtual machine based on the at least two initial objects;

[0096] In the case where it is determined that the migration of the virtual machine fails, creating a virtual machine migration recovery task corresponding to the virtual machine;

[0097] The virtual machine is migrated and recovered according to the virtual machine migration and recovery task.

[0098] Using the above example, qemu can obtain multiple 4K page tables corresponding to the virtual machine from the physical storage resources corresponding to the virtual machine, and perform hot migration operations on the virtual machine based on the multiple 4K page tables, thereby hot migrating the virtual machine from the source physical machine where it originally resides to the destination physical machine. In addition, during the migration process, qemu can monitor the execution status of the hot migration of the virtual machine. If it is determined that the hot migration operation is canceled due to the user canceling the hot migration through the console or command, the hot migration timeout, or other reasons, it can create a hot migration rollback task for the virtual machine that failed the hot migration, and perform a hot migration rollback operation on the virtual machine on the source host based on the hot migration rollback task.

[0099] In the embodiment provided in this specification, by acquiring at least two initial objects corresponding to a virtual machine, the virtual machine is migrated, thereby avoiding the problem of large bandwidth requirements for hot migration of virtual machines. In addition, when it is determined that the migration of the virtual machine fails, a virtual machine migration recovery task for the corresponding virtual machine is created, and the migration recovery process is performed on the virtual machine, thereby realizing the recovery of the virtual machine and ensuring the normal operation of the virtual machine.

[0100] Furthermore, in the embodiments provided in this specification, in order to avoid the problem of large bandwidth requirements for virtual machine hot migration, the virtual machine kernel can divide the 2M page table entry into multiple 4K page table entries, and the specific implementation method is as follows.

[0101] Before the virtual machine management module obtains at least two initial objects corresponding to the virtual machine from the object storage module, the virtual machine management module further includes:

[0102] The virtual machine management module sends a target object segmentation instruction carrying a preset object size to the object management module;

[0103] The object management module, in response to the target object segmentation instruction, segments the target object corresponding to the virtual machine based on the preset object size to obtain at least two initial objects, and stores the at least two initial objects in the object storage module.

[0104] The target object splitting instruction may be understood as an instruction instructing the object management module to split the target object, for example, an ioctl command sent by qemu to KVM-kmod, instructing the KVM-kmod to split a 2M page table into multiple 4K page tables.

[0105] The preset object size can be understood as the size that the target object needs to be segmented into. For example, the preset object size can be 4K.

[0106] Specifically, before performing hot migration of a virtual machine, the virtual machine management module can send a target object splitting instruction carrying a preset object size to the object management module. After receiving the target object splitting instruction, the object management module responds to the target object splitting instruction and splits the target object corresponding to the virtual machine based on the preset object size to obtain at least two initial objects, for example, a 2M page table is split into multiple 4K page tables according to the size of 4K. After completing the splitting of the target object and obtaining at least two initial objects, the virtual machine kernel can store the at least two initial objects in the object storage module corresponding to the virtual machine.

[0107] Furthermore, the object management module, in response to the target object splitting instruction, splits the target object corresponding to the virtual machine based on the preset object size to obtain at least two initial objects, including:

[0108] The object management module determines the target object corresponding to the virtual machine from the object storage unit corresponding to the virtual machine in response to the target object splitting instruction;

[0109] Based on the preset object size carried in the target object segmentation instruction, the target object is segmented into at least two initial objects.

[0110] In actual applications, the page table entry corresponding to the virtual machine is stored in the virtual machine memory. Based on this, after receiving the target object splitting instruction, the object management module responds to the target object splitting instruction and obtains the target object from the object storage module corresponding to the virtual machine. For example, KVM-kmod obtains the 2M page table entry from the physical storage unit corresponding to the virtual machine memory in the host machine. The physical storage unit can be understood as the physical memory of the host machine, or the storage resources allocated by the host machine to the virtual machine memory, etc., and no specific restrictions are made here.

[0111] Afterwards, the object management module divides the target object corresponding to the virtual machine based on the preset object size to obtain at least two initial objects. After obtaining the at least two initial objects, KVM-kmod can store the at least two initial objects in the object storage module.

[0112] In the embodiment provided in this specification, when the virtual machine completes hot migration, the virtual machine management module can delete the data of the virtual machine remaining in the source host machine, thereby releasing the resources of the source host machine. The specific implementation method is as follows.

[0113] After performing virtual machine migration on the virtual machine based on the at least two initial objects, the method further includes:

[0114] The virtual machine management module deletes the associated data corresponding to the virtual machine when determining that the virtual machine migration is successful.

[0115] The associated data corresponding to the virtual machine can be understood as data such as memory data corresponding to the virtual machine and a page table of the virtual machine.

[0116] Specifically, when determining that the virtual machine migration is successful, the virtual machine management module can delete the associated data corresponding to the virtual machine, thereby releasing the resources of the source host machine, for example, deleting the memory data of the virtual machine in the source host machine, the page table of the virtual machine and other data.

[0117] The object processing method provided in this specification deletes at least two initial objects corresponding to the virtual machine migration and recovery task by the object management module upon receiving an object deletion instruction sent by the virtual machine management module, thereby avoiding the impact of the residual initial objects on the performance of the virtual machine and avoiding the problem of the virtual machine performance degradation caused by the two initial objects, which leads to the reduction of the operating efficiency of the virtual machine. At the same time, upon receiving an object recovery request for the target object, the target object is restored, thereby ensuring the normal operation of the virtual machine.

[0118] The following combination Figure 3 , taking the application of the object processing method provided in this specification to rebuild the virtual machine page table after hot migration rollback as an example, the object processing method is further described. Figure 3 A processing flow chart of an object processing method provided by an embodiment of the present specification is shown, which specifically includes the following steps.

[0119] Step 302: Start hot migration.

[0120] Specifically, qemu starts hot migration for the virtual machine, and hot migrates the virtual machine from the source host machine to the destination host machine.

[0121] When hot migration is initiated, in order to reduce the transmission data and avoid the problem of large bandwidth demand for virtual machine hot migration, the 2M page table entries when the VM is created will be broken up and divided into multiple 4K page table entries for dirty marking. Based on the multiple 4K page table entries after division, the virtual machine is hot migrated from its original source host to the destination host.

[0122] Step 304: Determine whether to perform hot migration rollback.

[0123] Specifically, qemu can monitor the execution state of the virtual machine hot migration to determine whether to perform hot migration rollback. If so, it means that the hot migration operation is canceled due to the user canceling the hot migration through the console or command, the hot migration timeout or other reasons, and it is determined to perform hot migration rollback, and step 306 is executed.

[0124] If not, it means that the hot migration is successfully performed, and step 308 is executed.

[0125] Step 306: Determine whether to delete the page table entry.

[0126] Specifically, after hot migration is canceled and hot migration rollback is performed, the virtual machine operation and maintenance object determines whether to perform the operation of deleting the page table entry for the virtual machine obtained after the hot migration rollback. If so, execute step 310; if not, execute step 312.

[0127] Among them, the virtual machine operation and maintenance objects can be understood as operation and maintenance robots, operation and maintenance equipment, operation and maintenance programs, etc. for virtual machines.

[0128] Step 308: Determine that the hot migration is completed.

[0129] Specifically, when qemu determines that the hot migration is successful, it destroys the VM in the source host and deletes the memory data, page table and other data corresponding to the source VM. Correspondingly, it resumes the destination VM.

[0130] Step 310: Determine that the rollback is complete.

[0131] Specifically, after the hot migration is canceled and the hot migration rollback is performed, the ioctl command is sent to KVM-kmod through qemu, so that KVM-kmod can meet the drop spte (release page table entry) condition and enter the drop spte process, thereby deleting the 4K page table entry corresponding to the virtual machine after the hot migration rollback.

[0132] After KVM-kmod enters the drop spte process, when the virtual machine kernel is executing user tasks and cannot obtain the page table entry, a page fault exception will be triggered, the virtual machine will have a vm exit (a virtual machine event), enter KVM-kmod, and rebuild the page table entry.

[0133] After receiving the page table rebuild instruction, KVM-kmod will recreate a 2M (or larger than 2M) page table entry and store the 2M page table in the memory management module. The virtual machine kernel will load the 2M page table from the memory management module to ensure that the performance of the VM will not be affected.

[0134] Step 312: Determine that the rollback is complete.

[0135] Specifically, after the hot migration rollback operation is completed and the rolled-back virtual machine is obtained, it is determined that the rollback is completed. The page table corresponding to the virtual machine is a plurality of 4K page tables.

[0136] Based on this, the object processing method provided in this specification is a method for improving the performance of a virtual machine after hot migration rollback. In the actual hot migration rollback process, it can be learned from the measured data that the memory latency of the virtual machine has changed from 90ns before the migration to about 110ns, and the performance has decreased by about 25%; based on this, the method for improving the performance of a virtual machine after hot migration rollback provided in this specification, for the hot migration rollback scenario, releases the 4k page table entries broken up by the hot migration, so that when the vm is missing a page again, it will rebuild the 2M large page, so that the memory latency of the virtual machine will not fluctuate too much, and will be basically the same as the memory latency before the hot migration, thereby ensuring the normal operation of the virtual machine and avoiding the problem of not reducing the memory latency of the virtual machine after the hot migration rollback.

[0137] Corresponding to the above method embodiment, this specification also provides an object processing system embodiment. Figure 4 FIG. 1 shows a schematic diagram of the structure of an object processing system provided by an embodiment of the present specification. Figure 4 As shown, the system includes a virtual machine management module 402 and an object management module 404 in a host machine, wherein:

[0138] The virtual machine management module 402 is configured to send an object deletion instruction to the object management module 404 according to the virtual machine migration recovery task;

[0139] The object management module 404 is configured to delete at least two initial objects corresponding to the virtual machine migration and recovery task by executing the object deletion instruction, wherein the at least two initial objects are obtained by segmenting the target object corresponding to the virtual machine; and

[0140] When an object recovery request for the target object is received, the target object is recovered according to the historical record data corresponding to the target object.

[0141] Optionally, the virtual machine management module 402 is further configured to:

[0142] Monitoring current execution status information of the virtual machine migration recovery task, wherein the virtual machine migration recovery task is a task created when the virtual machine migration fails;

[0143] When it is determined that the virtual machine migration and recovery task is completed according to the current execution state information, an object deletion instruction is sent to the object management module 404 .

[0144] Optionally, the object processing system includes a virtual machine kernel;

[0145] Correspondingly, the virtual machine kernel is further configured to send a target object recovery request to the object management module 404 when executing an object execution task associated with the target object.

[0146] Optionally, the virtual machine kernel is further configured as:

[0147] receiving an object execution task associated with the target object;

[0148] In case of executing the object execution task, sending a target object recovery request to the virtual machine management module 402;

[0149] The virtual machine management module 402 sends the received target object recovery request to the object management module 404 .

[0150] Optionally, the object management module 404 is further configured to:

[0151] Determine a target object of the virtual machine and historical record data corresponding to the target object based on the received target object recovery request;

[0152] Determine the virtual address of the virtual machine and the physical address corresponding to the virtual address based on the historical record data;

[0153] Based on the virtual address and the physical address, a target object corresponding to the virtual machine is created.

[0154] Optionally, the virtual machine management module 402 is further configured to:

[0155] Acquire at least two initial objects corresponding to the virtual machine from the object storage module, and perform virtual machine migration on the virtual machine based on the at least two initial objects;

[0156] In the case where it is determined that the migration of the virtual machine fails, creating a virtual machine migration recovery task corresponding to the virtual machine;

[0157] The virtual machine is migrated and recovered according to the virtual machine migration and recovery task.

[0158] Optionally, the virtual machine management module 402 is further configured to:

[0159] Sending a target object segmentation instruction carrying a preset object size to the object management module 404;

[0160] The object management module 404, in response to the target object segmentation instruction, segments the target object corresponding to the virtual machine based on the preset object size to obtain at least two initial objects, and stores the at least two initial objects in the object storage module.

[0161] Optionally, the object management module 404 is further configured to:

[0162] In response to the target object splitting instruction, determining a target object corresponding to the virtual machine from an object storage unit corresponding to the virtual machine;

[0163] Based on the preset object size carried in the target object segmentation instruction, the target object is segmented into at least two initial objects.

[0164] Optionally, the virtual machine management module 402 is further configured to:

[0165] When it is determined that the migration of the virtual machine is successful, the associated data corresponding to the virtual machine is deleted.

[0166] Optionally, the object management module 404 is further configured to:

[0167] Storing the target object in an object storage module corresponding to the virtual machine, and sending a recovery completion instruction to the virtual machine kernel;

[0168] The virtual machine kernel is further configured as follows:

[0169] When the recovery completion instruction is received, the target object is loaded from the object storage module corresponding to the virtual machine, and an object execution task is performed according to the target object processing.

[0170] Optionally, the object management module 404 is further configured to:

[0171] Generate a recovery completion instruction based on the target object, and send the recovery completion instruction to the virtual machine kernel;

[0172] The virtual machine kernel is further configured as follows:

[0173] When the recovery completion instruction is received, the target object carried by the recovery completion instruction is obtained, and the object execution task is processed according to the target object.

[0174] The object processing system provided in this specification deletes at least two initial objects corresponding to the virtual machine migration and recovery task through the object management module when receiving the object deletion instruction sent by the virtual machine management module, thereby avoiding the impact of the residual initial objects on the performance of the virtual machine and avoiding the problem of the virtual machine performance degradation caused by the two initial objects, resulting in the reduction of the operating efficiency of the virtual machine. At the same time, when receiving an object recovery request for the target object, the target object is restored, thereby ensuring the normal operation of the virtual machine.

[0175] The above is a schematic scheme of an object processing system of this embodiment. It should be noted that the technical scheme of the object processing system and the technical scheme of the object processing method described above are of the same concept, and the details not described in detail in the technical scheme of the object processing system can be referred to the description of the technical scheme of the object processing method described above.

[0176] Figure 5 The structure block diagram of a computing device 500 provided according to an embodiment of the present specification is shown. The components of the computing device 500 include but are not limited to a memory 510 and a processor 520. The processor 520 is connected to the memory 510 via a bus 530, and the database 550 is used to store data.

[0177] The computing device 500 also includes an access device 540 that enables the computing device 500 to communicate via one or more networks 560. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 540 may include one or more of any type of network interface (e.g., a network interface card (NIC)) whether wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a World Wide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, a near field communication (NFC) interface, and the like.

[0178] In one embodiment of the present specification, the above components of the computing device 500 and Figure 5 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Figure 5 The computing device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0179] The computing device 500 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or PC. The computing device 500 may also be a mobile or stationary server.

[0180] The processor 520 is used to execute the following computer executable instructions, which, when executed by the processor 520, implement the steps of the above-mentioned object processing method.

[0181] The above is a schematic scheme of a computing device of this embodiment. It should be noted that the technical scheme of the computing device and the technical scheme of the object processing method described above are of the same concept, and the details not described in detail in the technical scheme of the computing device can be referred to the description of the technical scheme of the object processing method described above.

[0182] An embodiment of the present specification further provides a computer-readable storage medium storing computer-executable instructions, which can implement the steps of the above-mentioned object processing method when executed by a processor.

[0183] The above is a schematic scheme of a computer-readable storage medium of this embodiment. It should be noted that the technical scheme of the storage medium and the technical scheme of the object processing method described above are of the same concept, and the details not described in detail in the technical scheme of the storage medium can be referred to the description of the technical scheme of the object processing method described above.

[0184] An embodiment of the present specification further provides a computer program, wherein when the computer program is executed in a computer, the computer is caused to execute the steps of the above-mentioned object processing method.

[0185] The above is an illustrative solution of a computer program of this embodiment. It should be noted that the technical solution of the computer program and the technical solution of the object processing method described above are of the same concept, and the details not described in detail in the technical solution of the computer program can be found in the description of the technical solution of the object processing method described above.

[0186] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0187] The computer instructions include computer program codes, which may be in source code form, object code form, executable files or some intermediate forms, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0188] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of this specification are not limited by the order of the actions described, because according to the embodiments of this specification, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of this specification.

[0189] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0190] The preferred embodiments of this specification disclosed above are only used to help explain this specification. The optional embodiments do not describe all the details in detail, nor do they limit the invention to only the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of the embodiments of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of this specification, so that technicians in the relevant technical field can well understand and use this specification. This specification is only limited by the claims and their full scope and equivalents.

Claims

1. An object processing method, applied to an object processing system, the system comprising a virtual machine management module and an object management module in a host machine, wherein: The virtual machine management module sends an object deletion instruction to the object management module according to the virtual machine migration recovery task; the sending of the object deletion instruction to the object management module according to the virtual machine migration recovery task includes: sending the object deletion instruction to the object management module when it is determined that the virtual machine migration recovery task is completed according to the current execution state information of the virtual machine migration recovery task; The object management module deletes at least two initial objects corresponding to the virtual machine migration and recovery task by executing the object deletion instruction, wherein the at least two initial objects are obtained by segmenting the target object corresponding to the virtual machine; and When a target object recovery request for the target object is received, the target object is restored according to the historical record data corresponding to the target object, where the historical record data is data recording the mapping relationship between the virtual address of the virtual machine in the page table and the physical address of the host machine.

2. The object processing method according to claim 1, wherein the virtual machine management module sends an object deletion instruction to the object management module when determining that the virtual machine migration task is restored based on the current execution state information of the virtual machine migration recovery task, comprising: The virtual machine management module monitors the current execution status information of the virtual machine migration recovery task, wherein the virtual machine migration recovery task is a task created when the virtual machine migration fails; When it is determined according to the current execution state information that the virtual machine migration recovery task is completed, an object deletion instruction is sent to the object management module.

3. The object processing method according to claim 1, wherein the object processing system comprises a virtual machine kernel; Correspondingly, after the object management module deletes at least two initial objects corresponding to the virtual machine migration recovery task by executing the object deletion instruction, the object management module further includes: The virtual machine kernel, when executing an object execution task associated with the target object, sends a recovery request for the target object to the object management module.

4. The object processing method according to claim 3, wherein the virtual machine kernel, when executing an object execution task associated with the target object, sends a target object recovery request to the object management module, comprising: The virtual machine kernel receives an object execution task associated with the target object; In case of executing the object execution task, sending a target object recovery request to the virtual machine management module; The virtual machine management module sends the received target object recovery request to the object management module.

5. The object processing method according to claim 1, wherein the object management module, in response to the object recovery request, recovers the target object according to the historical record data corresponding to the target object, comprising: The object management module determines the target object of the virtual machine and the historical record data corresponding to the target object based on the received target object recovery request; Determine the virtual address of the virtual machine and the physical address corresponding to the virtual address based on the historical record data; Based on the virtual address and the physical address, a target object corresponding to the virtual machine is created.

6. The object processing method according to any one of claims 1 to 5, wherein before the virtual machine management module sends the object deletion instruction to the object management module according to the virtual machine migration recovery task, the method further comprises: The virtual machine management module obtains at least two initial objects corresponding to the virtual machine from the object storage module, and performs virtual machine migration on the virtual machine based on the at least two initial objects; In the case where it is determined that the migration of the virtual machine fails, creating a virtual machine migration recovery task corresponding to the virtual machine; The virtual machine is migrated and recovered according to the virtual machine migration and recovery task.

7. The object processing method according to claim 6, before the virtual machine management module obtains at least two initial objects corresponding to the virtual machine from the object storage module, further comprising: The virtual machine management module sends a target object segmentation instruction carrying a preset object size to the object management module; The object management module, in response to the target object segmentation instruction, segments the target object corresponding to the virtual machine based on the preset object size to obtain at least two initial objects, and stores the at least two initial objects in the object storage module.

8. The object processing method according to claim 7, wherein the object management module, in response to the target object segmentation instruction, segments the target object corresponding to the virtual machine based on the preset object size to obtain at least two initial objects, comprising: The object management module determines the target object corresponding to the virtual machine from the object storage unit corresponding to the virtual machine in response to the target object splitting instruction; Based on the preset object size carried in the target object segmentation instruction, the target object is segmented into at least two initial objects.

9. The object processing method according to claim 6, after performing virtual machine migration on the virtual machine based on the at least two initial objects, further comprising: The virtual machine management module deletes the associated data corresponding to the virtual machine when determining that the virtual machine migration is successful.

10. The object processing method according to claim 3, after restoring the target object according to the historical record data corresponding to the target object, further comprising: The object management module stores the target object in the object storage module corresponding to the virtual machine, and sends a recovery completion instruction to the virtual machine kernel; The virtual machine kernel, upon receiving the recovery completion instruction, loads the target object from the object storage module corresponding to the virtual machine and processes the object execution task according to the target object.

11. The object processing method according to claim 3, after restoring the target object according to the historical record data corresponding to the target object, further comprising: The object management module generates a recovery completion instruction based on the target object, and sends the recovery completion instruction to the virtual machine kernel; The virtual machine kernel, upon receiving the recovery completion instruction, obtains the target object carried by the recovery completion instruction, and processes the object execution task according to the target object.

12. An object processing system, comprising a virtual machine management module and an object management module in a host machine, wherein: The virtual machine management module is configured to send an object deletion instruction to the object management module according to the virtual machine migration recovery task; The object management module is configured to delete at least two initial objects corresponding to the virtual machine migration and recovery task by executing the object deletion instruction, wherein the at least two initial objects are obtained by segmenting the target object corresponding to the virtual machine; and When receiving an object recovery request for the target object, recover the target object according to the historical record data corresponding to the target object, wherein the historical record data is data recording a mapping relationship between a virtual address of the virtual machine and a physical address of the host machine in a page table; The virtual machine management module is further configured to send an object deletion instruction to the object management module when determining that the virtual machine migration task is restored based on the current execution state information of the virtual machine migration recovery task.

13. A computing device comprising: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the object processing method described in any one of claims 1 to 11 are implemented.

14. A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the steps of the object processing method according to any one of claims 1 to 11.

15. A computer program product, characterized in that The method comprises computer instructions, which, when executed by a processor, implement the steps of the object processing method according to any one of claims 1 to 11.

Images