Virtual machine migration method and related device

US12561159B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12561159-B2
Application numberUS-202217945864-A
CountryUS
Kind codeB2
Filing dateSep 15, 2022
Priority dateMar 16, 2020
Publication dateFeb 24, 2026
Grant dateFeb 24, 2026

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Embodiments of this application disclose a virtual machine migration method. One example method includes: indicating, by a controller, a proxy virtual machine to mount a volume; replacing, by using the proxy virtual machine, a driver of an original platform in the volume with a driver of a target platform; and then, mounting a replaced volume to a target virtual machine.

First claim

Opening claim text (preview).

What is claimed is: 1 . A virtual machine migration method, comprising: indicating, by a controller, a proxy virtual machine to mount a volume, wherein the volume comprises a first driver used to run the volume on an original platform; indicating, by the controller, the proxy virtual machine to replace the first driver in the volume with a second driver by injecting the second driver into the volume, wherein the first driver is a driver for running the volume on the original platform, and the second driver is a driver for running the volume on a target platform; indicating, by the controller, the target platform to mount a replaced volume to a target virtual machine; and cancelling a first operation permission for the volume on the original platform in response to the replaced volume having been mounted to the target virtual machine. 2 . The method according to claim 1 , wherein the method further comprises: indicating, by the controller, the target platform to obtain management information of an original virtual machine. 3 . The method according to claim 2 , wherein the method further comprises: indicating, by the controller, the target platform to create the target virtual machine based on the management information of the original virtual machine, wherein the original virtual machine is located on the original platform. 4 . The method according to claim 1 , wherein the method further comprises: indicating, by the controller, the proxy virtual machine to unmount the replaced volume. 5 . The method according to claim 1 , wherein the indicating, by a controller, a proxy virtual machine to mount a volume comprises: indicating, by the controller, the proxy virtual machine to mount a plurality of volumes, wherein the plurality of volumes belong to a plurality of virtual machines on the original platform; the indicating, by the controller, the proxy virtual machine to replace the first driver in the volume with a second driver comprises: indicating, by the controller, the proxy virtual machine to replace a first driver in each of the plurality of volumes with a second driver; and the indicating, by the controller, the target platform to mount a replaced volume to a target virtual machine comprises: indicating, by the controller, the target platform to respectively mount a plurality of replaced volumes to a plurality of target virtual machines. 6 . The method according to claim 1 , wherein the method further comprises: indicating, by the controller, the target platform to take a snapshot of the volume; and indicating, by the controller, the target platform to roll back the snapshot. 7 . The method according to claim 1 , wherein the method further comprises: indicating, by the controller, the original platform to set an operation permission for the volume. 8 . The method according to claim 1 , wherein the original platform is an open-source code virtual machine monitor (XEN) platform, and the target platform is a kernel-based virtual machine (KVM) platform. 9 . A controller, comprising: at least one processor; and one or more memories coupled to the at least one processor and storing programming instructions for execution by the at least one processor to cause the controller to: indicate a proxy virtual machine to mount a volume, wherein the volume comprises a first driver used to run the volume on an original platform; indicate the proxy virtual machine to replace the first driver in the volume with a second driver by injecting the second driver into the volume, wherein the first driver is a driver for running the volume on the original platform, and the second driver is a driver for running the volume on a target platform; indicate the target platform to mount a replaced volume to a target virtual machine; and cancel a first operation permission for the volume on the original platform in response to the replaced volume having been mounted to the target virtual machine. 10 . The controller according to claim 9 , wherein the programming instructions, when executed by the at least one processor, cause the controller to: indicate the target platform to obtain management information of an original virtual machine. 11 . The controller according to claim 10 , wherein the programming instructions, when executed by the at least one processor, cause the controller to: indicate the target platform to create the target virtual machine based on the management information of the original virtual machine, wherein the original virtual machine is located on the original platform. 12 . The controller according to claim 9 , wherein the programming instructions, when executed by the at least one processor, cause the controller to: indicate the proxy virtual machine to unmount the replaced volume. 13 . The controller according to claim 9 , wherein the programming instructions, when executed by the at least one processor, cause the controller to: indicate the proxy virtual machine to mount a plurality of volumes, wherein the plurality of volumes belong to a plurality of virtual machines on the original platform; indicate the proxy virtual machine to replace a first driver in each of the plurality of volumes with a second driver; and indicate the target platform to respectively mount a plurality of replaced volumes to a plurality of target virtual machines. 14 . The controller according to claim 9 , wherein the programming instructions, when executed by the at least one processor, cause the controller to: indicate the target platform to take a snapshot of the volume; and indicate the target platform to roll back the snapshot. 15 . The controller according to claim 9 , wherein the programming instructions, when executed by the at least one processor, cause the controller to: indicate the original platform to set an operation permission for the volume. 16 . The controller according to claim 9 , wherein the original platform is open-source code virtual machine monitor (XEN) platform, and the target platform is a kernel-based virtual machine (KVM) platform. 17 . A non-transitory computer storage medium, wherein the computer storage medium stores instructions, and when the instructions are run on a computer, the computer is enabled to: indicate a proxy virtual machine to mount a volume, wherein the volume comprises a first driver used to run the volume on an original platform; indicate the proxy virtual machine to replace the first driver in the volume with a second driver by injecting the second driver into the volume, wherein the first driver is a driver for running the volume on the original platform, and the second driver is a driver for running the volume on a target platform; indicate the target platform to mount a replaced volume to a target virtual machine; and cancel a first operation permission for the volume on the original platform in response to the replaced volume having been mounted to the target virtual machine. 18 . The computer storage medium according to claim 17 , wherein when the instructions are run on a computer, the computer is further enabled to: indicate the target platform to obtain management information of an original virtual machine; and indicate the target platform to create the target virtual machine based on the management information of the original virtual machine, wherein the original virtual machine is located on the original platform. 19 . The computer storage medium according to claim 17 , wherein when the instructions are run on a com

Assignees

Inventors

Classifications

  • involving virtual machines · CPC title

  • resumption being on a different machine, e.g. task migration, virtual machine migration (G06F9/5088 takes precedence) · CPC title

  • Creating, deleting, cloning virtual machine instances · CPC title

  • Configuring for operating with peripheral devices; Loading of device drivers · CPC title

  • Distribution of virtual machine instances; Migration and load balancing · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12561159B2 cover?
Embodiments of this application disclose a virtual machine migration method. One example method includes: indicating, by a controller, a proxy virtual machine to mount a volume; replacing, by using the proxy virtual machine, a driver of an original platform in the volume with a driver of a target platform; and then, mounting a replaced volume to a target virtual machine.
Who is the assignee on this patent?
Huawei Tech Co Ltd
What technology area does this patent fall under?
Primary CPC classification G06F9/45558. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Feb 24 2026 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).