WO2023179388A1

WO2023179388A1 - Hot migration method for virtual machine instance

Info

Publication number: WO2023179388A1
Application number: PCT/CN2023/080978
Authority: WO
Inventors: 刘派
Original assignee: 阿里巴巴（中国）有限公司
Priority date: 2022-03-25
Filing date: 2023-03-13
Publication date: 2023-09-28
Also published as: CN114691300A

Abstract

Provided in the present description is a hot migration method for a virtual machine instance, which method is applied to a cloud service device. The cloud service device carries micro-service hardware, and a virtual machine instance comprises a virtual machine simulator process on the micro-service hardware and a virtual machine driver in an operating system kernel which is carried by the cloud service device. The method comprises: in response to a virtual machine instance to be migrated meeting a hot migration condition, an operating system kernel acquiring first running data of the virtual machine instance in the operating system kernel which is carried by a cloud service device, and writing the first running data into a preset memory space; a virtual machine simulator process acquiring second running data of the virtual machine instance on micro-service hardware and third running data of the virtual machine instance in a memory space of the cloud service device, and reading the first running data from the preset memory space; and the virtual machine simulator process sending the acquired running data to a target cloud service device, so as to migrate the virtual machine instance to the target cloud service device.

Description

A method of live migration of virtual machine instances

This application claims priority to the Chinese patent application submitted to the China Patent Office on March 25, 2022, with the application number 202210307611.5 and the application name "A method for live migration of virtual machine instances", the entire content of which is incorporated herein by reference. Applying.

Technical field

The embodiments of this specification relate to the field of computer technology, and more specifically, the embodiments of this specification relate to a method for live migration of virtual machine instances.

Background technique

This section is intended to provide background or context for the implementation of this specification as set forth in the claims. The description herein is not admitted to be prior art by inclusion in this section.

Cloud servers usually include virtual machine instances implemented through virtualization technology on cloud server devices. Through virtual machine instances, various services of cloud servers can be implemented. These businesses usually need to remain online in real time, so when the virtual machine instances need to be migrated from the current cloud service equipment, these businesses cannot be interrupted.

Contents of the invention

In order to overcome the problems existing in related technologies, this specification provides the following methods and devices.

In the first aspect of the implementation of this specification, a method of live migration of virtual machine instances is provided, which is applied to cloud service equipment. The cloud service equipment is equipped with microservice hardware. The virtual machine instances to be migrated include those running on the microservices. The virtual machine simulator process on the service hardware and the virtual machine driver running in the operating system kernel carried by the cloud service device; the method includes:

In response to the virtual machine instance to be migrated meeting the hot migration conditions, the virtual machine driver obtains the first running data of the virtual machine instance in the operating system kernel mounted on the cloud service device, and transfers the first The running data is written into the preset memory space;

The virtual machine simulator process obtains the second operating data of the virtual machine instance on the microservice hardware and the third operating data of the virtual machine instance in the memory space of the cloud service device, and obtains the second operating data of the virtual machine instance on the microservice hardware and obtains the third operating data from the virtual machine instance. Read the first operating data from the preset memory space;

The virtual machine simulator process sends the obtained first operating data, the second operating data and the third operating data to the target cloud service device to migrate the virtual machine instance to the target. Cloud service equipment.

In the second aspect of the implementation of this specification, a live migration device for virtual machine instances is provided, which is applied to cloud service equipment. The cloud service equipment is equipped with microservice hardware. The virtual machine instances to be migrated include those running on microservices. The virtual machine simulator process on the service hardware and the virtual machine driver running in the operating system kernel carried by the cloud service equipment; the device includes:

A first acquisition unit configured to, in response to the virtual machine instance to be migrated satisfy the live migration condition, the virtual machine driver acquire the first running data of the virtual machine instance in the operating system kernel mounted on the cloud service device , and write the first operating data into the preset memory space;

A second acquisition unit configured to acquire, through the virtual machine simulator process, the second running data of the virtual machine instance on the microservice hardware and the memory space of the virtual machine instance in the cloud service device. third operating data, and reading the first operating data from the preset memory space;

A data sending unit, configured to send the acquired first running data, the second running data and the third running data to a target cloud service device by the virtual machine simulator process, so as to send the virtual machine simulator to the target cloud service device. Migrate the machine instance to the target cloud service device.

In a third aspect of the implementation of this specification, a system is provided; the system includes: a source cloud service device and a destination cloud service device;

