CN112231051A - UEFI boot file management method and device of ARM system architecture - Google Patents
UEFI boot file management method and device of ARM system architecture Download PDFInfo
- Publication number
- CN112231051A CN112231051A CN202011045556.4A CN202011045556A CN112231051A CN 112231051 A CN112231051 A CN 112231051A CN 202011045556 A CN202011045556 A CN 202011045556A CN 112231051 A CN112231051 A CN 112231051A
- Authority
- CN
- China
- Prior art keywords
- uefi boot
- boot file
- virtual machine
- uefi
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims abstract description 17
- 230000008676 import Effects 0.000 claims description 28
- 238000000034 method Methods 0.000 claims description 18
- 230000001360 synchronised effect Effects 0.000 claims description 10
- 238000001514 detection method Methods 0.000 claims description 4
- 230000001680 brushing effect Effects 0.000 claims description 3
- 238000004140 cleaning Methods 0.000 claims description 3
- 238000010367 cloning Methods 0.000 claims description 3
- 238000012544 monitoring process Methods 0.000 claims description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000013486 operation strategy Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a UEFI (unified extensible firmware interface) boot file management method and device of an ARM (advanced RISC machines) system architecture, wherein when a virtual machine migrates across hosts, whether a UEFI boot file exists on a target host is detected; if the UEFI boot file does not exist, distributing the UEFI boot file on the original host to the target host; if the UEFI boot file exists, judging whether the UEFI boot file is the same as the UEFI boot file on the original host; and if the difference is not the same, synchronizing the UEFI boot file on the original host to the target host. The invention avoids setting other configuration files again, thereby ensuring that the virtual machine can automatically guide, reducing the workload and improving the working efficiency.
Description
Technical Field
The invention relates to the field of an ARM system architecture UEFI boot file, in particular to a management method and a device of the ARM system architecture UEFI boot file.
Background
In recent years, the operating system of the server based on the ARM architecture and the related application software have become more mature, and the business requirements in most application scenarios can be met at present. However, when the virtual machines deployed in the server based on the ARM framework perform UEFI boot, it is found that the UEFI boot file writes data in real time during each installation, and when the virtual machines with the same configuration have different disk data and use the same boot file, the virtual machines cannot automatically boot, so that each virtual machine needs to have a separate configuration file, the workload is greatly increased, and the working efficiency is affected.
Disclosure of Invention
In order to solve the above problems, the present invention provides a UEFI boot file management method and apparatus for ARM system architecture.
The technical scheme of the invention is as follows: a UEFI boot file management method of an ARM system architecture comprises the following steps:
when the virtual machine migrates across hosts, detecting whether UEFI boot files exist on a target host or not;
if the UEFI boot file does not exist, distributing the UEFI boot file on the original host to the target host;
if the UEFI boot file exists, judging whether the UEFI boot file is the same as the UEFI boot file on the original host;
and if the difference is not the same, synchronizing the UEFI boot file on the original host to the target host.
Further, synchronizing the UEFI boot file on the original host to the target host specifically:
initializing a synchronous IO structural body;
cloning a structure body to a synchronous data set aiming at the UEFI boot file;
setting a corresponding bitmap for a write data block;
a wakeup daemon sends a write request;
synchronously brushing the disk by the bitmap;
and (4) finishing UEFI boot file synchronization by data landing.
Further, the method further comprises:
when the virtual machine is cloned, snapshotted, backed up and deployed on the original host, the UEFI boot file of the original virtual machine is copied and associated with the new virtual machine.
Further, the method further comprises:
when the virtual machine carries out export operation, exporting the direct import file of the virtual machine together with the UEFI boot file;
and when the virtual machine performs the import operation, judging whether the direct import file and the UEFI boot file exist under the path, and if so, continuing the import operation.
Further, the method further comprises:
and when the virtual machine is deleted or migrated to other hosts, deleting the residual UEFI boot files.
The technical scheme of the invention also comprises an ARM system architecture UEFI boot file management device, which comprises,
the management scheduling module: monitoring the operation of the virtual machine, and triggering a corresponding UEFI boot file processing strategy according to the operation of the virtual machine;
a difference detection module: when the virtual machine migrates across hosts, detecting whether a UEFI (unified extensible firmware interface) boot file exists on a target host, and if the UEFI boot file exists, detecting whether the UEFI boot file on the target host is the same as the UEFI boot file on the original host;
a distribution module: when the UEFI boot file does not exist on the target host, distributing the UEFI boot file on the original host to the target host;
a synchronization module: and when the UEFI boot file is on the target host and is different from the UEFI boot file on the original host, synchronizing the UEFI boot file on the original host to the target host.
Further, when the virtual machine is cloned, snapshot, backed up and deployed on the original host, the distribution module copies the UEFI boot file of the original virtual machine and associates the UEFI boot file with the new virtual machine.
Further, the method also comprises the following steps of,
and an import and export module: when the virtual machine carries out export operation, exporting the direct import file of the virtual machine together with the UEFI boot file; and when the virtual machine performs the import operation, judging whether the direct import file and the UEFI boot file exist under the path, and if so, continuing the import operation.
Further, the method also comprises the following steps of,
a cleaning module: and when the virtual machine is deleted or migrated to other hosts, deleting the residual UEFI boot files.
According to the UEFI boot file management method and device for the ARM system architecture, when the virtual machine is migrated across hosts, UEFI boot files on the original host are distributed or synchronized on the target host, and other configuration files are prevented from being set again, so that automatic boot of the virtual machine is guaranteed, workload is reduced, and working efficiency is improved.
Drawings
FIG. 1 is a schematic flow chart of a method according to an embodiment of the present invention;
fig. 2 is a schematic block diagram of a second structure according to an embodiment of the present invention.
Detailed Description
The present invention will be described in detail below with reference to the accompanying drawings by way of specific examples, which are illustrative of the present invention and are not limited to the following embodiments.
Example one
As shown in fig. 1, the present embodiment provides a UEFI boot file management method for ARM system architecture, which includes the following steps:
s1, when the virtual machine migrates across the hosts, detecting whether a Unified Extensible Firmware Interface (UEFI) boot file exists on the target host or not;
s2, if the UEFI boot file does not exist, distributing the UEFI boot file on the original host to the target host;
specifically, a UEFI boot file is copied on an original host, then a port is opened on a target host, the copied file is copied to the target host through connection established by the port, then the port is closed, and a configuration file is bound with a new virtual machine.
S3, if the UEFI boot file exists, judging whether the UEFI boot file is the same as the UEFI boot file on the original host;
specifically, whether the boot files of the virtual machines between two different hosts are consistent or not is judged through an interface of libvirt.
S4, if not, synchronizing the UEFI boot file on the original host to the target host;
the UEFI boot file on the original host is synchronized to the target host, and the method specifically comprises the following steps:
initializing a synchronous IO (input output) structure;
cloning a structure body to a synchronous data set aiming at the UEFI boot file;
setting a corresponding bitmap (bitmap) for a write data block;
a wakeup daemon sends a write request;
synchronously brushing the disk by the bitmap;
and (4) finishing UEFI boot file synchronization by data landing.
In the synchronization process, a data synchronization request is managed by defining a synchronization io structure, the reliability and the consistency of data are ensured through bitmap in the writing process, and in an abnormal scene, incremental synchronization can be realized through bitmap.
Preferably, when the virtual machine is deleted or migrated to other hosts, the residual UEFI boot file is deleted.
In addition, the method further comprises a relevant operation strategy and an import and export strategy of the virtual machine on the original host, and the method specifically comprises the following steps:
when the virtual machine is cloned, snapshotted, backed up and deployed on a template on an original host, copying a UEFI boot file of the original virtual machine and associating the UEFI boot file with a new virtual machine;
when the virtual machine carries out export operation, exporting a direct import file (ova file) of the virtual machine together with a UEFI boot file;
and when the virtual machine performs the import operation, judging whether the direct import file and the UEFI boot file exist under the path, and if so, continuing the import operation.
Example two
As shown in fig. 2, the present embodiment provides an ARM system architecture UEFI boot file management apparatus, which includes the following functional modules.
The management scheduling module 1: monitoring the operation of the virtual machine, and triggering a corresponding UEFI boot file processing strategy according to the operation of the virtual machine;
when a new virtual machine uses a UEFI boot mode, the system writes a 64M fd suffix RAW format file, the file is responsible for booting the virtual machine when starting up and entering the system, the file is used as a source file, and the file is uniquely bound with the virtual machine through id.
The difference detection module 2: when the virtual machine migrates across hosts, detecting whether a UEFI (unified extensible firmware interface) boot file exists on a target host, and if the UEFI boot file exists, detecting whether the UEFI boot file on the target host is the same as the UEFI boot file on the original host;
the module judges whether the boot files of the virtual machines between two different hosts are consistent or not through an interface of libvirt.
The distribution module 3: when the UEFI boot file does not exist on the target host, distributing the UEFI boot file on the original host to the target host;
it should be noted that, when the virtual machine is cloned, snapshotted, backed up, and deployed as a template on the original host, the distribution module 3 copies the UEFI boot file of the original virtual machine and associates the UEFI boot file with the new virtual machine.
Specifically, when the target host is the same as the original host, the file is directly copied and renamed; when the hosts are different, firstly opening a port at the target host, then copying the file to the target host through the connection established by the port, then closing the port, and binding the configuration file with the new virtual machine.
The synchronization module 4: when the UEFI boot file is on the target host and is different from the UEFI boot file on the original host, synchronizing the UEFI boot file on the original host to the target host;
when the difference detection module detects that the two UEFI boot files have difference, the difference data of the two boot files needs to be synchronized. The data synchronization request is managed by defining the synchronization io structure, the reliability and the consistency of data are guaranteed through bitmap in the writing process, and increment synchronization can be achieved through bitmap in an abnormal scene.
The import/export module 5: when the virtual machine carries out export operation, exporting a direct import file (ova file) of the virtual machine together with a UEFI boot file; when the virtual machine conducts import operation, whether the direct import file and the UEFI boot file which are the same exist under the path or not is judged, and if yes, the import operation is continued;
the module can export the ova file and the UEFI boot file of the virtual machine together, and the command mode uniformly adopts the mode of virtual machine ID + timestamp; and when the virtual machine is imported, judging whether corresponding ova and UEFI boot file information exist under the path, and continuing the operation of importing the virtual machine when the ova and the UEFI boot file information correspond to each other.
Cleaning module 6: and when the virtual machine is deleted or migrated to other hosts, deleting the residual UEFI boot files.
The above disclosure is only for the preferred embodiments of the present invention, but the present invention is not limited thereto, and any non-inventive changes that can be made by those skilled in the art and several modifications and amendments made without departing from the principle of the present invention shall fall within the protection scope of the present invention.
Claims (9)
1. A UEFI boot file management method of an ARM system architecture is characterized by comprising the following steps:
when the virtual machine migrates across hosts, detecting whether UEFI boot files exist on a target host or not;
if the UEFI boot file does not exist, distributing the UEFI boot file on the original host to the target host;
if the UEFI boot file exists, judging whether the UEFI boot file is the same as the UEFI boot file on the original host;
and if the difference is not the same, synchronizing the UEFI boot file on the original host to the target host.
2. The method for managing UEFI boot files of ARM system architecture according to claim 1, wherein UEFI boot files on the original host are synchronized to the target host, specifically:
initializing a synchronous IO structural body;
cloning a structure body to a synchronous data set aiming at the UEFI boot file;
setting a corresponding bitmap for a write data block;
a wakeup daemon sends a write request;
synchronously brushing the disk by the bitmap;
and (4) finishing UEFI boot file synchronization by data landing.
3. The method for managing UEFI boot files of ARM system architecture according to claim 1 or 2, further comprising:
when the virtual machine is cloned, snapshotted, backed up and deployed on the original host, the UEFI boot file of the original virtual machine is copied and associated with the new virtual machine.
4. The method of claim 3, wherein the method further comprises:
when the virtual machine carries out export operation, exporting the direct import file of the virtual machine together with the UEFI boot file;
and when the virtual machine performs the import operation, judging whether the direct import file and the UEFI boot file exist under the path, and if so, continuing the import operation.
5. The method of claim 4, wherein the method further comprises:
and when the virtual machine is deleted or migrated to other hosts, deleting the residual UEFI boot files.
6. A UEFI boot file management device of ARM system architecture is characterized by comprising,
the management scheduling module: monitoring the operation of the virtual machine, and triggering a corresponding UEFI boot file processing strategy according to the operation of the virtual machine;
a difference detection module: when the virtual machine migrates across hosts, detecting whether a UEFI (unified extensible firmware interface) boot file exists on a target host, and if the UEFI boot file exists, detecting whether the UEFI boot file on the target host is the same as the UEFI boot file on the original host;
a distribution module: when the UEFI boot file does not exist on the target host, distributing the UEFI boot file on the original host to the target host;
a synchronization module: and when the UEFI boot file is on the target host and is different from the UEFI boot file on the original host, synchronizing the UEFI boot file on the original host to the target host.
7. The apparatus of claim 6, wherein when the virtual machine is cloned, snapshotted, backed up, and deployed on the original host, the distribution module copies the UEFI boot file of the original virtual machine to one copy and associates the UEFI boot file with the new virtual machine.
8. The ARM system architecture UEFI boot file management apparatus of claim 7, further comprising,
and an import and export module: when the virtual machine carries out export operation, exporting the direct import file of the virtual machine together with the UEFI boot file; and when the virtual machine performs the import operation, judging whether the direct import file and the UEFI boot file exist under the path, and if so, continuing the import operation.
9. The ARM system architecture UEFI boot file management apparatus of claim 8, further comprising,
a cleaning module: and when the virtual machine is deleted or migrated to other hosts, deleting the residual UEFI boot files.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011045556.4A CN112231051B (en) | 2020-09-28 | 2020-09-28 | UEFI boot file management method and device of ARM system architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011045556.4A CN112231051B (en) | 2020-09-28 | 2020-09-28 | UEFI boot file management method and device of ARM system architecture |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112231051A true CN112231051A (en) | 2021-01-15 |
| CN112231051B CN112231051B (en) | 2022-05-31 |
Family
ID=74121128
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011045556.4A Active CN112231051B (en) | 2020-09-28 | 2020-09-28 | UEFI boot file management method and device of ARM system architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112231051B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104572061A (en) * | 2014-03-21 | 2015-04-29 | 中电科技（北京）有限公司 | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Loongson server |
| CN104660660A (en) * | 2013-11-25 | 2015-05-27 | 英业达科技有限公司 | Cloud platform application method and system |
| CN107656797A (en) * | 2017-09-27 | 2018-02-02 | 郑州云海信息技术有限公司 | The method and apparatus of across virtual platform migration virtual machine |
| US20180060077A1 (en) * | 2016-08-26 | 2018-03-01 | Qualcomm Incorporated | Trusted platform module support on reduced instruction set computing architectures |
-
2020
- 2020-09-28 CN CN202011045556.4A patent/CN112231051B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104660660A (en) * | 2013-11-25 | 2015-05-27 | 英业达科技有限公司 | Cloud platform application method and system |
| CN104572061A (en) * | 2014-03-21 | 2015-04-29 | 中电科技（北京）有限公司 | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Loongson server |
| US20180060077A1 (en) * | 2016-08-26 | 2018-03-01 | Qualcomm Incorporated | Trusted platform module support on reduced instruction set computing architectures |
| CN107656797A (en) * | 2017-09-27 | 2018-02-02 | 郑州云海信息技术有限公司 | The method and apparatus of across virtual platform migration virtual machine |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112231051B (en) | 2022-05-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11604708B2 (en) | Memory first live snapshot | |
| US9460028B1 (en) | Non-disruptive and minimally disruptive data migration in active-active clusters | |
| US8326803B1 (en) | Change tracking of individual virtual disk files | |
| AU2012273366B2 (en) | Managing replicated virtual storage at recovery sites | |
| US9852198B1 (en) | Method and system for fast generation of file system snapshot bitmap in virtual environment | |
| US9400611B1 (en) | Data migration in cluster environment using host copy and changed block tracking | |
| CN103970585B (en) | Create the method and device of virtual machine | |
| CN110851302B (en) | Database information backup method and database information recovery method | |
| US9501231B2 (en) | Storage system and storage control method | |
| US8732128B2 (en) | Shadow copy bookmark generation | |
| US11947429B2 (en) | Data disaster recovery method and site | |
| US20140208012A1 (en) | Virtual disk replication using log files | |
| JP4419884B2 (en) | Data replication apparatus, method, program, and storage system | |
| US20110066879A1 (en) | Virtual machine system, restarting method of virtual machine and system | |
| CN102200941A (en) | Method and unit for monitoring process state | |
| JP4883986B2 (en) | Computer system, management computer, and data recovery method | |
| CN102193813A (en) | Embedded type virtualized quick start method and system | |
| CN110837441A (en) | KVM virtual machine backup method based on dirty data bitmap and network block equipment | |
| CN108255643A (en) | A kind of continuous data protection method of no agency | |
| US11307934B1 (en) | Virtual backup and restore of virtual machines | |
| CN115729749A (en) | Data backup method and system | |
| CN112231051B (en) | UEFI boot file management method and device of ARM system architecture | |
| CN103327112A (en) | Desktop synchronization method based on cloud storage and device for realizing desktop synchronization | |
| CN105488139B (en) | The method of cross-platform storing data migration based on power information acquisition system | |
| CN114490570A (en) | Production data synchronization method and device, data synchronization system and server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |