BIOS (Basic Input / Output System) configuration method, device and equipment and readable storage medium

Abstract

The invention provides a BIOS configuration method, device and equipment and a readable storage medium. The method comprises the steps that in response to an abnormal event of a first BIOS system, a second BIOS system is started, a configuration obtaining request is sent to BMC equipment, BIOS configuration data fed back by the BMC equipment in response to the configuration obtaining request is obtained, and the BIOS configuration data comprises compatibility verification information; analyzing to obtain compatibility verification information, and judging whether the obtained BIOS configuration data is suitable for a second BIOS system or not according to the compatibility verification information; and in response to a judgment result suitable for the second BIOS system, configuring the second BIOS system according to the BIOS configuration data. According to the technical scheme of the invention, the BIOS configuration data contains the compatibility verification information, and the compatibility verification is carried out, so that the system abnormality caused by incompatible configuration is effectively avoided, and the stability of the server and the user experience are improved.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a BIOS configuration method, device, equipment and readable storage medium. Background Art

[0002] With the rapid development of information technology, servers, as core components of data centers and cloud computing infrastructure, have received unprecedented attention for their stability and reliability. As the underlying software for starting and managing server hardware, the importance of the server's Basic Input Output System (BIOS) is self-evident. In order to improve the reliability of BIOS, the industry has begun to adopt a dual Flash storage design, that is, configuring two Flash memories in the server to store BIOS firmware, so that when one Flash fails, it can be seamlessly switched to the other Flash to ensure the normal operation of the server.

[0003] However, the existing BIOS dual-Flash technology has some problems that need to be solved, mainly in the following aspects:

[0004] Configuration synchronization problem: When Flash1 fails and needs to be switched to Flash2, if the BIOS configurations between the two Flashes are not synchronized, users will face the tedious task of reconfiguring the BIOS, which not only increases the difficulty of operation and maintenance, but also affects the availability of the server.

[0005] Configuration compatibility issues: Due to differences in BIOS firmware versions, different versions of BIOS may have different requirements for the compatibility of configuration files. If the BIOS versions of Flash1 and Flash2 are significantly different, even if the configuration is synchronized, Flash2 may not be able to be used normally due to incompatible configurations.

[0006] Operation and maintenance convenience issues: In existing technical solutions, users often need to configure two sets of Flash BIOS separately, which undoubtedly increases the workload of operation and maintenance and reduces the efficiency of operation and maintenance. Summary of the invention

[0007] In view of this, the present specification provides a BIOS configuration method, device, electronic device, and readable storage medium to improve at least one of the above technical problems.

[0008] The specific technical solutions are as follows:

[0009] The present specification provides a BIOS configuration method, which is applied to a server, wherein the server includes a first BIOS system and a second BIOS system, and the server includes a BMC device. The method includes: in response to an abnormal event of the first BIOS system, starting the second BIOS system, sending a configuration acquisition request to the BMC device, and acquiring BIOS configuration data fed back by the BMC device in response to the configuration acquisition request, wherein the BIOS configuration data includes compatibility verification information; parsing and acquiring the compatibility verification information, and judging whether the acquired BIOS configuration data is applicable to the second BIOS system according to the compatibility verification information; in response to a judgment result that the BIOS configuration data is applicable to the second BIOS system, configuring the second BIOS system according to the BIOS configuration data; the BIOS configuration data is updated and stored by the BMC device according to the configuration update information of the first BIOS system sent by the server, and the BIOS configuration data can be updated and stored by the BMC device according to the configuration update information of the second BIOS system sent by the server.

[0010] As a technical solution, the abnormal event of the first BIOS system includes: the first BIOS system fails and cannot be started normally; or the first BIOS system is configured to be unable to be started normally at present.

[0011] As a technical solution, the compatibility verification information includes a configuration version number, and the parsing obtains the compatibility verification information, and determines whether the obtained BIOS configuration data is applicable to the second BIOS system according to the compatibility verification information, including: the parsing obtains the configuration version number, and determines whether the obtained BIOS configuration data is applicable to the second BIOS system according to the configuration version number.

[0012] As a technical solution, the configuration version number includes a major version number and a minor version number, and the major version number and the minor version number are evolved and updated according to preset rules respectively; the preset rules include: if the configuration version number is evolved and updated without verification after the BIOS firmware is pre-configured to be upgraded, the major version number is evolved and updated; if the configuration is incompatible after verification after the BIOS firmware is upgraded, the minor version number is evolved and updated; if the configuration is compatible after verification after the BIOS firmware is upgraded, the configuration version number is kept unchanged.

[0013] As a technical solution, in response to an abnormal event of the first BIOS system, the second BIOS system is started and a configuration acquisition request is sent to the BMC device, including: obtaining the non-BIOS configuration information fed back by the BMC device in response to the configuration acquisition request, and calling the default configuration to configure the current BIOS system.

[0014] The present specification also provides a BIOS configuration device, which is applied to a server, wherein the server includes a first BIOS system and a second BIOS system, and the server includes a BMC device, and the device includes: a first module, which is used to start the second BIOS system in response to an abnormal event of the first BIOS system, send a configuration acquisition request to the BMC device, and obtain BIOS configuration data fed back by the BMC device in response to the configuration acquisition request, wherein the BIOS configuration data includes compatibility verification information; a second module, which is used to parse and obtain the compatibility verification information, and determine whether the obtained BIOS configuration data is applicable to the second BIOS system according to the compatibility verification information; a third module, which is used to configure the second BIOS system according to the BIOS configuration data in response to a judgment result that the BIOS configuration data is applicable to the second BIOS system; the BIOS configuration data is updated and stored by the BMC device according to the configuration update information of the first BIOS system sent by the server, and the BIOS configuration data can be updated and stored by the BMC device according to the configuration update information of the second BIOS system sent by the server.

[0015] As a technical solution, the abnormal event of the first BIOS system includes: the first BIOS system fails and cannot be started normally; or the first BIOS system is configured to be unable to be started normally at present.

[0016] As a technical solution, the compatibility verification information includes a configuration version number, and the parsing obtains the compatibility verification information, and determines whether the obtained BIOS configuration data is applicable to the second BIOS system according to the compatibility verification information, including: the parsing obtains the configuration version number, and determines whether the obtained BIOS configuration data is applicable to the second BIOS system according to the configuration version number.

[0017] As a technical solution, the configuration version number includes a major version number and a minor version number, and the major version number and the minor version number are evolved and updated according to preset rules respectively; the preset rules include: if the configuration version number is evolved and updated without verification after the BIOS firmware is pre-configured to be upgraded, the major version number is evolved and updated; if the configuration is incompatible after verification after the BIOS firmware is upgraded, the minor version number is evolved and updated; if the configuration is compatible after verification after the BIOS firmware is upgraded, the configuration version number is kept unchanged.

[0018] As a technical solution, in response to an abnormal event of the first BIOS system, the second BIOS system is started and a configuration acquisition request is sent to the BMC device, including: obtaining the non-BIOS configuration information fed back by the BMC device in response to the configuration acquisition request, and calling the default configuration to configure the current BIOS system.

[0019] This specification also provides an electronic device, including a processor and a readable storage medium, wherein the readable storage medium stores machine executable instructions that can be executed by the processor, and the processor executes the machine executable instructions to implement the aforementioned BIOS configuration method.

[0020] This specification also provides a readable storage medium, which stores machine executable instructions. When the machine executable instructions are called and executed by a processor, the machine executable instructions prompt the processor to implement the aforementioned BIOS configuration method.

[0021] The above technical solution provided in this specification brings at least the following beneficial effects:

[0022] This technical solution includes compatibility verification information in the BIOS configuration data and performs compatibility verification when the second BIOS system is started, effectively avoiding system anomalies caused by incompatible configurations and improving server stability and user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the implementation methods of this specification or the technical solutions in the prior art, the drawings required for use in the implementation methods of this specification or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some implementation methods recorded in this specification. For ordinary technicians in this field, other drawings can also be obtained based on these drawings of the implementation methods of this specification.

[0024] Figure 1 is a flow chart of a BIOS configuration method in one implementation of this specification;

[0025] Figure 2 is a processing flow chart of BMC and BIOS in one implementation mode of this specification;

[0026] Figure 3 is a structural diagram of a BIOS configuration device in one implementation of this specification;

[0027] Figure 4 It is a hardware structure diagram of an electronic device in one implementation of this specification.

[0028] Reference numerals: first module 21 , second module 22 , third module 23 . DETAILED DESCRIPTION

[0029] The terms used in the embodiments of this specification are only for the purpose of describing specific embodiments, rather than limiting this specification. The singular forms of "a", "said" and "the" used in this specification and claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to any or all possible combinations of one or more associated listed items.

[0030] It should be understood that although the terms first, second, third, etc. may be used to describe various information in the embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, in addition, the word "if" used may be interpreted as "at the time of" or "when" or "in response to determining".

[0031] With the development of information technology and the increasing demand for data processing capabilities by enterprises, the stability and reliability of server systems have become one of the key factors in data center operations. As a bridge between hardware and operating systems, the reliability and availability of the server's basic input and output system (BIOS) directly affect the overall performance of the server.

[0032] In recent years, in order to improve the reliability of server BIOS firmware, the industry has generally adopted a BIOS dual-Flash design. This design allows the system to automatically or manually switch to the backup Flash to continue running when a problem occurs in the main Flash, thereby ensuring that there is at least one available BIOS firmware to maintain the normal operation of the server. However, although this design enhances the reliability of the system, it also brings some new challenges, especially in configuration management and maintenance.

[0033] In a technical solution of BIOS dual-Flash design, if the configuration synchronization between the two Flashes is not supported, then when the main Flash is switched to the backup Flash due to a fault, the user may need to re-set a large number of BIOS configuration options. This is a tedious task for operation and maintenance personnel, which seriously affects the operation and maintenance efficiency and user experience.

[0034] At the same time, if the BIOS configuration on the main Flash is abnormal, simply copying these configurations to the backup Flash may cause the backup Flash to also fail to boot normally. In addition, if the BIOS versions between the two Flashes are significantly different, the configuration files may also cause the BIOS on the backup Flash to also fail to work properly due to version incompatibility.

[0035] In addition, since there may be a large version difference between the two Flashes, the version compatibility of the configuration file becomes an urgent problem to be solved. If not handled properly, the configuration file may not be correctly applied when switching to the backup Flash, and the backup Flash may not be started normally.

[0036] In one technical solution, the firmware and configuration of the BIOS dual flash are relatively independent. When an abnormality occurs in the main flash, it will automatically switch to the backup flash, but the user needs to reconfigure the BIOS on the backup flash. Although this method can ensure the availability of the system, it increases the operation and maintenance burden of the user.

[0037] In another technical solution, when the main Flash fails and switches to the backup Flash, the configuration files are automatically synchronized to ensure that users can seamlessly use the BIOS on the backup Flash. However, if the BIOS versions between the main Flash and the backup Flash are significantly different or there are configuration compatibility issues, this simple configuration synchronization may cause both Flashes to not work properly.

[0038] The above problems show that the existing BIOS dual-Flash configuration management method still has shortcomings, especially in terms of configuration synchronization and compatibility. Therefore, a new solution is needed to overcome these problems and improve the practicality and user experience of BIOS dual-Flash configuration management.

[0039] The specific technical solution is described below.

[0040] In one embodiment, the present specification provides a BIOS configuration method, which is applied to a server, wherein the server includes a first BIOS system and a second BIOS system, and the server includes a BMC device. The method includes: in response to an abnormal event of the first BIOS system, starting the second BIOS system, sending a configuration acquisition request to the BMC device, and acquiring BIOS configuration data fed back by the BMC device in response to the configuration acquisition request, wherein the BIOS configuration data includes compatibility verification information; parsing and acquiring the compatibility verification information, and judging whether the acquired BIOS configuration data is applicable to the second BIOS system according to the compatibility verification information; in response to a judgment result that the data is applicable to the second BIOS system, configuring the second BIOS system according to the BIOS configuration data; the BIOS configuration data is updated and stored by the BMC device according to the configuration update information of the first BIOS system sent by the server, and the BIOS configuration data can be updated and stored by the BMC device according to the configuration update information of the second BIOS system sent by the server.