The source cloud service device is equipped with source microservice hardware. The virtual machine instance to be migrated includes a virtual machine simulator process running on the microservice hardware and a virtual machine running in the operating system kernel installed on the source cloud service device. drive;

The source cloud service device is configured to: in response to the virtual machine instance to be migrated meeting the hot migration condition, the operating system kernel obtains the virtual machine instance in the operating system kernel installed on the source cloud service device. a running data, and writes the first running data into a preset memory space; the virtual machine simulator process obtains the second running data of the virtual machine instance on the source microservice hardware and the virtual The third running data of the machine instance in the memory space of the source cloud service device, and reads the first running data from the preset memory space; the virtual machine simulator process will obtain all the The first operating data, the second operating data and the third operating data are sent to the target cloud service device to migrate the virtual machine instance to the target cloud service device;

The target cloud service device is equipped with target microservice hardware;

The target cloud service device is configured to: in response to the virtual machine instance to be migrated satisfying the live migration condition, accept the first operating data sent by the source cloud service device, the second operating data and the The third operating data; create a virtual machine instance according to the received operating data. The virtual machine instance includes a virtual machine simulator process running on the target microservice hardware and an operating system running on the target cloud service device. Virtual machine driver in the kernel to complete the migration of virtual machine instances from the source cloud service device to the target cloud service device.

In a fourth aspect of the implementation of this specification, a storage medium is provided; a computer program is stored on the storage medium, and when the computer program is executed, the steps of the following method are implemented:

In response to the virtual machine instance to be migrated meeting the hot migration conditions, the operating system kernel obtains the first running data of the virtual machine instance in the operating system kernel installed on the cloud service device, and transfers the first The running data is written into the preset memory space;

In a fifth aspect of the embodiment of this specification, a computer device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the processor executes the program Implement the following methods:

The above embodiments in this specification have at least the following beneficial effects:

In the above technical solution, when the virtual machine instance to be migrated meets the live migration conditions, the running data of the virtual machine instance to be migrated on the cloud service equipment and microservice hardware is obtained in real time, and the virtual machine simulator process is used to migrate the virtual machine instance to be migrated. The running data of the virtual machine instance is sent to the target service device. Since all running data of the virtual machine instance to be migrated is transferred to the target service device, the migrated virtual machine instance can continue to run on the target service device without causing business interruption.

Description of the drawings

In order to more clearly explain the embodiments of this specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are only These are some embodiments recorded in this specification. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings.

Figure 1 schematically shows a schematic diagram of a virtual machine instance according to an embodiment of this specification;

Figure 2 schematically shows an architectural diagram of a live migration system for a virtual machine instance according to an embodiment of this specification;

Figure 3 schematically shows a flow chart of a method for live migration of a virtual machine instance according to an embodiment of this specification;

Figure 4 schematically shows a block diagram of a live migration device for a virtual machine instance according to an embodiment of this specification;

Figure 5 schematically shows an architectural diagram of a live migration system for a virtual machine instance according to an embodiment of this specification;

FIG. 6 schematically shows a hardware structure diagram of a computer device where a live migration method of a virtual machine instance is implemented according to an embodiment of this specification.

In the drawings, the same or corresponding reference numerals represent the same or corresponding parts.

Detailed ways

The principles and spirit of the present specification will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided only to enable those skilled in the art to better understand and implement the present specification, and are not intended to limit the scope of the present specification in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

Those skilled in the art know that the embodiments of this specification can be implemented as a system, device, equipment, method or computer program product. Therefore, this specification can be implemented in the following form, namely: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

Cloud servers are implemented through virtualization technology and cloud computing technology, and are deployed on cloud service platforms. The cloud server of microservice architecture is an implementation architecture of cloud server.

For example, please refer to FIG. 1 , which schematically shows a schematic structural diagram of a virtual machine instance according to an embodiment of this specification.

The cloud server with microservice architecture introduces a microservice hardware on the physical server and independently runs an operating system on the microservice hardware. The microservice hardware can be a microservice card connected to the physical server through a bus, and provides services such as virtualization of input and output IO devices, processing and forwarding of IO requests to the physical server, so that the physical server can become like a virtual machine. flexible.

When the virtual machine instance is deployed on the cloud server of the above microservice architecture, the virtual machine instance can adopt a separated architecture, and the virtual machine simulator process of the virtual machine can be run on the microservice hardware, and the virtual machine simulator process and the physical The server operating system kernel implements virtualization of hardware devices such as CPU, memory, and input and output devices to implement virtual machine instances.

