CN108509252B - Virtual machine starting device and method and host - Google Patents
Virtual machine starting device and method and host Download PDFInfo
- Publication number
- CN108509252B CN108509252B CN201810251730.7A CN201810251730A CN108509252B CN 108509252 B CN108509252 B CN 108509252B CN 201810251730 A CN201810251730 A CN 201810251730A CN 108509252 B CN108509252 B CN 108509252B
- Authority
- CN
- China
- Prior art keywords
- virtual machine
- virtual disk
- disk file
- size value
- virtual
- 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.)
- Active
Links
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
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/062—Securing storage systems
- G06F3/0623—Securing storage systems in relation to content
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
- G06F3/0643—Management of files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0662—Virtualisation aspects
- G06F3/0664—Virtualisation aspects at device level, e.g. emulation of a storage device or system
-
- 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/45575—Starting, stopping, suspending or resuming 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/45579—I/O management, e.g. providing access to device drivers or storage
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a virtual machine starting device, a virtual machine starting method and a host, wherein the virtual machine starting device and the virtual machine starting method are applied to each host in communication connection with a storage device, at least one virtual machine is deployed in each host, and a virtual disk file for starting the virtual machine is stored in the storage device. The device includes: the virtual machine starting module is used for acquiring a virtual disk size value recorded in header information of a target virtual disk file when executing a starting instruction for starting any virtual machine through the target virtual disk file, and starting the virtual machine through the target virtual disk file when the virtual disk size value is larger than a preset threshold value; and the header information modification module is used for modifying the virtual disk size value recorded in the header information of the virtual machine into a preset size value when the virtual machine is successfully started through the target virtual disk file, so as to prevent other virtual machines from being started through the target virtual disk file.
Description
Technical Field
The present application relates to the field of virtual machine technologies, and in particular, to a virtual machine starting apparatus, a virtual machine starting method, and a host.
Background
Currently, multiple hosts are typically communicatively connected to a dedicated storage device (e.g., shared storage), and a virtual machine deployed in each host may be started via a virtual disk file stored in the storage device. However, each host can read and write files in the storage device, so that the situation that different virtual machines use the same virtual disk file at the same time and then read and write the virtual disk file at the same time is easy to occur, and data of the virtual disk file is disturbed or even damaged.
Disclosure of Invention
In view of the above, an object of the present invention is to provide a virtual machine booting apparatus, a method and a host to improve the above problems.
In order to achieve the above object, an embodiment of the present application provides a virtual machine starting apparatus, which is applied to each host communicatively connected to a storage device, where at least one virtual machine is deployed in each host, and a virtual disk file for starting the virtual machine is stored in the storage device; the device comprises:
the virtual machine starting module is used for acquiring a virtual disk size value recorded in header information of a target virtual disk file when executing a starting instruction for starting any virtual machine through the target virtual disk file, and starting the virtual machine through the target virtual disk file when the virtual disk size value is larger than a preset threshold value;
and the header information modification module is used for modifying the virtual disk size value recorded in the header information of the target virtual disk file into a preset size value when the virtual machine is successfully started through the target virtual disk file, so as to prevent other virtual machines from being started through the target virtual disk file.
Optionally, the storage device records an actual size value of the target virtual disk file, and the virtual machine starting apparatus further includes:
the recording module is used for acquiring the identification information of the virtual machine when the virtual machine is successfully started through the target virtual disk file and the identification information of the virtual machine is not recorded in the storage device, and recording the identification information in a preset storage position corresponding to the target virtual disk file in the storage device;
the identification information acquisition module is used for acquiring the identification information stored in the preset storage position when the size value of the virtual disk acquired by the virtual machine starting module is not larger than the preset threshold value;
and the restarting module is used for acquiring the actual size value of the target virtual disk file from the storage device when the acquired identification information comprises the identification information of the virtual machine, recovering the virtual disk size value recorded in the header information of the target virtual disk file to the actual size value, and executing a starting instruction for starting the virtual machine through the target virtual disk file again.
Optionally, the virtual machine starting apparatus further includes:
the starting prompting module is used for outputting prompting information to prompt that the virtual machine cannot be started through the target virtual disk file when the obtained identification information does not include the identification information of the virtual machine;
and the forced starting module is used for acquiring the actual size value of the target virtual disk file from the storage equipment, restoring the virtual disk size value recorded in the header information of the target virtual disk file to the actual size value and executing the starting instruction when receiving the starting instruction input again by the user after the prompt information is output and starting the target virtual disk file.
Optionally, the recording module is further configured to, when the virtual machine is successfully started through the target virtual disk file, obtain the virtual disk size value before the header information modification module modifies the virtual disk size value recorded in the header information of the target virtual disk file to a preset size value, and record the virtual disk size value as the actual size value of the target virtual disk file in the preset storage location.
Optionally, the virtual boot apparatus further includes:
the first deleting module is used for deleting the identification information of any virtual machine in the storage equipment when the virtual machine is closed or deleted; and/or
And the second deleting module is used for deleting the identification information of the virtual machine in a preset storage position corresponding to the virtual disk file in the storage equipment when a deleting instruction for deleting the virtual disk file in any virtual machine is received.
The embodiment of the application further provides a virtual machine starting method, which is applied to each host machine in communication connection with the storage device, wherein at least one virtual machine is deployed in each host machine, and the storage device stores a virtual disk file for starting the virtual machine; the method comprises the following steps:
when a starting instruction for starting any virtual machine through a target virtual disk file is executed, acquiring a virtual disk size value recorded in header information of the target virtual disk file, and when the virtual disk size value is larger than a preset threshold value, starting the virtual machine through the target virtual disk file;
and when the virtual machine is successfully started through the target disk file, modifying the virtual disk size value recorded in the header information of the target virtual disk file into a preset size value so as to prevent other virtual machines from being started through the target virtual disk file.
Optionally, the storage device records an actual size value of the target virtual disk file, and the virtual machine starting method further includes:
when the virtual machine is successfully started through the target virtual disk file and the identification information of the virtual machine is not recorded in the storage equipment, acquiring the identification information of the virtual machine and recording the identification information in a preset storage position corresponding to the target virtual disk file in the storage equipment;
when the size value of the obtained virtual disk is not larger than the preset threshold value, obtaining identification information stored in the preset storage position;
when the acquired identification information includes the identification information of the virtual machine, acquiring the actual size value of the target virtual disk file from the storage device, restoring the virtual disk size value recorded in the header information of the target virtual disk file to the actual size value, and re-executing a start instruction for starting the virtual machine through the target virtual disk file.
When the obtained identification information does not include the identification information of the virtual machine, outputting prompt information to prompt that the virtual machine cannot be started through the target virtual disk file;
when a starting instruction input again by the user after the prompt information is output is received to start through the target virtual disk file, acquiring the actual size value of the target virtual disk file from the preset storage position, restoring the virtual disk size value recorded in the header information of the target virtual disk file to the actual size value, and executing the starting instruction.
Optionally, when the virtual machine is successfully started through the target disk file, the virtual machine starting method further includes:
and before the virtual disk size value recorded in the header information of the target virtual disk file is modified to a preset size value, acquiring the virtual disk size value, and recording the virtual disk size value as the actual size value of the target virtual disk file in the preset storage position.
Optionally, the virtual machine starting method further includes:
when any virtual machine is closed or deleted, deleting the identification information of the virtual machine in the storage equipment; and/or
When a deleting instruction for deleting the virtual disk file in any virtual machine is received, the identification information of the virtual machine is deleted in a preset storage position corresponding to the virtual disk file in the storage equipment.
The embodiment of the application also provides a host which is in communication connection with the storage device, wherein at least one virtual machine is deployed in the host, and the storage device stores a virtual disk file for starting the virtual machine;
the host comprises a memory, a processor and a virtual machine starting device provided by the embodiment of the application, wherein the virtual machine starting device is stored in the memory and is controlled by the processor to execute.
The embodiment of the present application further provides a storage medium, on which computer readable instructions are stored, and when the computer readable instructions are executed, the virtual machine starting method provided by the embodiment of the present application is implemented.
Compared with the prior art, the embodiment of the application has the following beneficial effects:
in the device, the method and the host for starting the virtual machine provided by the embodiment of the application, at least one virtual machine is deployed in each host which is in communication connection with the storage device, and the virtual disk file for starting the virtual machine is stored in the storage device. Each host comprises a virtual machine starting module and a header information modification module; the virtual machine starting module is used for acquiring a virtual disk size value recorded in header information of a target virtual disk file when executing a starting instruction for starting any virtual machine through the target virtual disk file, and starting the virtual machine through the target virtual disk file when the virtual disk size value is larger than a preset threshold value; the header information modification module is used for modifying the virtual disk size value recorded in the header information of the target virtual disk file into a preset size value when the virtual machine is successfully started through the target virtual disk file, so as to prevent other virtual machines from being started through the target virtual disk file. Therefore, the method can effectively prevent different virtual machines from using the same virtual disk file at the same time, thereby preventing the data of the virtual disk file from being damaged.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
FIG. 1 is a schematic diagram illustrating a communication between a host and a storage device according to an embodiment of the present disclosure;
fig. 2 is a schematic block diagram of a host according to an embodiment of the present disclosure;
fig. 3 is a schematic block diagram of a virtual machine starting apparatus according to an embodiment of the present disclosure;
FIG. 4 is a schematic diagram illustrating a communication between a host and a storage device according to an embodiment of the present application;
fig. 5 is a flowchart illustrating a virtual machine starting method according to an embodiment of the present application.
Icon: 10-starting a system by a virtual machine; 100-a storage device; 200-a host; 210-a memory; 220-a processor; 230-a communication unit; 300-a host; 400-virtual machine startup device; 410-a virtual machine start module; 420-a header information modification module; 430-a recording module; 440-an identification information acquisition module; 450-restart module; 460-start the prompt module; 470-forced start module; 480-a first deletion module; 490-second delete module.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
As shown in fig. 1, a virtual machine boot system 10 according to an embodiment of the present disclosure is provided, where the virtual machine boot system 10 includes a storage device 100 and at least two hosts (e.g., a host 200 and a host 300 in fig. 1) communicatively connected to the storage device 100 through a network. At least one virtual machine is deployed in each host communicatively connected to the storage apparatus 100, and the storage apparatus 100 stores therein a virtual disk file for starting the virtual machine in each host.
The host in this embodiment refers to a host on which a virtual machine runs. The virtual disk file in this embodiment may be a file in vmx format, or may also be a file in qcow2 format, which is not limited in this embodiment.
The storage device 100 may be an independent storage server or a server cluster composed of a plurality of storage servers, and a corresponding storage system (e.g., a shared file system) is built on the storage device 100 for the at least two hosts to access.
In this case, the at least two hosts may both read and write files in the storage device 100, that is, different virtual machines may use the same virtual disk file at the same time, and then read and write the same virtual disk file at the same time, which may easily cause data disorder and even damage of the virtual disk file.
Accordingly, embodiments of the present application provide a virtual machine starting apparatus, a virtual machine starting method, and a host, so as to improve the above problem. This is explained in detail below with reference to the figures.
Fig. 2 is a block diagram of a host 200 according to an embodiment of the present disclosure, in which the host 200 includes a virtual machine boot apparatus 400, a memory 210, and a processor 220.
The memory 210 and the processor 220 are electrically connected to each other directly or indirectly, so as to realize data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The memory 210 includes software functional modules stored in firmware or software (software), and the processor 220 implements a corresponding functional application or data processing by executing the executable modules in the memory 210. For example, the virtual machine startup device 400 may be stored in the memory 210 and controlled to execute by the processor 220.
It should be understood that the structure shown in fig. 2 is only an illustration, and the host 200 may further include fewer or more components than those shown in fig. 2, for example, the host 200 may further include a communication unit 230 for establishing a communication connection with the storage device 100; for another example, after the host 200 starts any virtual machine through the virtual disk file in the storage device 100, the host 200 may further include a corresponding virtual machine.
In addition, the host 200 may also have a completely different configuration from that shown in fig. 2. It should be noted that, the components shown in fig. 2 may be implemented by software, hardware or a combination thereof, and the embodiment is not limited thereto.
In this embodiment, the host 300, the host 400 and other hosts have similar components to the host 200, and the connection relationship between the components is also similar, which is not described herein again.
As shown in fig. 3, the functional block diagram of a virtual machine startup device 400 provided in this embodiment of the present application is a functional block diagram, where the virtual machine startup device 400 is applied to each host communicatively connected to the storage apparatus 100 in fig. 1. The virtual machine starting apparatus 400 includes a virtual machine starting module 410 and a header information modification module 420.
The virtual machine starting module 410 is configured to, when a starting instruction for starting any virtual machine through a target virtual disk file is executed, obtain a virtual disk size value recorded in header information of the target virtual disk file, and when the virtual disk size value is greater than a preset threshold, start the virtual machine through the target virtual disk file.
In this embodiment, the host may be managed by a management platform, and a user may perform operations related to the virtual machine on the host managed by the user through the management platform, for example, to create a new virtual machine, start the virtual machine, add or delete a virtual disk file to or from the virtual machine, and the like.
For any virtual machine, the target virtual disk file in this embodiment may be any virtual disk file selected and added by the user for the virtual machine in the storage device 100.
Taking the host 200 as an example, when a user inputs a start instruction for starting any virtual machine on the host 200 through a corresponding target virtual disk file on the management platform, the management platform sends a corresponding start command to the host 200, and the host 200 reads the target virtual disk file from the storage device 100 through a management tool thereon. The management tool runs on the host 200, and may invoke a corresponding drive, and the virtual disk file acquired from the storage device 100 may be parsed by the drive, for example, when the virtual disk file is a file in the qcow2 format, the management tool may be Libvirt, and Libvirt may invoke a qemu drive to parse a qcow2 file. In addition, the management tool can also acquire internal information of the virtual machine, operate files on the host 200, and the like.
The header information of the virtual disk file comprises a field virtual size used for storing the size of the virtual disk, and the value of the field is the virtual disk size value of the virtual disk file. In this embodiment, when reading the target virtual disk file, the management tool first reads the virtual disk size value of the target virtual disk file from the header information of the target virtual disk file. The inventor has found that, when the size of the virtual disk file is too small, the BIOS (Basic Input Output System) of the virtual machine cannot read the partition table of the virtual disk file normally, that is, cannot read the data on the virtual disk file, so that the operating System cannot be booted, and the virtual machine cannot be used normally. For a virtual machine that has not been installed with an operating system, if the virtual machine is started from a virtual disk file with a too small size value of a virtual disk, the BIOS of the virtual machine cannot normally create a partition table of the virtual disk file, and cannot read data on the virtual disk file, so that the operating system cannot be installed, and the virtual machine cannot be normally used. That is, when the virtual disk size value of the virtual disk file is not greater than the preset threshold, the virtual machine cannot be used normally.
The inventor finds, through multi-party statistical research, that when the virtual disk size value of the virtual disk file is less than or equal to 1M, the BIOS of the virtual machine cannot normally read or create the partition table of the virtual disk file. Therefore, in the present embodiment, the preset threshold may be 1M.
It should be noted that the start instruction may be a start instruction issued by the management platform according to a user operation, or may be a start instruction triggered when the host automatically restarts the virtual machine, which is not limited in this embodiment.
The header information modification module 420 is configured to modify a virtual disk size value recorded in header information of the target virtual disk file to a preset size value when the virtual machine is successfully started through the target virtual disk file, so as to prevent other virtual machines from being started through the target virtual disk file.
In this embodiment, the successful start of the virtual machine through the target virtual disk file may refer to when a management tool on the host detects a virtual machine process (e.g., a kvm process) corresponding to the virtual machine, and the detected virtual machine process includes path information of the target virtual disk file. Taking a kvm process as an example, after each virtual machine is successfully started, the kvm process of the virtual machine may exist on a host where the virtual machine is located, and the kvm process includes path information of a virtual disk file used by the virtual machine.
In implementation, when the virtual machine is successfully started through the target virtual disk file, the value currently recorded in the size field of the header information of the target virtual disk file is modified to be a preset size value. If the other virtual machines are to be started from the target virtual disk file, the preset size value is read from the header information of the target virtual disk file when a start instruction is executed, and the other virtual machines cannot be started from the target virtual disk file due to the fact that the preset size value is small.
It should be noted that the preset size value may be a smaller value, and when the virtual disk size value of the virtual disk file is the preset size value, the virtual machine cannot be started from the virtual disk file. The preset size value may be any value less than or equal to the preset threshold, for example, the preset size value may be 0, 0.5M, 1M, or the like.
Through the process, the situation that different virtual machines use the same virtual disk file at the same time can be effectively avoided, and data in the virtual disk file are further prevented from being damaged.
Further, the virtual machine startup device 400 provided in this embodiment sets the virtual disk size value in the target virtual disk file used by the virtual machine after the virtual machine is successfully started, and once another virtual machine needs to be started from the target virtual disk file, it is necessary to read the virtual disk size value. Therefore, no matter other virtual machines on the same host, or other hosts, or virtual machines on hosts in other host clusters, cannot use the target virtual disk file with the virtual machine.
However, in the existing method, it is usually limited on a management platform that manages a host cluster, and different virtual machines in the host cluster are prohibited from using the same virtual disk file at the same time. This approach cannot avoid different virtual machines in different host clusters using one virtual disk file at the same time.
In actual applications, a virtual machine may be started and shut down multiple times after being created. According to the above description, when a virtual machine is started through a target virtual disk file, the virtual disk size value of the target virtual disk file has been modified to a preset size value, and if the virtual machine needs to be started again from the target virtual disk file after being closed, the start will inevitably fail. Thus, each time the virtual machine is restarted after shutdown, the user is required to restart the virtual machine through corresponding manual settings.
Furthermore, in some cases, it is sometimes necessary for multiple virtual machines to use the same virtual disk file, for example, in a database application, a cluster of database virtual machines needs to use the same virtual disk file. Correspondingly, these virtual machines may also be started and shut down multiple times. Then, in the case where the virtual disk size value of the virtual disk file has been modified to a preset size value, it can only be started by the user through some manual settings. However, it is very inconvenient when the number of virtual machines in the virtual machine cluster is large or the number of repeated starts is large.
For the above situation, for a virtual machine that has been started from a target virtual disk file, an association relationship between the virtual machine and the target virtual disk file may be established. Correspondingly, the virtual machine starting apparatus 400 provided in the embodiment of the present application may further include a recording module 430, an identification information obtaining module 440, and a restarting module 450.
The recording module 430 is configured to, when the virtual machine is successfully started through the target virtual disk file and the storage device 100 does not record the identification information of the virtual machine, obtain the identification information of the virtual machine, and record the identification information in a preset storage location corresponding to the target virtual disk file in the storage device 100.
In this embodiment, the association between the virtual machine and the target virtual disk file may be implemented by storing the identification information of the virtual machine in a preset storage location corresponding to the target virtual disk file in the storage device 100.
In detail, when the virtual machine is started through the target virtual disk file, whether the storage device 100 stores the identification information of the virtual machine or not can be checked, if yes, the association relationship between the virtual machine and the target virtual disk file is established, and the establishment is not needed again; if not, indicating that the association relationship between the virtual machine and the target virtual disk file is not established, creating identification information of the virtual machine, where the identification information may include a name of the virtual machine, a name of a host where the virtual machine is located, and the like. Further, since hosts in different host clusters may have the same name, the identification information may also include an ip (internet protocol) address of the host where the virtual machine is located. And then, storing the newly-built identification information of the virtual machine to the preset storage position.
The preset storage location corresponding to the target virtual disk file may be a file associated with the target virtual disk file in the storage device 100, for example, a file having the same suffix name as the target virtual disk file; it may also be a reserved field in the target virtual disk file.
The identification information obtaining module 440 obtains the identification information stored in the preset storage location when the size value of the virtual disk obtained by the virtual machine starting module 410 is not greater than the preset threshold.
When the size value of the virtual disk acquired by the virtual machine starting module 410 is not greater than the preset threshold, although the virtual machine (hereinafter referred to as "virtual machine to be started") cannot boot the operating system from the target virtual disk file, the host still starts the virtual machine process corresponding to the virtual machine. When the virtual machine process corresponding to the virtual machine is detected, the host machine can judge that the virtual machine is normally started.
Therefore, in this embodiment, when the size value of the virtual disk acquired by the virtual machine through the virtual machine starting module 410 is not greater than the preset threshold, starting of the virtual machine process corresponding to the virtual machine may be prohibited. When detecting that the virtual disk size value of the target virtual disk file is not greater than the preset threshold and the virtual machine cannot be started, the host can basically determine that the target virtual disk file is already occupied by other virtual machines, and at this time, can acquire the identification information stored in the preset storage location associated with the target virtual disk file.
If the acquired identification information includes identification information of a virtual machine to be started, it indicates that the virtual machine is a virtual machine that allows the target virtual disk file to be used, in which case, the virtual machine starting apparatus 400 may restart the virtual machine through the restart module 450.
The restart module 450 is configured to, when the obtained identification information includes the identification information of the virtual machine, obtain an actual size value of the target virtual disk file from the storage device, restore the virtual disk size value recorded in the header information of the target virtual disk file to the actual size value, and execute a start instruction for starting the virtual machine through the target virtual disk file again.
In this embodiment, the storage device 100 may record an actual size value of the target virtual disk file, and in an optional manner, the actual size value may be recorded by the recording module 430 in the following manner, that is, the recording module 430 may further be configured to:
when the virtual machine is successfully started through the target virtual disk file, before the header information modification module 420 modifies the virtual disk size value recorded in the header information of the target virtual disk file to a preset size value, the virtual disk size value is obtained, and the virtual disk size value is recorded in the preset storage position as the actual size value of the target virtual disk file.
The virtual machine can be started through the target virtual disk file, which indicates that the virtual disk size value currently recorded in the header information of the target virtual disk file is not the preset size value but the actual size value of the target virtual disk file. Therefore, when the virtual machine is started through the target virtual disk file, the host may obtain, through the recording module 430, the virtual disk size value currently recorded in the header information of the target virtual disk file, and record the virtual disk size value as the actual size value of the target virtual disk file in the storage device 100.
In the implementation process, after the actual size value of the target virtual disk file is recorded, the size value of the virtual disk currently recorded in the header information of the target virtual disk file is modified by the header information modification module 420.
Optionally, in this embodiment, the identification information of the virtual machine and the actual size value may be recorded at the same time. For convenience of management, the identification information of the virtual machine and the actual size value of the target virtual disk file may form a record, and the record may be stored in the preset storage location.
In implementation, when any virtual machine is started through a corresponding target virtual disk file, a record of the virtual machine may be recorded through the recording module 430, where the record includes an actual size value of the target virtual disk file and identification information of the virtual machine, and the record is stored in a file associated with the target virtual disk file in the storage device 100, or stored in a reserved field of the target virtual disk file.
Optionally, for convenience of management, when the preset storage location is a reserved field of the target virtual disk file, a list may be created for storing the first record before the first record is created. Thus, when the virtual machine is started through the target virtual disk file, the list can be directly acquired, whether the list includes the identification information of the virtual machine or not is detected, and if the list does not include the identification information of the virtual machine and the record including the actual size value of the target virtual disk file is stored in the list.
In this embodiment, for the case that the identification information acquired by the identification information acquisition module 440 does not include the identification information of the virtual machine, the virtual machine starting apparatus 400 may further include a start prompting module 460 and a forced start module 470.
The start prompting module 460 is configured to, when the obtained identification information does not include the identification information of the virtual machine, output a prompting message to prompt that the virtual machine cannot be started through the target virtual disk file.
The forced start module 470 is configured to, when receiving a start instruction input again by the user after the prompt information is output to start the virtual disk file, obtain the actual size value of the target virtual disk file from the preset storage location, restore the virtual disk size value recorded in the header information of the target virtual disk file to the actual size value, and execute the start instruction.
In implementation, when the user sees the prompt information, if the virtual machine needs to be forcibly started, the start instruction for starting the virtual machine through the target virtual disk file can be input again. The prompt message may further include a message asking the user whether the user needs to forcibly start the virtual machine from the target virtual disk file. For example, corresponding options such as two tab options of "force start" and "abort start" may be provided on the interface displaying the output information, and the two tab options may be displayed through the management platform of the host.
In detail, when the user selects the tag option of "abandon start", the subsequent operation will be stopped, and when the user selects the tag option of "force start", a start instruction for starting the virtual machine through the target virtual disk file will be sent to the host.
Since the size value of the virtual disk detected by the start prompting module 460 is smaller than the preset threshold, the size value of the virtual disk currently recorded in the header information of the target virtual disk file is necessarily the preset size value modified by the host, and the preset size value can be restored to the actual size value if forced start is required. Therefore, when the host receives the start instruction, the forcible start module 470 may modify the virtual disk size value currently recorded in the header information of the target virtual disk file to the actual size value recorded in the preset storage location, and then re-execute the start instruction.
In this way, when the start instruction is re-executed, since the value of the size field in the header information of the target virtual disk file has been changed to the actual size value of the target virtual disk file, the virtual machine can be successfully started from the target virtual disk file.
It should be noted that the virtual machine startup module 410 is triggered to operate when the startup instruction is executed again.
Optionally, in this embodiment, the virtual machine starting apparatus 400 may further include a first deleting module 480 and/or a second deleting module 490.
The first deleting module 480 is configured to delete the identification information of any virtual machine in the storage device 100 when the virtual machine is deleted.
In this embodiment, when the host detects that any virtual machine is deleted through the management tool, which indicates that the virtual machine does not use the corresponding target virtual disk file any more at this time, the host may obtain the target virtual disk file added in the virtual machine from the xml configuration file of the virtual machine, search the preset storage location associated with the target virtual disk file in the storage device 100, and delete the identification information of the virtual machine in the preset storage location.
When the identification information of the virtual machine is deleted, the first deletion module 480 may be further configured to detect whether the preset storage location further includes identification information of other virtual machines, and if not, it indicates that the target virtual disk file is not currently used by any virtual machine, and may restore the virtual disk size value currently recorded in the header information of the target virtual disk file to its actual size value.
The second deleting module 490 is configured to, when a deleting instruction for deleting a virtual disk file in any virtual machine is received, delete the identification information of the virtual machine in a preset storage location corresponding to the virtual disk file in the storage device 100.
In practical applications, multiple virtual disk files may be added to one virtual machine. When the virtual disk file is used, a situation that one of the virtual disk files is no longer needed may occur, and at this time, the user may delete the virtual disk file in the virtual machine through the corresponding management platform, and at this time, the virtual machine will no longer use the virtual disk file. At this time, the identification information of the virtual machine may be deleted in the preset storage location corresponding to the virtual disk file to identify that the virtual disk file is no longer allowed to be used by the virtual machine.
Correspondingly, when the identification information of the virtual machine is deleted, if it is detected that the preset storage location corresponding to the virtual disk file does not include the identification information of other virtual machines, the actual size value of the virtual disk file can be recovered in the header information of the virtual disk file.
A specific example is given below to further illustrate the above-described virtual machine starting apparatus 400. The specific description is as follows:
as shown in fig. 4, it is assumed that there are a storage apparatus 100, and a host 200 and a host 300 which communicate with the storage apparatus 100, a virtual disk file a having a virtual disk size value of 40G is stored in the storage apparatus 100, a virtual machine startup device 400 and a virtual machine a are deployed on the host 200, and a virtual machine startup device 400 and a virtual machine B are deployed on the host 300.
The virtual disk file A, the virtual machine A and the virtual machine B are all newly built, namely the virtual disk file A is not used by any virtual machine, and the virtual disk file is not added in the virtual machine A and the virtual machine B.
The virtual disk file A is added to the virtual machine A through the management platform, so that the virtual machine A can be started through the virtual disk file A, and the virtual disk file A is a target virtual disk file of the virtual machine A.
Firstly, when the management platform issues a start instruction to the host 200 to control the virtual machine a to start from the virtual disk file a, the host 200 reads, through the virtual machine start module, that the virtual disk size value currently recorded in the header information of the virtual disk file a is 40G, and 40G is greater than a preset threshold (assumed to be 1M), so that the virtual machine a can successfully boot the operating system from the virtual disk file a, and thus the virtual machine a can be normally used.
Secondly, when the virtual machine a is started through the virtual disk file a (target virtual disk file), the host 200 obtains the virtual disk size value 40G and the identification information of the virtual machine a recorded in the header information of the virtual disk file a through the recording module, and stores the virtual disk size value and the identification information of the virtual machine a in the storage device 100 at a preset storage location corresponding to the virtual disk file a.
The identification information of the virtual machine a includes the name of the virtual machine a, the name of the host 200, and the IP address of the host 200. The preset storage location may be an independent file in the storage device 100 with the same suffix name as the virtual disk file a, or may be a reserved field of the virtual disk file a. Wherein "40G" recorded in the preset storage location is an actual size value as the virtual disk file a. The following description will take the example where the preset storage location is an independent file in the storage device 100 with the same suffix name as the virtual disk file a.
Thirdly, after the recording module records the actual size value of the virtual disk file a and the identification information of the virtual machine a, the host 200 modifies the virtual disk size value currently recorded in the header information of the virtual disk file a by the header information modification module to a preset size value of 0.
In this way, the size of the disk file read by the other virtual machines when the virtual disk file a is started is 0, and the other virtual machines cannot be started from the virtual disk file a.
If the user adds the virtual disk file a to the virtual machine B through the management platform and controls to start the virtual machine B through the virtual disk file a, the host 300 may run the virtual machine start module. The method specifically comprises the following steps:
fourthly, the host 300 reads that the size value of the virtual disk currently recorded in the header information of the virtual disk file a is 0 through the virtual machine startup module, and the virtual machine B cannot be started from the virtual disk file a.
Fifth, the host 300 searches for a file associated with the virtual disk file a in the storage device 100 through the identification information obtaining module, and obtains the identification information stored in the file.
At this time, the acquired identification information only includes the identification information of the virtual machine a, so that it can be determined that the acquired identification information does not include the identification information of the virtual machine B, and it is determined that the virtual machine B is not allowed to be forcibly used from the virtual disk file a.
Sixthly, when the identification information acquired by the identification information acquisition module does not include the identification information of the virtual machine B, the host 300 outputs prompt information by starting the prompt module to prompt the user that the virtual disk file a is used by the virtual machine a.
In addition, the user can be further prompted that the actual size value of the virtual disk file a is 40G.
Two tab options of "force start" and "abandon start" may also be provided on the display page of the reminder information. When the user selects 'abandon start', the subsequent operation is not carried out; when the user selects "force boot," the host 300 may run a first force boot module.
Seventhly, the host 300 obtains the actual size value 40G of the virtual disk file a from the file associated with the virtual disk file a through the first forced boot module, modifies the virtual disk size value 0 currently recorded in the header information of the virtual disk file a to 40G, and then re-executes the boot instruction.
At this time, the host 300 reads, through the virtual machine boot module, that the virtual disk size of the virtual disk file a is 40G, which is greater than 1M, and thus the virtual machine B can boot from the virtual disk file a.
After the virtual machine B is started from the virtual disk file a, the host 300 may run a recording module and a header information modification module, and execute steps similar to the second and third steps described above, specifically:
eighth, when the virtual machine B is started from the virtual disk file a, the host 300 obtains the actual size value 40G of the virtual disk file a and the identification information of the virtual machine B through the recording module, and stores the actual size value and the identification information into the file associated with the virtual disk file a in the storage device 100. And then modifying the size value of the virtual disk currently recorded in the header information of the virtual disk file A to be a preset size value 0 through a header information modification module.
In implementation, when it is detected that the virtual machine a (or the virtual machine B) is deleted, the identification information of the virtual machine a (or the virtual machine B) may be deleted in the storage apparatus 100. When a deletion instruction for deleting the virtual disk file A in the virtual machine A is detected, the identification information of the virtual machine A is deleted in the file associated with the virtual disk file A. And if a deletion instruction for deleting the virtual disk file B in the virtual machine B is further detected, deleting the identification information of the virtual machine B in the file associated with the virtual disk file A. However, since only the identification information of the virtual machine B is included in the file associated with the virtual disk file a at this time, the currently recorded virtual disk size value 0 may be modified to 40G in the header information of the virtual disk file a to indicate that the current virtual disk file a is not used by any virtual machine.
Fig. 5 is a schematic flowchart of a virtual machine starting method provided in this embodiment, and the method is applied to each host communicatively connected to the storage device 100 in fig. 1. The method comprises the following steps:
step S501, when a starting instruction for starting any virtual machine through a target virtual disk file is executed, a virtual disk size value recorded in header information of the target virtual disk file is obtained, and when the virtual disk size value is larger than a preset threshold value, the virtual machine is started through the target virtual disk file.
In this embodiment, the description about step S501 may refer to the description about the virtual machine starting module 410 in the foregoing, that is, step S501 may be executed by the virtual machine starting module 410.
Step S502, when the virtual machine is successfully started through the target disk file, the virtual disk size value recorded in the header information of the target virtual disk file is modified to a preset size value, so as to prevent other virtual machines from being started through the target virtual disk file.
In the present embodiment, the description about step S502 may specifically refer to the description about the header information modification module 420 in the above-mentioned content, that is, step S502 may be performed by the header information modification module 420.
Optionally, the storage device 100 may record an actual size value of the target virtual disk file, and correspondingly, the virtual machine starting method may include the following steps:
when the virtual machine is successfully started through the target virtual disk file and the identification information of the virtual machine is not recorded in the storage device 100, acquiring the identification information of the virtual machine and recording the identification information in a preset storage position corresponding to the target virtual disk file in the storage device 100;
when the size value of the obtained virtual disk is not larger than the preset threshold value, obtaining identification information stored in the preset storage position;
when the acquired identification information includes the identification information of the virtual machine, acquiring the actual size value of the target virtual disk file from the storage device 100, restoring the virtual disk size value recorded in the header information of the target virtual disk file to the actual size value, and re-executing a start instruction for starting the virtual machine through the target virtual disk file.
The detailed description of the recording module 430, the identification information obtaining module 440, and the restarting module 450 can be referred to for the above steps.
Optionally, the virtual machine starting method may further include the following steps:
when the obtained identification information does not include the identification information of the virtual machine, outputting prompt information to prompt that the virtual machine cannot be started through the target virtual disk file;
when a start instruction input again by the user after the prompt information is output is received to start the virtual machine through the target virtual disk file, acquiring the actual size value of the target virtual disk file from the preset storage position, restoring the virtual disk size value recorded in the header information of the target virtual disk file to the actual size value, and executing the start instruction.
The above steps can be described with reference to the detailed description of the start prompting module 460 and the forced start module 470 in the above.
Optionally, in this embodiment, the virtual machine starting method may further include the following steps:
when any virtual machine is deleted, deleting the identification information of the virtual machine in the storage device 100; and/or
When a deletion instruction for deleting a virtual disk file in any virtual machine is received, the identification information of the virtual machine is deleted in a preset storage location corresponding to the virtual disk file in the storage device 100.
The detailed description of the first deleting module 480 and the second deleting module 490 in the above-mentioned content can be referred to for the description of the above steps.
To sum up, the embodiments of the present application provide a virtual machine starting apparatus, a virtual machine starting method, and a host, where at least one virtual machine is deployed in each host in communication connection with a storage device, and a virtual disk file for starting the virtual machine is stored in the storage device. Each host comprises a virtual machine starting module and a header information modification module; the virtual machine starting module is used for acquiring a virtual disk size value recorded in header information of a target virtual disk file when any virtual machine is started through a corresponding target virtual disk file, and starting the virtual machine through the target virtual disk file when the virtual disk size value is larger than a preset threshold value; the header information modification module is used for modifying the virtual disk size value recorded in the header information of the target virtual disk file into a preset size value when the virtual machine is started through the target virtual disk file, so as to prevent other virtual machines from being started through the target virtual disk file. Therefore, the method can effectively prevent different virtual machines from using the same virtual disk file at the same time, thereby preventing the data of the virtual disk file from being damaged.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (11)
1. A virtual machine starting device is applied to each host which is in communication connection with a storage device, at least one virtual machine is deployed in each host, and a virtual disk file used for starting the virtual machine is stored in the storage device; the device comprises:
the virtual machine starting module is used for acquiring a virtual disk size value recorded in header information of a target virtual disk file when executing a starting instruction for starting any virtual machine through the target virtual disk file, and starting the virtual machine through the target virtual disk file when the virtual disk size value is larger than a preset threshold value;
and the header information modification module is used for modifying the virtual disk size value recorded in the header information of the target virtual disk file into a preset size value when the virtual machine is successfully started through the target virtual disk file, so as to prevent other virtual machines from being started through the target virtual disk file.
2. The virtual machine startup apparatus according to claim 1, wherein an actual size value of the target virtual disk file is recorded in the storage device, the apparatus further comprising:
the recording module is used for acquiring the identification information of the virtual machine when the virtual machine is successfully started through the target virtual disk file and the identification information of the virtual machine is not recorded in the storage device, and recording the identification information in a preset storage position corresponding to the target virtual disk file in the storage device;
the identification information acquisition module is used for acquiring the identification information stored in the preset storage position when the size value of the virtual disk acquired by the virtual machine starting module is not larger than the preset threshold value;
and the restarting module is used for acquiring the actual size value of the target virtual disk file from the storage device when the acquired identification information comprises the identification information of the virtual machine, recovering the virtual disk size value recorded in the header information of the target virtual disk file to the actual size value, and executing a starting instruction for starting the virtual machine through the target virtual disk file again.
3. The virtual machine startup device of claim 2, characterized in that the device further comprises:
the starting prompting module is used for outputting prompting information to prompt that the virtual machine cannot be started through the target virtual disk file when the obtained identification information does not include the identification information of the virtual machine;
and the forced starting module is used for acquiring the actual size value of the target virtual disk file from the storage equipment, restoring the virtual disk size value recorded in the header information of the target virtual disk file to the actual size value and executing the starting instruction when the starting instruction input again by the user after the prompt information is output is received to start the virtual machine through the target virtual disk file.
4. The virtual machine startup device according to any one of claims 2 to 3, wherein the recording module is further configured to, when the virtual machine is successfully started through the target virtual disk file, obtain the virtual disk size value before the header information modification module modifies the virtual disk size value recorded in the header information of the target virtual disk file to a preset size value, and record the virtual disk size value as an actual size value of the target virtual disk file in the preset storage location.
5. A virtual machine startup device according to any one of claims 1 to 3 characterized in that the device further comprises:
the first deleting module is used for deleting the identification information of any virtual machine in the storage equipment when the virtual machine is deleted; and/or the second deleting module is used for deleting the identification information of the virtual machine in a preset storage position corresponding to the virtual disk file in the storage equipment when a deleting instruction for deleting the virtual disk file in any virtual machine is received.
6. A virtual machine starting method is applied to each host which is in communication connection with a storage device, at least one virtual machine is deployed in each host, and a virtual disk file used for starting the virtual machine is stored in the storage device; the method comprises the following steps:
when a starting instruction for starting any virtual machine through a target virtual disk file is executed, acquiring a virtual disk size value recorded in header information of the target virtual disk file, and when the virtual disk size value is larger than a preset threshold value, starting the virtual machine through the target virtual disk file;
and when the virtual machine is successfully started through the target virtual disk file, modifying the virtual disk size value recorded in the header information of the target virtual disk file into a preset size value so as to prevent other virtual machines from being started through the target virtual disk file.
7. The virtual machine startup method according to claim 6, wherein an actual size value of the target virtual disk file is recorded in the storage device, and the method further comprises:
when the virtual machine is successfully started through the target virtual disk file and the identification information of the virtual machine is not recorded in the storage equipment, acquiring the identification information of the virtual machine and recording the identification information in a preset storage position corresponding to the target virtual disk file in the storage equipment;
when the size value of the obtained virtual disk is not larger than the preset threshold value, obtaining identification information stored in the preset storage position;
when the acquired identification information includes the identification information of the virtual machine, acquiring the actual size value of the target virtual disk file from the storage device, restoring the virtual disk size value recorded in the header information of the target virtual disk file to the actual size value, and re-executing a start instruction for starting the virtual machine through the target virtual disk file.
8. The virtual machine startup method of claim 7, characterized in that the method further comprises:
when the obtained identification information does not include the identification information of the virtual machine, outputting prompt information to prompt that the virtual machine cannot be started through the target virtual disk file;
when a start instruction input again by the user after the prompt information is output is received to start the virtual machine through the target virtual disk file, acquiring the actual size value of the target virtual disk file from the preset storage position, restoring the virtual disk size value recorded in the header information of the target virtual disk file to the actual size value, and executing the start instruction.
9. A virtual machine startup method according to any one of claims 7 to 8, characterized in that when the virtual machine is successfully started through the target virtual disk file, the method further comprises:
and before the virtual disk size value recorded in the header information of the target virtual disk file is modified to a preset size value, acquiring the virtual disk size value, and recording the virtual disk size value as the actual size value of the target virtual disk file in the preset storage position.
10. A virtual machine startup method according to any one of claims 6 to 8, characterized in that the method further comprises:
when any virtual machine is deleted, deleting the identification information of the virtual machine in the storage equipment; and/or when a deleting instruction for deleting the virtual disk file in any virtual machine is received, deleting the identification information of the virtual machine in a preset storage position corresponding to the virtual disk file in the storage equipment.
11. A host is characterized in that the host is in communication connection with a storage device, at least one virtual machine is deployed in the host, and a virtual disk file for starting the virtual machine is stored in the storage device;
the host comprises a memory, a processor and the virtual machine starting device as claimed in any one of claims 1 to 5, wherein the virtual machine starting device is stored in the memory and is controlled to execute by the processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810251730.7A CN108509252B (en) | 2018-03-26 | 2018-03-26 | Virtual machine starting device and method and host |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810251730.7A CN108509252B (en) | 2018-03-26 | 2018-03-26 | Virtual machine starting device and method and host |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108509252A CN108509252A (en) | 2018-09-07 |
| CN108509252B true CN108509252B (en) | 2021-04-06 |
Family
ID=63378402
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810251730.7A Active CN108509252B (en) | 2018-03-26 | 2018-03-26 | Virtual machine starting device and method and host |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108509252B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110018883A (en) * | 2019-04-11 | 2019-07-16 | 苏州浪潮智能科技有限公司 | A kind of virtual machine delet method, device, equipment and storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104572242A (en) * | 2013-10-24 | 2015-04-29 | 华为技术有限公司 | Method and device for expanding disk space of virtual machine and virtual machine system |
| CN105487984B (en) * | 2014-09-17 | 2020-04-03 | 中兴通讯股份有限公司 | Method and device for dynamically compressing disk data of virtual machine by host system |
| CN106775924B (en) * | 2016-11-07 | 2018-08-07 | 北京百度网讯科技有限公司 | Virtual machine starts method and apparatus |
-
2018
- 2018-03-26 CN CN201810251730.7A patent/CN108509252B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN108509252A (en) | 2018-09-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8738883B2 (en) | Snapshot creation from block lists | |
| EP2652599B1 (en) | System reset | |
| US7694169B2 (en) | Restoring a client device | |
| US11698808B2 (en) | System and method of selectively restoring a computer system to an operational state | |
| CN112596951B (en) | NAS data disaster recovery method, device, equipment and storage medium | |
| CN106970856B (en) | Data management system and method for backing up, recovering and mounting data | |
| CN115098299B (en) | Backup method, disaster recovery method, device and equipment of virtual machine | |
| US20170075776A1 (en) | Methods for preserving state across a failure and devices thereof | |
| CN103198122A (en) | Method and device for restarting in-memory database | |
| CN108874441B (en) | Board card configuration method, device, server and storage medium | |
| CN105867962A (en) | System upgrading method and device | |
| CN109726039B (en) | Method and apparatus for managing virtual machines | |
| CN110941516B (en) | Operating system restoration method, device, equipment and storage medium | |
| US8990168B1 (en) | Efficient conflict resolution among stateless processes | |
| CN108509252B (en) | Virtual machine starting device and method and host | |
| CN106897063B (en) | Method and system for permanently adding OS boot entry to BIOS based on EFI | |
| KR102274668B1 (en) | Apparatus and method for controlling updating software of AVN system in vehicle | |
| US20160004607A1 (en) | Information processing apparatus and information processing method | |
| US7313725B2 (en) | Replacement restoration disk drive and method | |
| CN108259613B (en) | Disaster recovery data online synchronization device, method and computer readable storage medium | |
| CN110389862B (en) | Data storage method, device, equipment and storage medium | |
| CN117215835A (en) | Equipment starting method and device, electronic equipment and storage medium | |
| CN115543539A (en) | Virtual machine password resetting method, device and medium | |
| CN112667358A (en) | Management method of virtual machine snapshot, electronic device and computer readable medium | |
| US8370306B1 (en) | Systems and methods for recovering from continuous-data-protection blackouts |
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 |