[0041] Specifically, Figure 1 , including the following steps:

[0042] Step S11, in response to an abnormal event of the first BIOS system, starting the second BIOS system, sending a configuration acquisition request to the BMC device, and acquiring BIOS configuration data fed back by the BMC device in response to the configuration acquisition request.

[0043] When an abnormality occurs in the first BIOS system, the server automatically detects and triggers the switching mechanism to start the second BIOS system. At the same time, the second BIOS system sends a configuration acquisition request to the BMC device, which contains the requirements for the current BIOS configuration and compatibility requirements.

[0044] Step S12, parsing and obtaining compatibility verification information, and determining whether the obtained BIOS configuration data is applicable to the second BIOS system according to the compatibility verification information.

[0045] After receiving the configuration acquisition request, the BMC device retrieves the stored BIOS configuration data from its non-volatile medium and feeds the data back to the second BIOS system. These configuration data include not only conventional BIOS settings, but also compatibility verification information, such as version number and compatibility identifier of configuration definition.

[0046] After receiving the BIOS configuration data, the second BIOS system first parses the compatibility check information. By comparing the version number in the configuration data with the version number of its own firmware, it determines whether the configuration data is applicable to the current system. If the version numbers are consistent or compatible, it means that the configuration data can be accepted; if they are inconsistent, further configuration adjustments or resets may be required.

[0047] Step S13, in response to the determination result that the second BIOS system is applicable, configuring the second BIOS system according to the BIOS configuration data.

[0048] If the compatibility check passes, the second BIOS system configures itself according to the acquired configuration data to ensure that the server can run according to the predetermined working parameters. This includes but is not limited to key parameters such as CPU settings, memory configuration, and boot sequence.

[0049] At the same time, the BMC device has the ability to dynamically update BIOS configuration data. When the BIOS configuration is updated during server operation, whether it comes from the first BIOS system or the second BIOS system, the BMC can receive the update information and store it in non-volatile media for use in the next switch or configuration recovery.

[0050] In one embodiment, the server is equipped with a first BIOS system (main BIOS) and a second BIOS system (backup BIOS). When the server starts, the startup information is loaded from the first BIOS system by default. If the first BIOS system fails or is abnormal, it is necessary to switch to the second BIOS system to ensure that the server can continue to run.

[0051] When an abnormality is detected in the first BIOS system, the server will automatically start the second BIOS system. This process is usually completed by the server hardware monitoring module (such as BMC). Once the second BIOS system is started, the subsequent configuration recovery process will begin.

[0052] After the second BIOS system starts, it sends a configuration acquisition request to the BMC device. This request is intended to obtain the pre-stored BIOS configuration data from the BMC device. The BMC device is a dedicated microcontroller in the server that is responsible for monitoring and managing the server status.

[0053] After receiving the configuration acquisition request, the BMC device will read the corresponding BIOS configuration data from its internal memory and send it to the second BIOS system. These configuration data are collected and stored by the BMC device when the first BIOS system is running normally, and also include compatibility verification information.

[0054] The compatibility check information is a mechanism designed to ensure that the BIOS configuration data is compatible with the currently started BIOS system version. It may contain information such as the version number and the valid range of the configuration items. When the second BIOS system receives the configuration data, it will first parse the compatibility check information.

[0055] The second BIOS system determines whether the acquired BIOS configuration data is applicable to the current system based on the compatibility check information. For example, if the version number in the configuration data matches the version number of the second BIOS system, and the valid range of the configuration item is consistent with the current system, the configuration data is considered applicable.

[0056] If the BIOS configuration data is determined to be applicable to the second BIOS system, the second BIOS system is configured according to the configuration data, which means that the second BIOS system can be quickly restored to the same configuration state as the first BIOS system, thereby ensuring the continuous availability of the server.