Wherein, multiple virtual machine embodiments can be deployed on the above-mentioned physical server at the same time, and the above-mentioned multiple virtual machine instances can share the above-mentioned physical server operating system kernel.

In the scenario of using the cloud server with the above microservice architecture, the virtual machine instances on a certain cloud service device may need to be migrated to a new cloud service device in some cases.

Due to various businesses on cloud servers. These businesses usually need to remain online in real time, so when the virtual machine instances need to be migrated from the current cloud service equipment, these businesses cannot be interrupted.

In view of this, this application proposes a method to obtain the running data of the virtual machine instance to be migrated on cloud service equipment and microservice hardware in real time when the virtual machine instance to be migrated meets the conditions for live migration, and use the virtual machine simulator to process A live migration method that sends the running data of the virtual machine instance to be migrated to the virtual machine instance of the target service device.

Exemplary embodiments will be described in detail below, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of this specification. Rather, they are merely examples of apparatus and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.

It should be noted that in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, methods may include more or fewer steps than described in this specification. In addition, a single step described in this specification may be broken down into multiple steps for description in other embodiments; and multiple steps described in this specification may also be combined into a single step in other embodiments. describe.

Figure 2 is a schematic architectural diagram of a live migration system for virtual machine instances provided in an exemplary embodiment. As shown in Figure 1, the system may include a network 20, a server 21, and several electronic devices, such as mobile phones 22, 23, and 24.

The server 21 may be a physical server including an independent host, or the server 21 may be a virtual server, cloud server, etc. hosted by a host cluster. Cell phones 22-24 are just one type of electronic device available to users. In fact, users can obviously also use the following types of electronic devices: tablets, laptops, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.), etc. One or more of this manual Various embodiments are not limited in this regard. Network 20 may include various types of wired or wireless networks.

In one embodiment, the server 21 can cooperate with the mobile phones 22-24; wherein the mobile phones 22-24 can accept user operations and upload the received commands and files to the server 21 through the network 20, and then the server 21 can The file is processed according to the program in the instructions. In another embodiment, the mobile phone 22-24 can independently implement the text processing solution of this description; wherein the mobile phone 22-24 accepts user operations and processes the accepted commands and files based on the solution of this description to realize virtualization. Live migration of machine instances.

The solutions of this specification will be described in detail below with reference to the accompanying drawings.

Please refer to Figure 3. Figure 3 is a flow chart of a method for live migration of a virtual machine instance provided by an exemplary embodiment. The method is applied to a processing device. The processing device can be, for example, the server 21 or a mobile phone shown in Figure 2. 22-24 etc.

This method is applied to cloud service equipment, which is equipped with microservice hardware. The virtual machine instance to be migrated includes a virtual machine simulator process running on the microservice hardware and an operating system kernel running on the cloud service equipment. Virtual machine driver in;

The virtual machine instance on the cloud server includes a virtual machine simulator process running on the microservice hardware and an operating system kernel driver installed on the cloud server device. The above virtual machine simulator process and kernel driver jointly implement the CPU, memory, input and output devices, etc. Hardware virtualization.

In one embodiment shown in this specification, the above-mentioned virtual machine simulator process realizes the virtualization of hardware such as input and output devices, and the above-mentioned kernel driver jointly realizes the virtualization of hardware such as CPU and memory.

In one embodiment shown in this specification, the above-mentioned microservice hardware includes a microservice card.

Microservice card, such as MOC (microserver on card) card, is a kind of microservice hardware. It is a physical board device with its own CPU and ROM/RAM. It can run an independent operating system and can be connected through the system bus (such as PCIe) is connected to a physical server and provides services such as virtualization of input and output devices, processing and forwarding of input and output requests to the server.

This manual does not limit the specific type of operating system installed on the cloud service device. For example, it can be Linux, MacOS, or Windows, etc.

This manual does not limit the specific type of virtual machine instance. For example, it can be a KVM (Kernel-based Virtual Machine, kernel-based virtual machine) virtual machine instance, a Xen virtual machine instance, or a vbox virtual machine instance, etc.

Similarly, this description does not limit the specific type of the virtual machine emulator process. For example, it can be a QEMU process, a VMware process, etc.

In one embodiment shown in this specification, the virtual machine instance includes a KVM virtual machine instance; the virtual machine emulator process includes a QEMU process.

