CN116339908A - Virtual machine starting method, device, computer equipment and storage medium - Google Patents
Virtual machine starting method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN116339908A CN116339908A CN202211705383.3A CN202211705383A CN116339908A CN 116339908 A CN116339908 A CN 116339908A CN 202211705383 A CN202211705383 A CN 202211705383A CN 116339908 A CN116339908 A CN 116339908A
- Authority
- CN
- China
- Prior art keywords
- version information
- virtual
- virtual machine
- hardware version
- server
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 238000004590 computer program Methods 0.000 claims abstract description 25
- 238000006243 chemical reaction Methods 0.000 claims description 22
- 238000012545 processing Methods 0.000 claims description 15
- 238000012937 correction Methods 0.000 claims description 14
- 238000001514 detection method Methods 0.000 claims description 9
- 230000004048 modification Effects 0.000 claims description 7
- 238000012986 modification Methods 0.000 claims description 7
- 230000008569 process Effects 0.000 claims description 6
- 230000004044 response Effects 0.000 claims description 5
- 230000006870 function Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000008676 import Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 238000009825 accumulation Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 239000002699 waste material Substances 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
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The application relates to a virtual machine starting method, a virtual machine starting device, computer equipment, a storage medium and a computer program product. The method comprises the following steps: responding to a starting instruction of a server, and acquiring virtual hardware version information of each virtual machine installed under the server; determining target virtual machines of which the virtual hardware version information does not accord with preset version conditions in each virtual machine; correcting virtual hardware version information contained in a configuration file of the target virtual machine into first target virtual hardware version information; the first target virtual hardware version information is virtual hardware version information matched with the version information of the virtualized platform program suite operated by the server; and starting the corrected virtual machines. By adopting the method, the problem that the virtual machine cannot be started and then the server is restarted or down due to poor compatibility of the virtualized platform program suite and the server can be solved, and the stability and safety of the whole environment of the virtualized platform are improved.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a virtual machine starting method, apparatus, computer device, storage medium, and computer program product.
Background
VMware vSphere is a widely used virtualization platform suite of programs, and users can build a virtualization platform based on the VMware vSphere suite of programs. Specifically, the VMware vSphere program suite mainly includes an ESXi program component and a vCenter Server program component, by installing and running the ESXi program component on a Server, the Server can be deployed as an ESXi host, as a virtualization platform for creating and running a virtual machine, multiple ESXi hosts can form a virtualized platform cluster (vSphere cluster), and each ESXi host in the vSphere cluster can be managed by a management node deployed based on the vCenter Server program component.
However, some versions of the VMware vSphere suite (e.g., version 7.0 and version 8.0) have poor compatibility with the ESXi host on which the C86 processor is installed, and therefore, when the virtual machine is started on the ESXi host, a situation that the virtual machine cannot be started easily occurs, which causes a problem that the ESXi host is restarted or down.
Disclosure of Invention
Accordingly, in view of the above-mentioned problems, it is necessary to provide a method, an apparatus, a computer device, a computer readable storage medium and a computer program product for starting a virtual machine, which can avoid the problem that a virtual machine cannot be started up and further the server is restarted or down due to poor compatibility between a virtualized platform program suite (such as VMware vSphere program suite) and the server carrying the C86 processor, so as to improve the stability and safety of the overall environment of the virtualized platform.
In a first aspect, the present application provides a virtual machine starting method. The method is applied to a server, wherein a plurality of virtual machines are deployed on the server, and the method comprises the following steps:
responding to a starting instruction of the server, and acquiring virtual hardware version information of each virtual machine installed under the server;
determining target virtual machines of which the virtual hardware version information does not accord with preset version conditions in the virtual machines;
correcting virtual hardware version information contained in a configuration file of the target virtual machine into first target virtual hardware version information; the first target virtual hardware version information is virtual hardware version information matched with version information of a virtualized platform program suite operated by the server;
and starting the corrected virtual machines.
In this embodiment, by automatically checking the compatibility of the virtual hardware version information of each virtual machine installed under the server, the virtual hardware version information of the target virtual machine which does not meet the preset version condition is revised to be the virtual hardware version information (i.e., the first target virtual hardware version information) which is matched with the version information of the virtualized platform program suite operated by the server, so that each revised virtual machine can be started normally, even if the compatibility between the server and the operated virtualized platform program suite is poor, the problem that the server is restarted or down due to the fact that the virtual machine cannot be started is avoided, and the stability and safety of the whole environment of the virtualized platform are improved.
In one embodiment, the modifying the virtual hardware version information included in the configuration file of the target virtual machine to the first target virtual hardware version information includes:
performing first format conversion on the configuration file of the target virtual machine in the original format to obtain the configuration file in the target format, and correcting virtual hardware version information contained in the configuration file in the target format into first target virtual hardware version information;
and carrying out second format conversion on the corrected configuration file in the target format to obtain the corrected configuration file in the original format.
In this embodiment, for a configuration file of a target virtual machine in an original format, in which a server cannot directly read and modify content, smooth modification of virtual hardware version information of the target virtual machine can be achieved through format conversion, so that when the modified virtual machine is started, the problem that the virtual machine cannot be started and then the server is restarted or down due to poor compatibility of the server and a virtualization platform program suite can be avoided.
In one embodiment, in each of the virtual machines, determining that the virtual hardware version information does not meet the target virtual machine of the preset version condition includes:
Matching the virtual hardware version information of each virtual machine with second target virtual hardware version information contained in a preset version information set; the second target virtual hardware version information is virtual hardware version information which is not matched with the version information of the virtualized platform program suite operated by the server;
and under the condition that the virtual hardware version information successfully matched with the second target virtual hardware version information exists, determining the virtual machine corresponding to the successfully matched virtual hardware version information as a target virtual machine which does not meet the preset version condition.
In this embodiment, the target virtual machine which is successfully matched and does not conform to the preset version condition is determined by matching the virtual hardware version information of each virtual machine with the second target virtual hardware version information (the second target virtual hardware version information is the virtual hardware version information which is not matched with the virtualized platform program suite and is not qualified), and compared with the size of the version number of each virtual hardware version information and the minimum virtual hardware version information which is qualified, the method has higher efficiency, and the target virtual machine can be rapidly determined and corrected.
In one embodiment, the responding to the start instruction of the server, obtaining the virtual hardware version information of each virtual machine installed under the server includes:
and responding to the starting instruction of the server, and acquiring the virtual hardware version information of each installed virtual machine from the server in a preset period.
In this embodiment, after the server is started, the virtual hardware version information of each virtual machine installed on the server may be obtained according to a preset period, so as to check and correct the virtual hardware version information of each virtual machine on the server in time, so as to avoid the compatibility problem that the virtual machine cannot be started and the server is restarted or down caused by untimely correction, thereby improving the stability and security of the overall environment of the virtualized platform.
In one embodiment, before the performing the startup processing on each virtual machine after the correction, the method further includes:
and under the condition that the virtual machine is a vCLS proxy virtual machine, correcting the central processor parameter detection value contained in the configuration file of the vCLS proxy virtual machine into a target parameter value, wherein the target parameter value is used for indicating that the central processor parameter reading step is not executed when the vCLS proxy virtual machine is started.
In this embodiment, by correcting the CPU parameter detection value in the configuration file of the vCLS proxy virtual machine to the target parameter value, when starting the vCLS proxy virtual machine based on the corrected configuration file, the CPU parameter reading step will not be executed, so that the vCLS proxy virtual machine can be successfully started on the server carrying the C86 processor, and a guarantee is provided for starting the DRS function of the virtualized platform cluster.
In one embodiment, before the performing the startup processing on each virtual machine after the correction, the method further includes:
under the condition that the virtual machine is a vCLS proxy virtual machine, virtual identification information is obtained from a configuration file of the vCLS proxy virtual machine;
and performing anti-registration processing on the vCLS proxy virtual machine according to the virtual identification information.
In this embodiment, by acquiring the virtual ID of the vCLS proxy virtual machine, the vCLS proxy virtual machine is subjected to the anti-registration processing, so that the server does not generate the vCLS proxy virtual machine, thereby achieving the effect of not generating alarm information.
In a second aspect, the application further provides a virtual machine starting device. The device comprises:
the first acquisition module is used for responding to a starting instruction of a server and acquiring virtual hardware version information of each virtual machine installed under the server;
The determining module is used for determining target virtual machines, of which the virtual hardware version information does not accord with the preset version conditions, in the virtual machines;
the first correction module is used for correcting the virtual hardware version information contained in the configuration file of the target virtual machine into first target virtual hardware version information; the first target virtual hardware version information is virtual hardware version information matched with version information of a virtualized platform program suite operated by the server;
and the starting module is used for starting the corrected virtual machines.
In one embodiment, the first correction module is specifically configured to:
performing first format conversion on the configuration file of the target virtual machine in the original format to obtain the configuration file in the target format, and correcting virtual hardware version information contained in the configuration file in the target format into first target virtual hardware version information; and carrying out second format conversion on the corrected configuration file in the target format to obtain the corrected configuration file in the original format.
In one embodiment, the determining module is specifically configured to:
matching the virtual hardware version information of each virtual machine with second target virtual hardware version information contained in a preset version information set; the second target virtual hardware version information is virtual hardware version information which is not matched with the version information of the virtualized platform program suite operated by the server; and under the condition that the virtual hardware version information successfully matched with the second target virtual hardware version information exists, determining the virtual machine corresponding to the successfully matched virtual hardware version information as a target virtual machine which does not meet the preset version condition.
In one embodiment, the first obtaining module is specifically configured to:
and responding to the starting instruction of the server, and acquiring the virtual hardware version information of each installed virtual machine from the server in a preset period.
In one embodiment, the apparatus further comprises:
and the second correction module is used for correcting the central processor parameter detection value contained in the configuration file of the vCLS proxy virtual machine to be a target parameter value when the virtual machine is the vCLS proxy virtual machine, wherein the target parameter value is used for indicating that the central processor parameter reading step is not executed when the vCLS proxy virtual machine is started.
In one embodiment, the apparatus further comprises:
the second acquisition module is used for acquiring virtual identification information from a configuration file of the vCLS proxy virtual machine when the virtual machine is the vCLS proxy virtual machine;
and the anti-registration module is used for carrying out anti-registration processing on the vCLS proxy virtual machine according to the virtual identification information.
In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the steps of the method of the first aspect when the processor executes the computer program.
In a fourth aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method of the first aspect.
In a fifth aspect, the present application also provides a computer program product. The computer program product comprising a computer program which, when executed by a processor, implements the steps of the method of the first aspect.
After a server (i.e., an ESXi host deployed based on a VMware vSphere program suite) is started, virtual hardware version information of all virtual machines installed under the server is obtained, and a target virtual machine whose virtual hardware version information does not meet a preset version condition is determined, so that virtual hardware version information contained in a configuration file of the target virtual machine is modified into first target virtual hardware version information, and then starting processing is performed on each virtual machine after modification. According to the method, the compatibility of the virtual hardware version information of each virtual machine installed under the server can be automatically checked, the virtual hardware version information of the virtual machine which does not meet the preset version conditions is revised to be the virtual hardware version information matched with the version information of the virtualized platform program suite operated by the server, so that each revised virtual machine can be normally started, and the problem that the server is restarted or down due to the fact that the virtual machine cannot be started even if the compatibility of the server and the operated virtualized platform program suite is poor is avoided, and the stability and safety of the whole environment of the virtualized platform are improved.
Drawings
FIG. 1 is a flow chart of a virtual machine starting method in one embodiment;
FIG. 2 is a flow diagram of correcting virtual hardware version information in one embodiment;
FIG. 3 is a flow diagram of determining a target virtual machine in one embodiment;
FIG. 4 is a block diagram of a virtual machine starting apparatus in one embodiment;
fig. 5 is an internal structural diagram of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
First, before the technical solution of the embodiments of the present application is specifically described, a description is first given of a technical background or a technical evolution context on which the embodiments of the present application are based.
VMware vSphere is a widely used virtualized platform suite of programs that contains a number of program components, mainly ESXi program components and vCenter Server program components. A user can build a virtualized platform based on a VMware vSphere program suite, specifically, a server can be deployed as an ESXi host by installing an ESXi program component on the server, and the ESXi host and a related virtual machine with shared resources and a shared management interface form a virtualized platform cluster (vSphere cluster) serving as a virtualized platform for creating and running the virtual machines. Based on the vCenter Server program component, one ESXi host in the vSphere cluster can be deployed as a management node to provide vCenter Server service so as to uniformly manage each ESXi host in the vSphere cluster and a virtual machine installed under each ESXi host. The management node may be deployed on a virtual machine installed under the ESXi host, and the virtual machine deployed as the management node may be referred to as a vCenter virtual device.
Currently, the VMware vSphere suite has been developed in several versions, including newer developed versions of VMware vSphere 7.0 (including U1, U2, U3) and 8.0. The newer release introduced some new functionality, for example, the vphere cluster service (vSphere Clustering Service, vCLS) is a new one introduced in the vphere version 7.0, which can be used to maintain the resources and operating conditions of the workload running in the vphere cluster. When the ESxi host is added to the cluster, a vcLS proxy virtual machine (at most 3 vcLS proxy virtual machines in each vchere cluster are operated) is automatically created in the cluster, so that the vchere cluster service is provided through the vchere proxy virtual machine. The vmsphere DRS (vSphere Distributed Resource Scheduler, distributed resource scheduling) is an important function of VMware vmsphere for maintaining normal operation of workload within the vmsphere cluster, and the availability of DRS functions depends on the availability of vCLS proxy virtual machines.
However, some versions of the VMware vSphere suite have poor suitability and compatibility with domestic C86 processors, and particularly the compatibility problems of the newer versions of version 7.0 and version 8.0 with C86 processors are apparent. The main compatibility problem is represented by the problem that after a server carrying a C86 processor is deployed as an ESXi host based on a VMware vSphere program suite of 7.0 or 8.0, when a virtual machine is started on the ESXi host, the virtual machine is likely to be unable to be started, and the ESXi host is restarted or crashed. Due to the influence of a high availability mechanism (High Availability, HA) of the vSphere cluster, the compatibility problem can cause large-scale downtime or restarting faults of all ESXi hosts in the vSphere cluster to which the ESXi hosts belong, thereby seriously affecting the stability and the safety of the whole environment of the virtualized platform.
Based on the background, the applicant provides a long-term research and development and experimental verification method for starting virtual machines, which can automatically check the compatibility of virtual hardware version information of each virtual machine installed under a server (such as an ESXi host), correct the virtual hardware version information of the virtual machine which does not meet preset version conditions into virtual hardware version information matched with version information of a virtualization platform program suite (such as a VMware vSphere program suite) operated by the server, so that each corrected virtual machine can be normally started, and even if the compatibility of the server (such as a server carrying a C86 processor) and the operated VMware vSphere program suite (such as a 7.0 version or a 8.0 version) is poor, the problem that the ESXi host is restarted or down due to the fact that the virtual machine cannot be started is avoided, and the stability and safety of the overall environment of a virtualization platform based on the VMware vSphere program suite and the server carrying the C86 processor are improved.
In addition, the applicant has made a great deal of creative effort to find out the technical problems of the present application and to introduce the technical solutions of the following embodiments.
In one embodiment, as shown in fig. 1, a virtual machine starting method is provided, where the method may be applied to a server (e.g., a server carrying a C86 processor), where the server may be deployed as a virtualized platform (e.g., an ESXi host, i.e., a server having an ESXi program component installed and running) based on a virtualized platform program suite (e.g., a VMware vSphere program suite), where several virtual machines may be deployed on the server, and where vCenter virtual devices and other virtual devices deployed as management nodes may be included. It will be appreciated that this method is applicable to each ESXi host in a virtualized platform cluster (vSphere cluster). In this embodiment, the method specifically includes the following steps:
And step 101, responding to a starting instruction of the server, and acquiring virtual hardware version information of each virtual machine installed under the server.
In practice, the user may trigger a startup operation of the server (i.e., the ESXi host) and send a startup instruction to the server. For example, the user may remotely access the console interface of the ESXi host through the terminal, trigger the start operation of the ESXi host at the console interface, or the user may trigger the start operation through a physical start button of the ESXi host. The server may obtain virtual hardware version information of each of the locally installed virtual machines in response to the start instruction. The virtual hardware version information is attribute information of the virtual machine, and is used for indicating virtual hardware functions, virtual slot number, maximum CPU number, maximum memory configuration and other hardware characteristics supported by the virtual machine. Alternatively, the preset interface of the ESXi host may be accessed to obtain the virtual hardware version information of each virtual machine installed on the ESXi host, for example, the preset interface may be a vSphere API (Application Programming Interface ) interface. The virtual machines comprise virtual machines newly created by a user on an ESXi host, virtual machines (or virtual devices) generated through an import template, or virtual machines automatically generated by the ESXi host (such as a vCLS proxy virtual machine). It will be appreciated that virtual machines installed under an ESXi host may include vCenter virtual devices deployed as management nodes, as well as other virtual devices (e.g., NSX virtual devices deployed as network virtualization platforms).
And 102, determining a target virtual machine of which the virtual hardware version information does not meet the preset version condition in each virtual machine.
In implementation, after the server obtains the virtual hardware version information of each locally installed virtual machine, the target virtual machine whose virtual hardware version information does not meet the preset version condition can be screened out from each virtual machine. For example, the preset version condition may be that the version number of the virtual hardware version information is greater than or equal to the version number of the first target virtual hardware version information. For example, the version number of the first target virtual hardware version information may be 13, and if a virtual machine whose version number of the virtual hardware version information is smaller than 13 (e.g., 10 or 11) exists in the virtual machines installed under the ESXi host, it may be determined that the virtual machine does not meet the preset version condition, and the virtual machine is determined to be the target virtual machine.
The version number of the first target virtual hardware version information is a version number of virtual hardware version information matched with the version information of a virtualized platform program suite (such as a VMware vSphere program suite) operated by a server, and a corresponding relationship between the VMware vSphere program suite of each version and the version number of the virtual hardware version information can be established in advance, so that the version number of the virtual hardware information matched with the version information of the VMware vSphere program suite operated by the server can be determined in the corresponding relationship. Specifically, after a server carrying a C86 processor is deployed as an ESXi host to construct a vSphere cluster based on a VMware vSphere program suite, when each virtual machine installed under the ESXi host is started, the ESXi host can check whether the virtual hardware version information of each virtual machine meets the requirements, if the virtual hardware version information does not meet the requirements, the virtual machine cannot be started successfully, and the ESXi host can be restarted or down. The VMware vSphere program suite of different versions has different requirements for virtual hardware version information of the virtual machine installed under the ESXi host on which the C86 processor is installed. For example, for VMware vSphere program packages of versions 7.0 and 8.0, when the virtual hardware version information (version number) of a virtual machine installed under an ESXi host on which a C86 processor is installed is 13 or less (10 or 11), starting the virtual machine will cause the host to restart or crash, and when the virtual hardware version information is 13 or more, the virtual machine can be smoothly started without causing the host to restart or crash.
And step 103, correcting the virtual hardware version information contained in the configuration file of the target virtual machine into first target virtual hardware version information.
In implementation, after the server determines that the target virtual machine does not meet the preset version condition, the virtual hardware version information may be modified to the first target virtual hardware version information in the configuration file of the target virtual machine. The first target virtual hardware version information is virtual hardware version information matched with the version information of the virtualized platform program suite operated by the server. It will be appreciated that there may be a plurality of matching virtual hardware version information, and the server may select the first target virtual hardware version information from each matching virtual hardware version information randomly or according to other selection conditions. For example, if the version information of the VMware vSphere program suite running on the ESXi host is 7.0 or 8.0 versions, the virtual hardware version information matched with the version information of the VMware vSphere program suite is 13 or more according to the corresponding relation between the version information of the program suite and the virtual hardware version information, so that the server can randomly select one virtual hardware version information from the matched virtual hardware version information as the first target virtual hardware version information, or the server can select the virtual hardware version information with the minimum version number (i.e. "13") from the matched virtual hardware version information as the first target virtual hardware version information.
In implementation, after the server corrects the virtual hardware version information of the locally installed target virtual machine which does not meet the preset version condition, the corrected virtual machines can be started. For example, the ESXi host may boot the virtual machine in response to a user-triggered boot operation for the virtual machine. The ESXi host may also automatically start the locally installed virtual machine (e.g., automatically start vCLS proxy virtual machine) according to other preset trigger conditions.
In the virtual machine starting method, the compatibility checking can be automatically performed on the virtual hardware version information of each virtual machine installed under the server, the virtual hardware version information of the target virtual machine which does not meet the preset version condition is modified to be the virtual hardware version information (namely the first target virtual hardware version information) matched with the version information of the virtualized platform program suite operated by the server, so that each modified virtual machine can be normally started, and even if the server (such as the server carrying the C86 processor) has poor compatibility with the operated virtualized platform program suite (such as the VMware vSphere program suite of 7.0 edition or 8.0 edition), the problem that the server is restarted or down due to the fact that the virtual machine cannot be started can be avoided, and the stability and the safety of the whole environment of the virtualized platform are improved.
In one embodiment, as shown in fig. 2, the process of correcting the virtual hardware version information in step 103 specifically includes the following steps:
In practice, there may be a configuration file in which the server cannot directly read and correct the content in the configuration file of each virtual machine installed on the server. For example, for a part of virtual machines, the configuration file is an ova file (i.e., the original format of the configuration file is an ova format), and the server cannot directly read and correct the content of the ova file. The server can identify the format (namely the original format) of the configuration file of the target virtual machine, and under the condition that the format of the configuration file of the target virtual machine is determined to be the preset format (namely the format which cannot be directly read and corrected), the server can perform first format conversion on the configuration file of the target virtual machine in the original format to obtain the configuration file in the target format. The target format is a file format in which the server can directly read and correct the file content. Specifically, the server may perform format conversion on the configuration file in the original format by using a format conversion tool corresponding to the original format and the target format to obtain the configuration file in the target format, so that the server may modify the virtual hardware version information included in the configuration file in the target format into the first target virtual hardware version information.
For example, for a configuration file in the original format that is an ova format, the server may use a format conversion tool (such as an ovftool) to convert the configuration file in the ova format, so as to obtain a configuration file (i.e. ovf file) in the ovf format (i.e. the target format) that the server may read and modify the file content, so that the server may read and modify the virtual hardware version information contained in the ovf file, and modify the virtual hardware version information into the first target virtual hardware version information.
It can be understood that if the configuration file of the original target virtual machine is a file that the server can directly read and modify the content, for example, a configuration file in vmx format, the server does not need to perform format conversion on the configuration file.
In implementation, after the server corrects the configuration file in the target format, the corrected configuration file in the target format may be subjected to second format conversion to be converted into a file in the original format, so as to obtain the corrected configuration file in the original format. So that the server can smoothly run the modified virtual machine based on the original format configuration file.
For example, for a configuration file with an original format being an ova format, the server may convert the configuration file with the ova format to obtain a ovf file by using a format conversion tool (such as an ovftool), and after correcting the virtual hardware version information included in the ovf file, the server may convert the corrected ovf file to the ova file by using the format conversion tool (such as the ovftool). It can be understood that after the ovftool is adopted to perform format conversion on the ova file, not only ovf files but also other files including mf files are obtained, after ovf files are corrected, the corrected ovf files and other files obtained by converting the original ova files can be subjected to format conversion together, and the corrected ova files are obtained. In order to smoothly import the corrected configuration file (corrected ova file), after the ovf file is corrected, the SHA1 (Secure Hash Algorithm, secure hash algorithm 1) value may be generated for the corrected ovf file, and the SHA1 value may be written into the mf file to ensure that the verification values are consistent, so that the corrected ovf file, the corrected mf file and other related files may be successfully imported into the virtualization platform.
In this embodiment, for a configuration file of an original format target virtual machine of which the server cannot directly read and modify content, the server may perform format conversion on the configuration file to obtain a configuration file of the original format of which the content can be read and modified, so that the configuration file of the target format can be modified, and format restoration is performed after modification, so that smooth modification of virtual hardware version information of the target virtual machine can be achieved, so as to ensure that the virtual hardware version information of each modified virtual machine meets preset version conditions, and thus the modified virtual machine can be started normally, and the problem that the virtual machine cannot be started and then is restarted or down due to poor compatibility of a program suite of a server and a virtualized platform is avoided.
In one embodiment, as shown in fig. 3, the process of determining the target virtual machine in step 102 specifically includes the following steps:
The second target virtual hardware version information is virtual hardware version information which is not matched with the version information of the virtualized platform program suite operated by the server. There may be a plurality of second target virtual hardware version information, and each second target virtual hardware version information constitutes a version information set. For example, for VMware vSphere program packages of versions 7.0 and 8.0, when the virtual hardware version information (version number) of a virtual machine installed under an ESXi host on which a C86 processor is installed is 13 or less (10 or 11), starting the virtual machine will cause the host to restart or crash, and when the virtual hardware version information is 13 or more, the virtual machine can be smoothly started without causing the host to restart or crash. Since the versions of the virtual hardware version information below "13" in the currently mainstream virtual machines are generally "10" and "11" (which are basically discarded below "10"), the virtual hardware version information "10" and "11" that does not match the version information of the virtualized platform program suite running on the server can be used as the second target virtual hardware version information to construct the preset version information set. Therefore, the server can match the virtual hardware version information of each virtual machine with each second target virtual hardware version information contained in the preset version information set.
And step 302, determining the virtual machine corresponding to the successfully matched virtual hardware version information as the target virtual machine which does not meet the preset version condition under the condition that the virtual hardware version information successfully matched with the second target virtual hardware version information exists.
In implementation, after the server matches the virtual hardware version information of each virtual machine with the second target virtual hardware version information, if there is virtual hardware version information successfully matched with the second target virtual hardware version information in the virtual hardware version information of each virtual machine, the server may determine the virtual machine corresponding to the successfully matched virtual hardware version information as the target virtual machine that does not meet the preset version condition. For example, the second target virtual hardware version information may be version numbers "10" and "11", so that the version numbers "10" and "11" may be respectively matched with the virtual hardware version information of each virtual machine. If the matching of the virtual hardware version information and any second target virtual hardware version information is successful, that is, the version number of the virtual hardware version information is '10' or '11', the virtual machine corresponding to the virtual hardware version information is the target virtual machine which does not meet the preset version condition.
In this embodiment, by matching the virtual hardware version information of each virtual machine with the second target virtual hardware version information (the second target virtual hardware version information is the virtual hardware version information that is not matched with the virtualized platform program suite and is not qualified), and determining the virtual machine corresponding to the virtual hardware version information that is successfully matched as the target virtual machine that does not conform to the preset version condition, compared with the comparison of the version number of each virtual hardware version information and the minimum virtual hardware version information that is qualified, the method has higher efficiency, and can quickly determine and correct the target virtual machine, thereby improving the stability and safety of the overall environment of the virtualized platform.
In one embodiment, the process of obtaining the virtual hardware version information of each virtual machine in step 101 specifically includes the following steps: and responding to the starting instruction of the server, and acquiring the virtual hardware version information of each installed virtual machine from the server in a preset period.
In implementation, after the user triggers a start instruction of the server, the server may obtain, in response to the start instruction, virtual hardware version information of each installed virtual machine from the server in a preset period. That is, after the server is started, the virtual hardware version information of the virtual machine is obtained and the subsequent steps of compatibility checking and correction are performed, and the steps may be performed according to a preset period, for example, the preset period may be set to 1 minute.
In this embodiment, since a user may create or import a new virtual machine or virtual device on a server (ESXi host) at any time, after the server is started, virtual hardware version information of each virtual machine installed on the server may be obtained according to a preset period, so as to timely check and correct virtual hardware version information of each virtual machine on the server, and avoid compatibility problems that the virtual machine cannot be started and a server is restarted or down due to untimely correction, thereby improving stability and security of the overall environment of the virtualization platform.
In one embodiment, before each virtual machine is started in step 104, the method further comprises the steps of: and when the virtual machine is the vCLS proxy virtual machine, correcting the central processor parameter detection value contained in the configuration file of the vCLS proxy virtual machine into a target parameter value, wherein the target parameter value is used for indicating that the vCLS proxy virtual machine is started, and the central processor parameter reading step is not executed.
In implementations, the server can identify a locally installed vCLS proxy virtual machine. For example, the server may match the names of vCLS proxy virtual machines with the names of the virtual machines, and the virtual machine with successfully matched names is the vCLS proxy virtual machine. The server may then modify the Central Processing Unit (CPU) parameter detection value to a target parameter value in the vCLS proxy virtual machine's configuration file. The target parameter value is used for indicating that the CPU parameter reading step is not executed when the vCLS proxy virtual machine is started. The target parameter values may be obtained in advance from experimental analysis.
The vCLS agent virtual machine is a virtual machine automatically generated by an ESxi host in the vSphere cluster, and a configuration file of the vCLS agent virtual machine is a default configuration file, wherein the configuration file comprises a CPU parameter detection value. When the vCLS proxy virtual machine is started according to the default configuration file, a step of reading a CPUID (CPUID operation code) in an EAX register (Extended accumulator register, extended accumulation register) of the CPU to identify the CPU type is executed, and if the CPU type is identified as a qualified type, the vCLS proxy virtual machine can be successfully started. For the C86 processor, the return value is zero when the content of the EAX register is read, so that the vCLS proxy virtual machine cannot judge the type of the CPU, the vCLS proxy virtual machine cannot be started, and alarm information is also sent. That is, there is another compatibility problem with virtualized platform program packages (e.g., VMware vspheres 7.0 and 8.0) with servers hosting C86 processors: the vCLS proxy virtual machine on the ESXi host on which the C86 processor is mounted cannot be started. The most direct influence of the compatibility problem is that the DRS (Distributed Resource Scheduler, distributed resource scheduling) function of the virtualized platform cluster (vSphere cluster) which depends on the vCLS proxy virtual machine cannot be used, so that the vSphere cluster cannot automatically balance resource load, the resource utilization rate of partial hosts in the cluster is possibly too low, the resource waste is caused, the resource utilization rate of partial hosts is too high, and the stability and the efficiency of the whole environment of the virtualized platform are seriously influenced. The embodiment can solve the problem that the vCLS proxy virtual machine cannot be started due to poor compatibility of the virtualized platform program suite and the server carrying the C86 processor.
In this embodiment, by correcting the CPU parameter detection value in the configuration file of the vCLS proxy virtual machine to the target parameter value, when starting the vCLS proxy virtual machine based on the corrected configuration file, the steps of CPU parameter reading and CPU type identification will not be executed, but the vCLS proxy virtual machine is directly started by the configuration of the general-purpose processor, so that the vCLS proxy virtual machine can be successfully started on the ESXi host carrying the C86 processor, and a guarantee is provided for starting the DRS function of the virtualized platform cluster.
In one embodiment, before each virtual machine is started in step 104, the method further comprises the steps of: under the condition that the virtual machine is a vCLS proxy virtual machine, virtual identification information is obtained from a configuration file of the vCLS proxy virtual machine; and performing anti-registration processing on the vCLS proxy virtual machine according to the virtual identification information.
In an implementation, when the vCLS proxy virtual machine is identified in each virtual machine, the server may acquire virtual identification information (i.e., virtual ID) from a configuration file of the vCLS proxy virtual machine, and then, the server may perform a deregistration process on the vCLS proxy virtual machine according to the virtual identification information of the vCLS proxy virtual machine, that is, deregister the vCLS proxy virtual machine.
In this embodiment, because the compatibility between the server on which the C86 processor is mounted and the virtualized platform program suite (e.g., VMware vspheres 7.0 and 8.0 versions) is poor, when the vCLS proxy virtual machine is started on the virtualized platform host (ESXi host) on which the C86 processor is mounted, the virtualized platform will send out alarm information because the vCLS proxy virtual machine cannot be successfully started, and the use experience of the user is affected. According to the embodiment, the virtual ID of the vCLS proxy virtual machine is obtained, and the vCLS proxy virtual machine is subjected to anti-registration processing, so that the server does not generate the vCLS proxy virtual machine, and the effect of not generating alarm information is achieved.
It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.
Based on the same inventive concept, the embodiment of the application also provides a virtual machine starting device for realizing the above related virtual machine starting method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation in the embodiments of the virtual machine starting device or devices provided below may refer to the limitation of the virtual machine starting method hereinabove, and will not be repeated herein.
In one embodiment, as shown in fig. 4, there is provided a virtual machine starting apparatus 400, including: a first acquisition module 401, a determination module 402, a first correction module 403, and a start module 404, wherein:
the first obtaining module 401 is configured to obtain, in response to a start instruction of a server, virtual hardware version information of each virtual machine installed under the server.
A determining module 402, configured to determine, in each of the virtual machines, a target virtual machine whose virtual hardware version information does not meet a preset version condition.
A first correction module 403, configured to correct virtual hardware version information included in a configuration file of the target virtual machine to first target virtual hardware version information; the first target virtual hardware version information is virtual hardware version information that matches version information of a virtualized platform program suite operated by the server.
And the starting module 404 is configured to perform starting processing on each of the corrected virtual machines.
In one embodiment, the first correction module 403 is specifically configured to: performing first format conversion on the configuration file of the target virtual machine in the original format to obtain the configuration file in the target format, and correcting virtual hardware version information contained in the configuration file in the target format into first target virtual hardware version information; and carrying out second format conversion on the corrected configuration file in the target format to obtain the corrected configuration file in the original format.
In one embodiment, the determining module 402 is specifically configured to: matching the virtual hardware version information of each virtual machine with second target virtual hardware version information contained in a preset version information set; the second target virtual hardware version information is virtual hardware version information which is not matched with the version information of the virtualized platform program suite operated by the server; and under the condition that the virtual hardware version information successfully matched with the second target virtual hardware version information exists, determining the virtual machine corresponding to the successfully matched virtual hardware version information as a target virtual machine which does not meet the preset version condition.
In one embodiment, the first obtaining module 401 is specifically configured to: and responding to the starting instruction of the server, and acquiring the virtual hardware version information of each installed virtual machine from the server in a preset period.
In one embodiment, the apparatus further includes a second correction module, configured to correct, when the virtual machine is a vCLS proxy virtual machine, a cpu parameter detection value included in a configuration file of the vCLS proxy virtual machine to a target parameter value, where the target parameter value is used to indicate that the vCLS proxy virtual machine is started, and the cpu parameter reading step is not performed.
In one embodiment, the apparatus further includes a second acquisition module and a de-registration module, wherein:
and the second acquisition module is used for acquiring the virtual identification information from the configuration file of the vCLS proxy virtual machine when the virtual machine is the vCLS proxy virtual machine.
And the anti-registration module is used for carrying out anti-registration processing on the vCLS proxy virtual machine according to the virtual identification information.
The modules in the virtual machine starting device may be implemented in whole or in part by software, hardware, or a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 5. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used for storing data required or generated for executing the virtual machine starting method. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, implements a virtual machine starting method.
It will be appreciated by those skilled in the art that the structure shown in fig. 5 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the method embodiments described above when the computer program is executed.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, implements the steps of the method embodiments described above.
In an embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.
It should be noted that, user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the various embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the various embodiments provided herein may include at least one of relational databases and non-relational databases. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic units, quantum computing-based data processing logic units, etc., without being limited thereto.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application shall be subject to the appended claims.
Claims (10)
1. A virtual machine starting method, wherein the method is applied to a server, and the server is deployed with a plurality of virtual machines, and the method comprises:
responding to a starting instruction of the server, and acquiring virtual hardware version information of each virtual machine installed under the server;
determining target virtual machines of which the virtual hardware version information does not accord with preset version conditions in the virtual machines;
Correcting virtual hardware version information contained in a configuration file of the target virtual machine into first target virtual hardware version information; the first target virtual hardware version information is virtual hardware version information matched with version information of a virtualized platform program suite operated by the server;
and starting the corrected virtual machines.
2. The method of claim 1, wherein modifying virtual hardware version information contained in the configuration file of the target virtual machine to first target virtual hardware version information comprises:
performing first format conversion on the configuration file of the target virtual machine in the original format to obtain the configuration file in the target format, and correcting virtual hardware version information contained in the configuration file in the target format into first target virtual hardware version information;
and carrying out second format conversion on the corrected configuration file in the target format to obtain the corrected configuration file in the original format.
3. The method of claim 1, wherein determining, in each of the virtual machines, that the virtual hardware version information does not meet the target virtual machine of the preset version condition comprises:
Matching the virtual hardware version information of each virtual machine with second target virtual hardware version information contained in a preset version information set; the second target virtual hardware version information is virtual hardware version information which is not matched with the version information of the virtualized platform program suite operated by the server;
and under the condition that the virtual hardware version information successfully matched with the second target virtual hardware version information exists, determining the virtual machine corresponding to the successfully matched virtual hardware version information as a target virtual machine which does not meet the preset version condition.
4. The method according to claim 1, wherein the obtaining, in response to the start-up instruction of the server, virtual hardware version information of each of the virtual machines installed under the server includes:
and responding to the starting instruction of the server, and acquiring the virtual hardware version information of each installed virtual machine from the server in a preset period.
5. The method of claim 1, wherein before performing the boot process on each of the virtual machines after the modification, further comprising:
and under the condition that the virtual machine is a vCLS proxy virtual machine, correcting the central processor parameter detection value contained in the configuration file of the vCLS proxy virtual machine into a target parameter value, wherein the target parameter value is used for indicating that the central processor parameter reading step is not executed when the vCLS proxy virtual machine is started.
6. The method of claim 1, wherein before performing the boot process on each of the virtual machines after the modification, further comprising:
under the condition that the virtual machine is a vCLS proxy virtual machine, virtual identification information is obtained from a configuration file of the vCLS proxy virtual machine;
and performing anti-registration processing on the vCLS proxy virtual machine according to the virtual identification information.
7. A virtual machine starting apparatus, the apparatus comprising:
the first acquisition module is used for responding to a starting instruction of a server and acquiring virtual hardware version information of each virtual machine installed under the server;
the determining module is used for determining target virtual machines, of which the virtual hardware version information does not accord with the preset version conditions, in the virtual machines;
the first correction module is used for correcting the virtual hardware version information contained in the configuration file of the target virtual machine into first target virtual hardware version information; the first target virtual hardware version information is virtual hardware version information matched with version information of a virtualized platform program suite operated by the server;
and the starting module is used for starting the corrected virtual machines.
8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 6 when the computer program is executed.
9. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.
10. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211705383.3A CN116339908A (en) | 2022-12-29 | 2022-12-29 | Virtual machine starting method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211705383.3A CN116339908A (en) | 2022-12-29 | 2022-12-29 | Virtual machine starting method, device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116339908A true CN116339908A (en) | 2023-06-27 |
Family
ID=86893591
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211705383.3A Pending CN116339908A (en) | 2022-12-29 | 2022-12-29 | Virtual machine starting method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116339908A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117591170A (en) * | 2024-01-18 | 2024-02-23 | 麒麟软件有限公司 | Method and device for supporting OSTree-based system by Loongson PMON platform and storage medium |
-
2022
- 2022-12-29 CN CN202211705383.3A patent/CN116339908A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117591170A (en) * | 2024-01-18 | 2024-02-23 | 麒麟软件有限公司 | Method and device for supporting OSTree-based system by Loongson PMON platform and storage medium |
| CN117591170B (en) * | 2024-01-18 | 2024-04-12 | 麒麟软件有限公司 | Method and device for supporting OSTree-based system by Loongson PMON platform and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3479224B1 (en) | Memory allocation techniques at partially-offloaded virtualization managers | |
| EP3479223B1 (en) | Secure booting of virtualization managers | |
| US7908521B2 (en) | Process reflection | |
| US9003239B2 (en) | Monitoring and resolving deadlocks, contention, runaway CPU and other virtual machine production issues | |
| JP6845264B2 (en) | Reducing performance variability with an opportunistic hypervisor | |
| US10146657B2 (en) | Initialization trace of a computing device | |
| US9983988B1 (en) | Resuming testing after a destructive event | |
| JP6288275B2 (en) | Virtualization infrastructure management apparatus, virtualization infrastructure management system, virtualization infrastructure management method, and virtualization infrastructure management program | |
| US10795769B2 (en) | Facilitating the identification of a service operating system when a main operating system fails | |
| US11416614B2 (en) | Statistical detection of firmware-level compromises | |
| CN116339908A (en) | Virtual machine starting method, device, computer equipment and storage medium | |
| US10268822B2 (en) | Firmware module execution privilege | |
| US11461131B2 (en) | Hosting virtual machines on a secondary storage system | |
| JP2023044720A (en) | Computer implemented method for recovering crashed application, computer program product, and remote computer server (remote recovery of crashed process) | |
| US11354109B1 (en) | Firmware updates using updated firmware files in a dedicated firmware volume | |
| CN114153503A (en) | BIOS control method, device and medium | |
| CN114722927A (en) | Collapse clustering method and device, electronic equipment and storage medium | |
| US9836315B1 (en) | De-referenced package execution | |
| US20240160994A1 (en) | Dynamic checkpoint for simulation | |
| US11720345B2 (en) | Pull based inner-loop code deployment | |
| US11531531B1 (en) | Non-disruptive introduction of live update functionality into long-running applications | |
| CN117112037A (en) | Cloud platform starting method and device, electronic equipment and storage medium | |
| CN114594975A (en) | Firmware management method and device, storage medium and electronic equipment | |
| CN113645046A (en) | Network card driver installation method, main server and medium |
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 |