[0057] Assume that a server is configured as follows: main BIOS version 1.0.2, backup BIOS version 1.0.2. When the server is running normally, the first BIOS system (version 1.0.2) will periodically send configuration update information to the BMC device. The BMC device updates its internally stored BIOS configuration data based on this information and adds compatibility verification information (for example, version number 1.0.2). Assuming that there is a problem with the first BIOS system, the server will automatically start the second BIOS system (version 1.0.2). The second BIOS system sends a configuration acquisition request to the BMC device, and the BMC device returns BIOS configuration data containing compatibility verification information. The second BIOS system checks and finds that the version number is consistent with its own version. After confirming that the configuration data is applicable, it completes its own configuration according to the configuration data.

[0058] After adopting this technical solution, even if the first BIOS system is abnormal, the second BIOS system can quickly and accurately restore the configuration, significantly improving the stability and availability of the server. In addition, by adding compatibility verification information, problems caused by incompatible configurations are effectively avoided, further enhancing the reliability of the system and user experience.

[0059] In one embodiment, when the server detects an abnormality in the first BIOS system (Flash1), the system automatically or manually switches to the second BIOS system (Flash2). At this time, before the Setup phase during the startup of the second BIOS system, a configuration acquisition request is sent to the BMC device. The BMC device responds to this request and returns the BIOS configuration data stored therein. These configuration data include compatibility verification information, which is used to determine whether the configuration file is applicable to the current BIOS version.

[0060] After receiving the BIOS configuration data, the second BIOS system first parses the compatibility check information. The compatibility check information includes the version number of the configuration file, which is managed in two stages and is divided into a major version number and a minor version number. The major version number (such as 1) identifies the software version change, which means that the configuration is likely to be incompatible with the previous version; the minor version number (such as 2) identifies the change in the configuration definition within the same generation of software. If the configuration is incompatible with the old version, the minor version number is incremented.

[0061] Major version number: When developing the next generation of firmware, the configuration will most likely not be compatible with the current version, so the major version number is incremented by 1.

[0062] Minor version number: When the definition of the configuration modified by the same generation of firmware is not compatible with the old version of the same generation, the minor version number is incremented by 1.

[0063] Based on this information, the second BIOS system will determine whether the configuration file is applicable to the current BIOS version. If the version numbers are consistent, the configuration can be used directly; if they are inconsistent, it indicates that the configuration is incompatible, and the second BIOS system will not apply these configurations, but choose to use the default configuration or other available configurations.

[0064] Once the BIOS configuration data is confirmed to be applicable to the second BIOS system, the system will complete the configuration of the second BIOS system according to these configuration data. This step ensures that even if the first BIOS system fails, the normal operation of the system and the user's configuration preferences can be maintained as much as possible.

[0065] In one embodiment, the server is running an operating system based on a first BIOS system, but the first BIOS system cannot work properly due to a hardware failure. At this time, the server automatically detects the abnormality and starts the second BIOS system. The second BIOS system sends a configuration acquisition request to the BMC, and the BMC provides a configuration data containing compatibility verification information based on the configuration update information sent by the first BIOS system when it is running normally.

[0066] The second BIOS system parses this data and finds that both the major and minor version numbers are compatible with itself. Based on this information, the second BIOS system configures itself to match the server's hardware and operating system requirements. For example, if the server configuration includes CPU frequency settings, memory timings, and boot order, the second BIOS system will apply these settings to ensure seamless switching and system stability.

[0067] In addition, in daily operation and maintenance, the administrator may make some customized configuration changes to the first BIOS system, such as enabling specific hardware features or adjusting power management settings. These changes will be synchronized to the BMC in real time. Once it is necessary to switch to the second BIOS system, the BMC can provide the latest configuration data that has been verified for compatibility, thus avoiding the tedious work of repeated configuration.

[0068] Through this intelligent BIOS configuration management method, the server can not only quickly respond to single point failures, but also ensure configuration consistency and high availability of the system, greatly improving the efficiency of server operation and maintenance and user experience.