The operating system installed on the above cloud service device may be Linux, and the virtual machine instance may be a KVM virtual machine instance. KVM virtual machine instances include virtual machine drivers integrated into the Linux operating system kernel in the form of modules, and the above-mentioned QEMU process.

The above method performs the following steps:

Step 302: In response to the virtual machine instance to be migrated meeting the hot migration conditions, the operating system kernel obtains the first running data of the virtual machine instance in the operating system kernel installed on the cloud service device, and transfers the The first operating data is written into the preset memory space;

In some cases, virtual machine instances on cloud service devices may need to be live migrated. This application does not specifically limit the specific form and content of the live migration conditions that the virtual machine instances to be migrated need to meet.

In an exemplary embodiment shown in this application, the live migration condition of a virtual machine instance may be that the value corresponding to the running indicator of the virtual machine instance reaches a preset threshold. It should be understood that when the values corresponding to the above-mentioned operating indicators reach the preset threshold, one or more operating indicators may be lower than the preset threshold, one or more operating indicators may be higher than the preset threshold, or one or more operating indicators may be higher than the preset threshold. Multiple operating indicators are equal to or not equal to the preset threshold, or a logical combination of the above situations. This specification does not specifically limit this.

For example, the hot migration condition may be that the operating index A>100, and the operating index B is within the interval (1,10].

In response to the virtual machine instance to be migrated meeting the above hot migration conditions, migration of relevant operating data of the virtual machine instance to be migrated begins.

Wherein, the running data of the above-mentioned virtual machine instance includes: the first running data of the virtual machine instance in the operating system kernel installed on the cloud service device, the second running data of the virtual machine instance on the microservice hardware, and, the virtual machine The third running data of the instance in the memory space of the cloud service device.

In an illustrative embodiment shown in this specification, the above-mentioned first operating data includes the virtual machine instance in the above-mentioned Virtual CPU status data and virtual device status data on the cloud service device.

The above virtual CPU status data may include vcpu_regs (general register data), vcpu_sregs (segment register data), fpu (floating point unit data) and other virtual CPU statuses.

The above-mentioned virtual device status data may include clock (clock data), ioapic (input and output advanced programmable interrupt controller data), rtc (real-time clock data) and other device status data.

This specification does not specifically limit the organizational form of the above-mentioned first operating data. For example, the above first operating data can be organized in the form of a structure, or other data types can be used.

The first operating data in the operating system kernel installed on the cloud service device can be obtained through the operating system kernel and written into the preset memory space.

This specification does not specifically limit how the operating system kernel obtains the above-mentioned first operating data or writes it into the memory space. For example, it can be implemented directly through the virtual machine driver in the operating system kernel, or through other programs in the operating system kernel.

In an illustrative embodiment shown in this specification, a service program for obtaining and storing the first operating data may be implemented in the operating system kernel mounted on the cloud service device. Callback functions can be registered in the operating system kernel installed on the above-mentioned cloud service devices.

When the virtual machine instance meets the live migration conditions, the above callback function can be triggered to initiate a call to the above service program. The above service program can be run in the operating system kernel of the cloud service device to obtain the first running data of the virtual machine instance on the cloud service device, and write the first running data into the preset memory space.

For example, assume that the virtual machine instance is a KVM virtual machine instance and the operating system installed on the cloud service device is Linux.

The KVM module includes virtual machine drivers integrated into the Linux operating system kernel in the form of modules. The virtual machine driver can manage virtual hardware resources and complete the allocation of virtual machine memory, the reading and writing of virtual machine registers, and the operation of the virtual machine CPU.

The service program kvm_save for obtaining and storing the first operating data can be implemented in the Linux operating system kernel installed on the cloud service device. A callback function can be created and registered on the Linux kernel operating system, where the triggering condition of the callback function can be set to the above live migration conditions.

When the virtual machine instance meets the live migration conditions, the callback function can be triggered, and the service program kvm_save obtains the first running data on the above-mentioned cloud service device, including virtual CPU status data and virtual device status data, and saves it to the above-mentioned preset memory. space.

Among them, this specification does not limit the manner in which the above-mentioned service program obtains the above-mentioned first operating data.

For example, assume that the virtual machine instance is a KVM virtual machine instance and the operating system installed on the cloud service device is Linux. When a virtual machine instance is created, the KVM module will create a corresponding struct_kvm structure for the virtual machine instance to store the virtual CPU state, and synchronize the address of the struct_kvm to the service program kvm_save. Among them, the virtual CPU status will be saved into the struct_kvm structure in the data structure of vmcs (Virtual Machine Control Structure, virtual machine control structure). When the live migration conditions are met, the service program kvm_save can call the virtual CPU The status reading function vmcs_read obtains the corresponding virtual CPU status data from the vmcs data structure saved in the struct_kvm structure.

In an exemplary embodiment shown in this specification, the preset memory area includes a preset memory area applied from the memory space of the cloud service device corresponding to the virtual machine instance when the virtual machine instance is created. Leave memory space.

When creating a virtual machine instance, you can apply for reserved memory in the memory space of the cloud service device corresponding to the virtual machine instance, and use it to write the above-mentioned first operating data into the reserved memory when the live migration conditions are met.

Since the reserved memory space is in the memory of the cloud service device rather than the memory of the virtual machine instance, the reserved memory space can still be easily read after the virtual machine instance stops running.

This application does not limit the specific method of applying for reserved memory. For example, it can be implemented through the above-mentioned virtual machine simulator process, or through the operating system kernel installed on the above-mentioned cloud service device.

For example, assume that the virtual machine instance is a KVM virtual machine instance and the operating system installed on the cloud service device is Linux. The above reserved memory can be that the virtual machine simulator process applies for memory in the above service program kvm_save through the input and output control function IOCTL, and allocates and obtains the physical address of this memory space through the memory allocation function kzalloc. This allows the service program kvm_save to write the obtained first operation data into the reserved memory space after obtaining the first operation data.

Step 304: The virtual machine simulator process obtains the second running data of the virtual machine instance on the microservice hardware, and reads the first running data from the preset memory space;

After the first operating data is written into the reserved memory space, the virtual machine simulator process can obtain the first operating data of the reserved memory space.

In addition to the above first running data, live migration of the virtual machine instance also requires migrating the second running data of the above virtual machine instance on the microservice hardware. Therefore, the virtual machine simulator process can obtain the second running data of the virtual machine instance on the microservice hardware.

In an illustrative embodiment shown in this specification, the second running data includes: virtual device status data of the virtual machine instance on the microservice hardware.

The running data of the virtual machine instance includes the device status data on the above-mentioned microservice hardware.

Among them, this manual does not specifically limit the way in which the virtual machine simulator process obtains the device status data on the above-mentioned microservice hardware.

For example, in an illustrative embodiment shown, this part of the device status data can usually be saved by the virtual machine simulator process on the microservice hardware, and therefore can be directly obtained by the above-mentioned virtual machine simulator process.

In an illustrative embodiment shown in this specification, the third running data includes: data written by the virtual machine instance into the memory space corresponding to the virtual machine instance.

The running data of a virtual machine instance includes the memory data of the virtual machine instance, that is, the data written into the memory space corresponding to the virtual machine instance.

The memory space corresponding to the above-mentioned virtual machine instance is virtualized memory, which can be obtained by virtualizing the memory of the above-mentioned cloud server device.

The virtual machine simulator process can manage the data in the memory space corresponding to the virtual machine instance. Therefore, the virtual machine emulator process can obtain the memory data of the virtual machine instance.

For example, when the virtual machine emulator process is a QEMU process, the memory space corresponding to the virtual machine instance can be managed in MemoryRegion mode. Among them, when the memory space corresponding to the virtual machine instance is managed in MR (MemoryRegion) mode, an MR is used to represent a memory address. Among them, MR includes many categories, such as RAM, MMIO, container, alias, etc. The QUMU process can create a data structure named RamBlock for each of the above MRs, and all RamBlocks are strung together in the form of a linked list.

When the live migration conditions are met, the QEMU process can read the above RamBlock linked list to obtain the customer physical address (gpa) of various types of memory. Among them, the customer physical addresses of some MRs are stored in the form of variables in the QEMU process and can be obtained directly; some special MRs have blank memory reserved between them, and a structure can be used to record the size of the blank memory in advance. Based on the read value and the size of the blank memory, the customer's physical address of the actual memory data can be calculated.

Through the input and output memory management unit IOMMU of the virtual machine instance, the customer physical address of various types of memory can be converted into the physical address of the memory on the cloud service device. According to the physical address of the memory of the cloud service device, the QEMU process can pass the DMA of the virtual machine instance. Channel to obtain the data of the memory space corresponding to the virtual machine instance.