[0069] In one implementation, the event of the first BIOS system being abnormal includes: the first BIOS system fails and cannot be normally started; or the first BIOS system is configured to be currently unable to be normally started.

[0070] In one embodiment, the compatibility verification information includes a configuration version number, and the parsing to obtain the compatibility verification information, and judging whether the obtained BIOS configuration data is applicable to the second BIOS system according to the compatibility verification information, includes: the parsing to obtain the configuration version number, and judging whether the obtained BIOS configuration data is applicable to the second BIOS system according to the configuration version number.

[0071] In one embodiment, the configuration version number includes a major version number and a minor version number, and the major version number and the minor version number are evolved and updated according to preset rules respectively; the preset rules include: if the configuration version number is evolved and updated without verification after the BIOS firmware is pre-configured to be upgraded, the major version number is evolved and updated; if the configuration is verified to be incompatible after the BIOS firmware is upgraded, the minor version number is evolved and updated; if the configuration is verified to be compatible after the BIOS firmware is upgraded, the configuration version number is kept unchanged.

[0072] In one embodiment, in response to an abnormal event of the first BIOS system, starting the second BIOS system and sending a configuration acquisition request to the BMC device includes: acquiring non-BIOS configuration information fed back by the BMC device in response to the configuration acquisition request, and calling the default configuration to configure the current BIOS system.

[0073] In one embodiment, if Figure 2 In order to identify whether the configuration is common to the firmware in the two Flashes, the configuration is managed in a two-part version number (for example: 1.2). The configuration version number is stored in the header of the configuration file:

[0074] In the above example, "1" represents the major version number. When the next generation of firmware is developed, the configuration will most likely not be compatible with the current version, so the major version number is incremented by 1.

[0075] In the above example, "2" represents the minor version number. When the definition of the modified configuration of the same generation of firmware is not compatible with the old version of the same generation, this process requires compatibility verification or manual configuration, and the minor version number is incremented by 1.

[0076] During the BIOS startup process, before the Setup phase, the currently stored configuration file will be obtained from the BMC. If the currently stored configuration is obtained, the version information of the configuration file will be further verified. If the version numbers are consistent, it will be used directly. If the version numbers are inconsistent, it means that they are incompatible and will be discarded. During the BIOS startup process, the Setup phase ends and the current configuration is sent to the BMC before the OS is started.

[0077] When the BMC receives the configuration file passed by the BIOS, it will update it to the non-volatile media and delete the original configuration file. The BMC side only saves the configuration passed by the BIOS for the most recent time. If it is located that the configuration has been abnormally tampered with and the BIOS cannot run normally, the BIOS factory configuration can be restored through the BMC, that is, the BIOS configuration file saved by the BMC is deleted and the BIOS is restarted. When the BIOS firmware is upgraded online through the BMC, the firmware verification stage determines whether the configuration version supported by the firmware is compatible with the currently stored configuration version: if compatible, the optional configuration retention upgrade (retain the configuration file) or configuration overwrite upgrade (delete the configuration file); if incompatible, the user is reminded that only the configuration overwrite upgrade can be selected, and the saved configuration file will be cleared when the upgrade is executed.

[0078] In one embodiment, if Figure 3 The present specification also provides a BIOS configuration device, which is applied to a server, wherein the server includes a first BIOS system and a second BIOS system, and the server includes a BMC device. The device includes: a first module, which is used to start the second BIOS system in response to an abnormal event of the first BIOS system, send a configuration acquisition request to the BMC device, and obtain BIOS configuration data fed back by the BMC device in response to the configuration acquisition request, wherein the BIOS configuration data includes compatibility verification information; a second module, which is used to parse and obtain the compatibility verification information, and determine whether the obtained BIOS configuration data is applicable to the second BIOS system according to the compatibility verification information; a third module, which is used to configure the second BIOS system according to the BIOS configuration data in response to the determination result that the BIOS configuration data is applicable to the second BIOS system; the BIOS configuration data is updated and stored by the BMC device according to the configuration update information of the first BIOS system sent by the server, and the BIOS configuration data can be updated and stored by the BMC device according to the configuration update information of the second BIOS system sent by the server.