Step 306: The virtual machine simulator process sends the obtained first running data, the second running data and the third running data to the target cloud service device to migrate the virtual machine instance to The target cloud service device.

After obtaining the first running data, the second running data and the third running data, the virtual machine simulator process can send the running data of these virtual machine instances to the target cloud server device.

Among them, this manual does not specifically limit the selection of target cloud service equipment. For example, an available cloud service device can be randomly selected as the target cloud server, or the user can specify a specific cloud service device as the target cloud server, etc.

In an embodiment shown in this specification, cloud service devices that are currently in a normal state can be obtained; and from the cloud service devices in a normal state, a target cloud service device as the migrated party is allocated. The target cloud service device may be any of the cloud service devices in the above normal state.

This application does not specifically limit the manner in which the virtual machine simulator process sends the above running data to the target cloud server device.

In an exemplary embodiment of this specification, a device for live migration of virtual machine instances is also provided. Please refer to Figure 4. Figure 4 is a block diagram of a live migration device for a virtual machine instance according to an embodiment of this specification.

The device is applied to cloud service equipment. The cloud service equipment is equipped with microservice hardware. The virtual machine instance to be migrated includes a virtual machine simulator process running on the microservice hardware and an operating system running on the cloud service equipment. Virtual machine driver in the kernel; the device includes:

The first acquisition unit 410 is configured to, in response to the virtual machine instance to be migrated satisfy the hot migration condition, the operating system kernel obtain the first operation status of the virtual machine instance in the operating system kernel installed on the cloud service device. row data, and write the first running data into the preset memory space;

The second acquisition unit 420 is used to acquire, from the virtual machine simulator process, the second running data of the virtual machine instance on the microservice hardware and the memory space of the virtual machine instance in the cloud service device. The third operating data, and reads the first operating data from the preset memory space;

The data sending unit 440 is configured to send the obtained first running data, the second running data and the third running data to the target cloud service device by the virtual machine simulator process, so as to send the obtained The virtual machine instance is migrated to the target cloud service device.

Optionally, the live migration conditions include any of the following: the value corresponding to the running indicator of the virtual machine instance reaches a preset threshold; a live migration instruction for the virtual machine instance is received.

Optionally, a service program for obtaining and storing the first operating data is implemented in the operating system kernel installed on the cloud service device; a callback function is registered in the operating system kernel installed on the cloud service device; so The callback function is automatically triggered when the virtual machine instance meets the live migration conditions and is used to initiate a call to the service program;

The first acquisition unit 410 is specifically configured to respond to the virtual machine instance meeting the live migration conditions, trigger the callback function, and initiate a call to the service program to run the operating system kernel installed on the cloud service device. The service program obtains the first running data of the virtual machine instance on the cloud service device, and writes the first running data into a preset memory space.

Optionally, the preset memory area includes reserved memory space applied from the memory space of the cloud server device corresponding to the virtual machine instance when the virtual machine instance is created.

Optionally, the first running data includes: virtual CPU status data and virtual device status data of the virtual machine instance on the cloud service device; the second running data includes: the virtual machine instance on the cloud service device. The virtual device status data on the microservice hardware; the third operating data includes: data written by the virtual machine instance into the memory space corresponding to the virtual machine instance.

Optionally, the apparatus further includes: a target selection unit 430, configured to obtain the cloud service equipment currently in a normal state; and allocate the target cloud service equipment as the migrated party from the cloud service equipment in the normal state.

Optionally, the microservice hardware includes a microservice card.

Optionally, the virtual machine instance includes a KVM virtual machine instance; the virtual machine emulator process includes a QEMU process.

For details on the implementation process of the functions and effects of each unit in the above device, please refer to the implementation process of the corresponding steps in the above method, and will not be described again here.

As for the device embodiment, since it basically corresponds to the method embodiment, please refer to the partial description of the method embodiment for relevant details. The device embodiments described above are only illustrative. The units described as separate components may or may not be physically separated. The components shown as units may or may not be physical units, that is, they may be located in One location, or it can be distributed across multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution in this specification. Persons of ordinary skill in the art can understand and implement the method without any creative effort.

In the exemplary embodiment of this specification, a system embodiment is also provided. Please refer to Figure 5. Figure 5 is a schematic architectural diagram of a live migration system for virtual machine instances according to an embodiment of this specification.

The system includes: source cloud service equipment and destination cloud service equipment;

The target cloud service device is equipped with target microservice hardware;