[0079] In one implementation, the event of the first BIOS system being abnormal includes: the first BIOS system fails and cannot be normally started; or the first BIOS system is configured to be currently unable to be normally started.

[0080] In one embodiment, the compatibility verification information includes a configuration version number, and the parsing to obtain the compatibility verification information, and judging whether the obtained BIOS configuration data is applicable to the second BIOS system according to the compatibility verification information, includes: the parsing to obtain the configuration version number, and judging whether the obtained BIOS configuration data is applicable to the second BIOS system according to the configuration version number.

[0081] In one embodiment, the configuration version number includes a major version number and a minor version number, and the major version number and the minor version number are evolved and updated according to preset rules respectively; the preset rules include: if the configuration version number is evolved and updated without verification after the BIOS firmware is pre-configured to be upgraded, the major version number is evolved and updated; if the configuration is verified to be incompatible after the BIOS firmware is upgraded, the minor version number is evolved and updated; if the configuration is verified to be compatible after the BIOS firmware is upgraded, the configuration version number is kept unchanged.

[0082] In one embodiment, in response to an abnormal event of the first BIOS system, starting the second BIOS system and sending a configuration acquisition request to the BMC device includes: acquiring non-BIOS configuration information fed back by the BMC device in response to the configuration acquisition request, and calling the default configuration to configure the current BIOS system.

[0083] The device implementation is the same as or similar to the corresponding method implementation, and will not be described in detail here.

[0084] In one embodiment, the present specification provides an electronic device, including a processor and a readable storage medium, wherein the readable storage medium stores machine executable instructions that can be executed by the processor, and the processor executes the machine executable instructions to implement the aforementioned BIOS configuration method. From a hardware level, the hardware architecture diagram can be seen in Figure 4 shown.

[0085] In one embodiment, the present specification provides a readable storage medium, wherein the readable storage medium stores machine executable instructions, and when the machine executable instructions are called and executed by a processor, the machine executable instructions prompt the processor to implement the aforementioned BIOS configuration method.

[0086] Here, the readable storage medium can be any electronic, magnetic, optical or other physical storage device that can contain or store information, such as executable instructions, data, etc. For example, the readable storage medium can be: RAM (Radom Access Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as hard disk drive), solid state drive, any type of storage disk (such as CD, DVD, etc.), or similar storage medium, or a combination thereof.

[0087] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, a game console, a tablet computer, a wearable device or a combination of any of these devices.

[0088] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0089] It will be appreciated by those skilled in the art that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, this specification may be in the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this specification may be in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0090] This specification is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0091] Moreover, these computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0092] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0093] It will be appreciated by those skilled in the art that the embodiments of the present specification may be provided as methods, systems or computer program products. Therefore, the present specification may be in the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present specification may be in the form of a computer program product implemented on one or more computer-usable storage media (which may include but are not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0094] The above description is only an embodiment of the present specification and is not intended to limit the present specification. For those skilled in the art, the present specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification shall be included in the scope of the claims of the present specification.

Claims

1. A BIOS configuration method, characterized in that: Applied to a server, the server includes a first BIOS system and a second BIOS system, the server includes a BMC device, and the method includes: In response to an abnormal event of the first BIOS system, starting the second BIOS system, sending a configuration acquisition request to the BMC device, and acquiring BIOS configuration data fed back by the BMC device in response to the configuration acquisition request, wherein the BIOS configuration data includes compatibility verification information; Parse and obtain compatibility verification information, and determine whether the obtained BIOS configuration data is applicable to the second BIOS system according to the compatibility verification information; In response to the determination result that the second BIOS system is applicable, configuring the second BIOS system according to the BIOS configuration data; The BIOS configuration data is updated and stored by the BMC device according to configuration update information of the first BIOS system sent by the server, and the BIOS configuration data can be updated and stored by the BMC device according to configuration update information of the second BIOS system sent by the server.