In the exemplary embodiments of this specification, embodiments of a device and a terminal to which it is applied are also provided.

The embodiments of the live migration device for virtual machine instances in this specification can be applied to computer equipment, such as servers or terminal equipment. The device embodiments may be implemented by software, or may be implemented by hardware or a combination of software and hardware. Taking software implementation as an example, as a device in a logical sense, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory and running it through its processor. From the hardware level, as shown in Figure 6, it is a hardware structure diagram of the computer device 60 where the live migration device of a virtual machine instance is located in the embodiment of this specification. In addition to the processor 612 and the memory 630 shown in Figure 6 In addition to the network interface 620 and the non-volatile memory 540, the server or electronic equipment where the device is located in the embodiment may also include other hardware according to the actual functions of the computer equipment, which will not be described again.

In an exemplary embodiment of this specification, a computer-readable storage medium is also provided, on which a program product capable of implementing the above method of this specification is stored. In some possible embodiments, various aspects of this specification can also be implemented in the form of a program product, which includes program code. When the program product is run on a terminal device, the program code is used to cause the The terminal device performs the steps according to various exemplary embodiments of this specification described in the above-mentioned "Exemplary Method" section of this specification.

The program product used to implement the above method according to the embodiment of the present specification can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of this specification is not limited thereto. In this document, the readable storage medium may be any containing or A tangible medium that stores a program for use by or in connection with an instruction execution system, apparatus, or device.

The program product may take the form of any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: electrical connection with one or more conductors, portable disk, hard disk, random access memory (RAM), read only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.

A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave carrying readable program code therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A readable signal medium may also be any readable medium other than a readable storage medium that can send, propagate, or transport the program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any suitable medium, including but not limited to wireless, wireline, optical cable, RF, etc., or any suitable combination of the foregoing.

Program code for performing the operations of this specification may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, etc., as well as conventional procedures programming language - such as "C" or a similar programming language. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server execute on. In situations involving remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device, such as provided by an Internet service. (business comes via Internet connection).

Although this specification contains many specific implementation details, these should not be construed to limit the scope of any invention or what is claimed, but rather serve primarily to describe features of specific embodiments of particular inventions. Certain features described in this specification as multiple embodiments can also be combined in a single embodiment. On the other hand, various features that are described in a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, while features may function in certain combinations as described above and may even be originally claimed as such, one or more features from a claimed combination may in some cases be removed from that combination, and as claimed A protected combination can point to a subcombination or a variant of a subcombination.

Similarly, although operations are depicted in a specific order in the drawings, this should not be construed as requiring that the operations be performed in the specific order shown, or sequentially, or that all illustrated operations be performed to achieve desired results. result. In some cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system units and components in the above-described embodiments should not be construed as requiring such separation in all embodiments, and it should be understood that the processes described Program components and systems can often be integrated together in a single software product, or packaged into multiple software products.

Thus, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. Furthermore, the processes depicted in the figures do not necessarily require the specific order shown, or sequential order, to achieve desirable results. In some implementations, multitasking and parallel processing may be advantageous.

The above are only preferred embodiments of this specification and are not intended to limit this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this specification shall be included in this specification. within the scope of protection.

Claims

A method of live migration of virtual machine instances, applied to cloud service equipment, characterized in that the cloud service equipment is equipped with microservice hardware, and the virtual machine instance to be migrated includes a virtual machine simulator process running on the microservice hardware and a virtual machine driver running in the operating system kernel carried by the cloud service device; the method includes:

In response to the virtual machine instance to be migrated meeting the hot migration conditions, the operating system kernel obtains the first running data of the virtual machine instance in the operating system kernel installed on the cloud service device, and transfers the first The running data is written into the preset memory space;

The virtual machine simulator process obtains the second operating data of the virtual machine instance on the microservice hardware and the third operating data of the virtual machine instance in the memory space of the cloud service device, and obtains the second operating data of the virtual machine instance on the microservice hardware and obtains the third operating data from the virtual machine instance. Read the first operating data from the preset memory space;

The virtual machine simulator process sends the obtained first operating data, the second operating data and the third operating data to the target cloud service device to migrate the virtual machine instance to the target. Cloud service equipment.
The method according to claim 1, characterized in that:

The thermal migration conditions include any of the following:

The value corresponding to the running indicator of the virtual machine instance reaches a preset threshold;

A live migration instruction for the virtual machine instance is received.
The method according to claim 1, characterized in that:

A service program for obtaining and storing the first operating data is implemented in the operating system kernel of the cloud service device; a callback function is registered in the operating system kernel of the cloud service device; the callback function is Automatically triggered when the virtual machine instance meets the live migration conditions to initiate a call to the service program;

The operating system kernel obtains the first running data of the virtual machine instance in the operating system kernel mounted on the cloud service device, and writes the first running data into the preset memory space, including:

In response to the virtual machine instance meeting the live migration conditions, the callback function is triggered to initiate a call to the service program to run the service program in the operating system kernel carried by the cloud service device. The program obtains the first running data of the virtual machine instance on the cloud service device, and writes the first running data into a preset memory space.
The method according to claim 1, characterized in that:

The preset memory area includes reserved memory space applied from the memory space of the cloud server device corresponding to the virtual machine instance when the virtual machine instance is created.
The method according to claim 1, characterized in that:

The first operating data includes:

The virtual CPU status data and virtual device status data of the virtual machine instance on the cloud service device;

The second operating data includes:

The virtual device status data of the virtual machine instance on the microservice hardware;

The third operating data includes:

The virtual machine instance writes data in the memory space corresponding to the virtual machine instance.
The method according to claim 1, characterized in that:

Before the virtual machine simulator process sends the obtained first operation data, the second operation data and the third operation data to the target cloud service device, it also includes:

Obtain the cloud service equipment currently in normal status;

A target cloud service device as the migrated party is allocated from the cloud service devices in the normal state.
The method according to claim 1, characterized in that:

The microservice hardware includes microservice cards.
The method according to claim 1, characterized in that:

The virtual machine instance includes a KVM virtual machine instance;

The virtual machine emulator process includes a QEMU process.
A device for hot migration of virtual machine instances, applied to cloud service equipment, characterized in that the cloud service equipment is equipped with microservice hardware, and the virtual machine instance to be migrated includes a virtual machine simulator process running on the microservice hardware and a virtual machine driver running in the operating system kernel carried by the cloud service device; the device includes:

A first acquisition unit configured to obtain, by the operating system kernel, the first operating data of the virtual machine instance in the operating system kernel installed on the cloud service device in response to the virtual machine instance to be migrated meeting the hot migration conditions. , and write the first operating data into the preset memory space;

A second acquisition unit configured to acquire, through the virtual machine simulator process, the second running data of the virtual machine instance on the microservice hardware and the memory space of the virtual machine instance in the cloud service device. third operating data, and reading the first operating data from the preset memory space;

A data sending unit, configured to send the acquired first running data, the second running data and the third running data to a target cloud service device by the virtual machine simulator process, so as to send the virtual machine simulator to the target cloud service device. Migrate the machine instance to the target cloud service device.
A system, characterized in that the system includes: a source cloud service device and a target cloud service device;

The source cloud service device is equipped with source microservice hardware. The virtual machine instance to be migrated includes a virtual machine simulator process running on the microservice hardware and a virtual machine running in the operating system kernel installed on the source cloud service device. drive;

The source cloud service device is configured to: in response to the virtual machine instance to be migrated meeting the hot migration condition, the operating system kernel obtains the virtual machine instance in the operating system kernel installed on the source cloud service device. a running data, and writes the first running data into a preset memory space; the virtual machine simulator process obtains the second running data of the virtual machine instance on the source microservice hardware and the virtual The third running data of the machine instance in the memory space of the source cloud service device, and reads the first running data from the preset memory space; the virtual machine simulator process will obtain all the The first operating data, the second operating data and the third operating data are sent to the target cloud service device to migrate the virtual machine instance to the target cloud service device;

The target cloud service device is equipped with target microservice hardware;

The target cloud service device is configured to: in response to the virtual machine instance to be migrated satisfying the live migration condition, Receive the first operating data, the second operating data and the third operating data sent by the source cloud service device; create a virtual machine instance according to the received operating data, the virtual machine instance includes running on The virtual machine simulator process on the target microservice hardware and the virtual machine driver running in the operating system kernel carried by the target cloud service device are used to complete the migration of the virtual machine instance from the source cloud service device to the target cloud service device.
A storage medium, characterized in that a computer program is stored thereon, and when the computer program is executed, the steps of the method according to any one of claims 1-8 are implemented.
A computer device, characterized in that it includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following method when executing the program: wherein, the processing When the program is executed by a computer, the method according to any one of claims 1-8 is implemented.