2. The method according to claim 1, characterized in that The first BIOS system abnormal events include: The first BIOS system fails and cannot be started normally; Or, the first BIOS system is configured to be unable to be normally started at present.

3. The method according to claim 1, characterized in that The compatibility check information includes a configuration version number, and the parsing to obtain the compatibility check information, and judging whether the obtained BIOS configuration data is applicable to the second BIOS system according to the compatibility check information, includes: The parsing obtains the configuration version number, and determines whether the obtained BIOS configuration data is applicable to the second BIOS system according to the configuration version number.

4. The method according to claim 3, characterized in that The configuration version number includes a major version number and a minor version number, and the major version number and the minor version number are respectively evolved and updated according to preset rules; The preset rules include: If the BIOS firmware is pre-configured to be updated without verification after upgrading, the major version number is updated; If the BIOS firmware is upgraded and the configuration is confirmed to be incompatible, the minor version number will be updated; If the BIOS firmware is upgraded and the configuration is confirmed to be compatible, the configuration version number remains unchanged.

5. The method according to claim 1, characterized in that In response to an event that the first BIOS system is abnormal, starting the second BIOS system and sending a configuration acquisition request to the BMC device include: The non-BIOS configuration information fed back by the BMC device in response to the configuration acquisition request is acquired, and the default configuration is called to configure the current BIOS system.

6. A BIOS configuration device, characterized in that: Applied to a server, the server includes a first BIOS system and a second BIOS system, the server includes a BMC device, and the apparatus includes: The first module is used to start the second BIOS system in response to an abnormal event of the first BIOS system, send a configuration acquisition request to the BMC device, and obtain BIOS configuration data fed back by the BMC device in response to the configuration acquisition request, wherein the BIOS configuration data includes compatibility verification information; The second module is used to parse and obtain compatibility verification information, and determine whether the obtained BIOS configuration data is applicable to the second BIOS system according to the compatibility verification information; A third module, configured to configure the second BIOS system according to the BIOS configuration data in response to the determination result applicable to the second BIOS system; The BIOS configuration data is updated and stored by the BMC device according to configuration update information of the first BIOS system sent by the server, and the BIOS configuration data can be updated and stored by the BMC device according to configuration update information of the second BIOS system sent by the server.

7. The device according to claim 6, characterized in that The first BIOS system abnormal events include: The first BIOS system fails and cannot be started normally; Or, the first BIOS system is configured to be unable to be normally started at present.

8. The device according to claim 6, characterized in that The compatibility check information includes a configuration version number, and the parsing to obtain the compatibility check information, and judging whether the obtained BIOS configuration data is applicable to the second BIOS system according to the compatibility check information, includes: The parsing obtains the configuration version number, and determines whether the obtained BIOS configuration data is applicable to the second BIOS system according to the configuration version number.

9. The device according to claim 8, characterized in that The configuration version number includes a major version number and a minor version number, and the major version number and the minor version number are respectively evolved and updated according to preset rules; The preset rules include: If the BIOS firmware is pre-configured to be updated without verification after upgrading, the major version number is updated; If the BIOS firmware is upgraded and the configuration is confirmed to be incompatible, the minor version number will be updated; If the BIOS firmware is upgraded and the configuration is confirmed to be compatible, the configuration version number remains unchanged.

10. The device according to claim 6, characterized in that In response to an event that the first BIOS system is abnormal, starting the second BIOS system and sending a configuration acquisition request to the BMC device include: The non-BIOS configuration information fed back by the BMC device in response to the configuration acquisition request is acquired, and the default configuration is called to configure the current BIOS system.

11. An electronic device, characterized in that: include: A processor and a readable storage medium, wherein the readable storage medium stores machine executable instructions that can be executed by the processor, and the processor executes the machine executable instructions to implement any method described in claims 1-5.

12. A readable storage medium, characterized in that: The readable storage medium stores machine executable instructions, and when the machine executable instructions are called and executed by a processor, the machine executable instructions prompt the processor to implement any one of the methods of claims 1-5.

Images