Server startup display method and device

Abstract

This application discloses a server startup display method and device, relating to the field of server technology. The method comprises: when a server is started, running a server startup system; displaying server information on a startup interface of the startup system, and displaying startup progress information on the startup interface, wherein the server information is used to display the server configuration status, and the startup progress information is used to display the server startup progress; and updating the startup progress information based on the operation status of the startup system. This application can solve the technical problem of poor transparency in the server startup process in related technologies, thereby achieving the technical effect of improving the transparency of the server startup process and thus enhancing the user experience.

Description

Technical Field

[0001] The present application relates to the field of server technology, and in particular to a method and device for displaying startup of a server. Background Art

[0002] With the continuous development of servers, the user experience has become an increasing focus in the server industry. In related technologies, after pressing the server startup button, users must wait for the server to complete the startup process. This process is often a black box operation for users, during which they cannot obtain any information about the server. The transparency of the server startup process is poor, resulting in a poor user experience. Summary of the Invention

[0003] The present application provides a server startup display method and device to at least solve the problem of poor transparency of the server startup process in the related art.

[0004] The present application provides a server startup display method, comprising: when the server is started, running the server startup system; displaying server information on a startup interface of the startup system, and displaying startup progress information on the startup interface, wherein the server information is used to display the configuration status of the server, and the startup progress information is used to display the startup progress of the server; and updating the startup progress information according to the operation status of the startup system.

[0005] The present application also provides a server startup display device, including: an operation module, which is used to run the server startup system when the server is started; a first display module, which is used to display server information on the startup interface of the startup system and display startup progress information on the startup interface, wherein the server information is used to display the configuration status of the server, and the startup progress information is used to display the startup progress of the server; an update module, which is used to update the startup progress information according to the operation status of the startup system.

[0006] The present application also provides an electronic device, comprising: a memory for storing a computer program; and a processor for implementing the steps of any of the above-mentioned server startup display methods when executing the computer program.

[0007] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned server startup display methods are implemented.

[0008] The present application also provides a computer program product, including a computer program, which implements the steps of any of the above-mentioned server startup display methods when the computer program is executed by a processor.

[0009] Through the present application, when the server is started, the server startup system is run, and server information for displaying the configuration status of the server is displayed on the startup interface of the startup system, and startup progress information for displaying the startup progress of the server is displayed on the startup interface. The startup progress information is updated according to the operation status of the startup system. The user can also obtain the server configuration status and the server startup progress during the server startup process, thereby improving the transparency of the server startup process. Therefore, the technical problem of poor transparency of the server startup process in the related art can be solved, and the technical effect of improving the transparency of the server startup process and thus improving the user experience can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0011] Figure 1 This is a hardware structure diagram of the server startup display method of an embodiment of the present application;

[0012] Figure 2 is a flow chart of a method for starting and displaying a server according to an embodiment of the present application;

[0013] Figure 3 is a schematic diagram of a configuration file according to an embodiment of the present application;

[0014] Figure 4 is a schematic diagram of interaction between a controller and a starting system according to an embodiment of the present application;

[0015] Figure 5 This is a process of a method for selecting a configuration file on a startup interface through a controller according to an embodiment of the present application. Figure 1 ;

[0016] Figure 6 This is a process of a method for selecting a configuration file on a startup interface through a controller according to an embodiment of the present application. Figure 2 ;

[0017] Figure 7 is a schematic diagram of a fault weight adjustment method according to an embodiment of the present application;

[0018] Figure 8 This is a schematic diagram of a startup interface according to an embodiment of the present application. Figure 1 ;

[0019] Figure 9This is a schematic diagram of a startup interface according to an embodiment of the present application. Figure 2 ;

[0020] Figure 10 This is a schematic diagram of a startup interface according to an embodiment of the present application. Figure 3 ;

[0021] Figure 11 This is a schematic diagram of a startup interface according to an embodiment of the present application. Figure 4 ;

[0022] Figure 12 This is a schematic diagram of a startup interface according to an embodiment of the present application. Figure 5 ;

[0023] Figure 13 This is a schematic diagram of a startup interface according to an embodiment of the present application. Figure 6 ;

[0024] Figure 14 This is a schematic diagram of a startup interface according to an embodiment of the present application. Figure 7 ;

[0025] Figure 15 This is a structural block diagram of a server startup display device according to an embodiment of the present application. DETAILED DESCRIPTION

[0026] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0027] It should be noted that, in the description of this application, the terms "comprises," "includes," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. The terms "first," "second," etc., in this application are used to distinguish similar objects, and are not used to describe a particular order or sequence.

[0028] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0029] In conjunction with the specific application environment architecture or specific hardware architecture on which the execution of the server startup display method depends, the specific application environment architecture or specific hardware architecture is described herein.

[0030] The method embodiments provided in the embodiments of the present application can be executed in a server device or a similar computing device. Taking running on a server device as an example, Figure 1 This is a hardware structure diagram of the server startup display method of the embodiment of the present application. Figure 1 As shown, the server device may include one or more ( Figure 1 Only one is shown) a processor 102 (the processor 102 may include but is not limited to a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data. The server device may also include a transmission device 106 and an input / output device 108 for communication functions. It will be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above server device. Figure 1 More or fewer components than shown, or with Figure 1 Different configurations shown.

[0031] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the startup display method of the server in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, implementing the above-mentioned method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely located relative to the processor 102, and these remote memories can be connected to the server device via a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0032] Transmission device 106 is used to receive or transmit data via a network. A specific example of the aforementioned network may include a wireless network provided by a communication provider of the server device. In one embodiment, transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0033] An embodiment of the present application provides a method for starting and displaying a server, and the method is described in detail in conjunction with the execution flow of the method for starting and displaying a server.

[0034] In this embodiment, a method for starting and displaying a server is provided. Figure 2 Flowchart of the method for starting display of the server according to the embodiment of the present application, as shown in FIG. Figure 2 As shown, the method includes the following steps:

[0035] Step S202: When the server is started, the server startup system is run;

[0036] Step S204: displaying server information on a startup interface of the startup system, and displaying startup progress information on the startup interface, wherein the server information is used to display the configuration of the server, and the startup progress information is used to display the startup progress of the server;

[0037] Step S206: updating the startup progress information according to the operation status of the startup system.

[0038] Through the above steps, when the server is started, the server startup system is run, and server information for displaying the configuration status of the server is displayed on the startup interface of the startup system, and startup progress information for displaying the startup progress of the server is displayed on the startup interface. The startup progress information is updated according to the operation status of the startup system. The user can also obtain the server configuration status and the server startup progress during the server startup process, thereby improving the transparency of the server startup process. Therefore, the technical problem of poor transparency of the server startup process in the related art can be solved, and the technical effect of improving the transparency of the server startup process and thus improving the user experience can be achieved.

[0039] In the embodiment provided in step S202, the server startup can be triggered by, but is not limited to, the following methods: directly operating a physical switch on the server, such as pressing a power button; remote startup, i.e., starting the server via a network using a remote management tool such as the IPMI (Intelligent Platform Management Interface) protocol; software-triggered startup, i.e., starting the server via certain software or operating system commands. This application does not limit the method for triggering the server startup.

[0040] Optionally, in this embodiment, the server's boot system may refer to, but is not limited to, a series of firmware programs and software that are first run after the server is powered on. The server's boot system may be responsible for, but is not limited to, initializing hardware resources, detecting hardware status, loading the operating system kernel, and completing the entire system boot process. The server's boot system may include, but is not limited to, BIOS (Basic Input / Output System) or UEFI (Unified Extensible Firmware Interface).

[0041] In the embodiment provided in step S204, the startup interface may be displayed by, but is not limited to, a display device of the server. The display device of the server may display, but is not limited to, the startup interface during the startup process of the server and / or display the function interface of the server during the operation process after the server is started.

[0042] Optionally, in this embodiment, the startup interface can be used but is not limited to displaying relevant information during the server startup process, for example, it can be used but is not limited to displaying server information used to show the configuration status of the server, it can also be used but is not limited to displaying startup progress information used to indicate the startup progress of the server, it can also be used but is not limited to displaying system operations that can be performed during the startup process, etc.

[0043] Optionally, in this embodiment, the server information can be used but is not limited to displaying the configuration status of the server, can be but is not limited to all system configuration items of the server, and can be but is not limited to some system configuration items of all system configuration items of the server. This application does not impose any restrictions on this.

[0044] Optionally, in this embodiment, the server information displayed on the startup interface may be, but is not limited to, fixed, or may be, but is not limited to, flexibly changeable.

[0045] Optionally, in this embodiment, the startup progress information may be used for, but not limited to, displaying the startup progress of the server, and the startup progress information may refer to, but not limited to, the percentage of the currently completed startup process in the total startup process.

[0046] Optionally, in this embodiment, server information is displayed on the startup interface of the startup system, and startup progress information is displayed on the startup interface. It can be, but is not limited to, inserting multiple startup progress parameters into the server information for display, and the startup progress information includes multiple startup progress parameters, and these multiple startup progress parameters respectively represent different startup progress. For example, it can be, but is not limited to, displaying a first startup progress parameter on the first line of the startup interface, wherein the first startup progress parameter is used to indicate that the startup progress of the current server is 0; displaying server information on the second and subsequent lines of the display interface, and continuously paying attention to the operation status of the server's startup system during the display process; when the operation status of the startup system indicates that the startup progress is 50%, displaying the second startup progress parameter on the latest line of the current startup interface that does not display content; and when the operation status of the startup system indicates that the startup progress is 100%, displaying the third startup progress parameter on the latest line of the current startup interface that does not display content, wherein the second startup progress parameter is used to indicate that the startup progress of the current server is 50%, and the third startup progress parameter is used to indicate that the startup progress of the current server is 100%.

[0047] In the embodiment provided in step S206, the boot progress information can be updated based on the operation status of the boot system, but is not limited to it. During the server boot process, the boot system (such as BIOS or UEFI firmware) plays a core role. The boot system is responsible for initializing the hardware, loading the operating system kernel, executing the pre-boot software, etc. Each step in the boot system's operation process can be regarded as a measurable event or state, and the progress of these events or states can be used to reflect the progress of the overall server boot. It is possible to establish a correspondence between multiple steps in the boot system and the server's boot progress, but is not limited to it. When it is detected that the boot system has run to a certain step, the boot progress information is updated using the boot progress corresponding to the step.

[0048] As an optional implementation manner, displaying the server information on the startup interface of the startup system includes: displaying the target configuration item as the server information on the startup interface, wherein the system configuration items of the startup system include the target configuration item.

[0049] Optionally, in this embodiment, system configuration items may refer to, but are not limited to, various parameters and settings configurable in the server startup system. System configuration items may determine, but are not limited to, the server's startup behavior, performance characteristics, and the types of information to be displayed. These configuration items may cover everything from hardware configuration (such as detailed information about the CPU (Central Processing Unit), memory, storage, and network interfaces) to system behavior configuration (such as fault diagnosis mode and priority of displayed information).

[0050] Optionally, in this embodiment, the target configuration item may be, but is not limited to, a subset of the system configuration item, and the target configuration item may be, but is not limited to, specific configuration information that the user or operation and maintenance personnel want to view or pay attention to when the server is started.

[0051] Optionally, in this embodiment, displaying the target configuration item as server information on the startup interface may include, but is not limited to, displaying specific configuration information that the user or operation and maintenance personnel is concerned about on the startup interface, so that the user or operation and maintenance personnel can obtain this information more quickly.

[0052] As an optional implementation, the target configuration item includes at least one of the following: first version information, generation information, memory information, second version information, third version information, fourth version information, and address information. The first version information is used to indicate the processor version of the server, the generation information is used to indicate the processor generation of the server, the memory information is used to indicate the memory capacity of the server, the second version information is used to indicate the version number of the startup system, the third version information is used to indicate the version release time of the startup system, the fourth version information is used to indicate the controller version of the server, and the address information is used to indicate the controller address of the server.

[0053] Optionally, in this embodiment, the first version information may be, but is not limited to, used to indicate a processor version of the server, and the first version information may be, but is not limited to, include an RC (Reference Code) version, that is, a basic code version number.

[0054] Optionally, in this embodiment, the generation information may be, but is not limited to, used to indicate the generation of the server's processor. More specifically, the generation information may be, but is not limited to, used to indicate which generation of the server's central processing unit belongs to the processor manufacturer.

[0055] Optionally, in this embodiment, the second version information may be, but is not limited to, used to indicate the version number of the boot system. More specifically, the second version information may be, but is not limited to, including the version number of the BIOS.

[0056] Optionally, in this embodiment, the third version information may be, but is not limited to, used to indicate the release time of the boot system version, i.e., the time when the boot system version indicated by the second version information was officially released to the public or provided to users. More specifically, the third version information may include, but is not limited to, the version time of the BIOS.

[0057] Optionally, in this embodiment, the fourth version information may be, but is not limited to, used to indicate the version of the server controller. Optionally, the server controller may be, but is not limited to, a BMC (Baseboard Management Controller). More specifically, the fourth version information may include, but is not limited to, the BMC version number.

[0058] Optionally, in this embodiment, the address information may be, but is not limited to, an address of a controller indicating a server. More specifically, the address information may be, but is not limited to, an IP address (Internet Protocol Address) of a BMC.

[0059] As an optional implementation, displaying the target configuration item as server information on the startup interface includes: reading the target identifier configured by the target configuration item from the system configuration item; searching for the target configuration file corresponding to the target identifier from the identifiers and configuration files with corresponding relationships; and displaying the file content of the target configuration file on the startup interface as server information.

[0060] Optionally, in this embodiment, the identifier can be, but is not limited to, a unique code or name used to distinguish different configuration files. In the server startup process, the identifier can be the name of the configuration file (such as "Basic Information" or "Fault Diagnosis") or a numerical value (such as "1" or "2") for indexing and selection.

[0061] Optionally, in this embodiment, the target configuration item can be filtered out from the system configuration items by selecting an identifier, but is not limited to the method.

[0062] Optionally, in this embodiment, the identifier and the configuration file may be, but not limited to, one-to-one corresponding, and the content to be displayed on the startup interface may be found by searching for the target configuration file corresponding to the target identifier from the identifiers and configuration files having corresponding relationships, but not limited to.

[0063] Optionally, in this embodiment, Figure 3 Schematic diagram of a configuration file according to an embodiment of the present application. Figure 3As shown, a series of configuration files can be added to the BIOS (i.e., the boot system) but are not limited to being added, and these configuration files are synchronized to the BMC. These configuration files mainly include different categories of information (i.e., file content). For example, the name of configuration file one is "Basic Information" (i.e., identification), and its option value is "1" (i.e., identification). The content to be displayed under this configuration file (i.e., target configuration items) includes: CPU model, CPU basic parameters, memory model (including memory manufacturer and model parameters), memory basic parameters (including capacity information and speed), BIOS, BMC firmware version number, BMC IP information, date and time information, performance and energy consumption scenario mode, hardware anti-counterfeiting information, etc.; the name of configuration file two is "Fault Diagnosis", and its option value is "2" (i.e., identification). The content to be displayed under this configuration file (i.e., target configuration items) includes: fault diagnosis mode, BIOS, BMC firmware version number, whether there is a component fault (CE (Correctable Error) or UCE (Uncorrectable Error) Configuration file three is named "Device Asset Information" and its option value is "3" (i.e., identifier). The content displayed in this configuration file (i.e., target configuration items) includes the names, serial numbers (SNs), physical silkscreen information, and other parameters of installed hard drives (such as HDDs (Hard Disk Drives), SSDs (Solid State Drives), NVMe SSDs (Non-Volatile Memory Express Solid State Drives), and M.2 hard drives), PCIe (Peripheral Component Interconnect Express) add-in cards, OCP (Open Compute Project) cards, and USB (Universal Serial Bus) devices.

[0064] Optionally, in this embodiment, the file contents in each configuration file can be, but are not limited to, modifiable. For example, for the aforementioned configuration file one, the user or operation and maintenance personnel can, but are not limited to, delete the "date and time information" from the content to be displayed in configuration file one, and the user or operation and maintenance personnel can, but are not limited to, add the "date and time information" to the content to be displayed in configuration file two.

[0065] Through the above content, the file content of the target configuration file corresponding to the target identifier is displayed as server information on the startup interface. Compared with the solution that can only display fixed server information, the display solution of this application is more flexible.

[0066] As an optional implementation, the target identifier can be selected in the following manner before the target identifier configured by the target configuration item is read from the system configuration item, but is not limited to: a display configuration tab is displayed in the configuration tab of the startup system, wherein the display configuration tab is used to select the identifier of the configuration file to be displayed in the server startup phase from multiple identifiers; and the identifier among the multiple identifiers that is triggered by the selection operation is determined as the target identifier.

[0067] Optionally, in this embodiment, the configuration tab of the startup system may be, but is not limited to, displayed on the startup system.

[0068] Optionally, in this embodiment, multiple identifiers may be displayed on the display configuration tab, each identifier corresponding to a configuration file. The user may, but is not limited to, select the identifier of the configuration file to be displayed during the server startup phase from the multiple identifiers through the display configuration tab.

[0069] Optionally, in this embodiment, triggering a selection operation may refer to, but is not limited to, a user or operator performing a selection action on the display configuration tab of the startup system to select a specific configuration file to be displayed during the server startup phase. The selection operation may refer to, but is not limited to, the user or operator selecting an identifier using an interactive element (such as a mouse, keyboard, or touchscreen) within the display configuration tab interface. This selection action may be a click, touch, arrow key selection followed by pressing Enter, or other means to explicitly designate a configuration file as the target configuration file to be displayed. The identifier selected by the user is the target identifier.

[0070] As an optional implementation, displaying the display configuration tab in the configuration tab of the startup system includes: displaying the display configuration tab in the configuration tab of the startup system on the controller of the server.

[0071] Optionally, in this embodiment, the configuration tab of the startup system may be, but is not limited to, displayed on the controller of the server.

[0072] Optionally, in this embodiment, the controller of the server may refer to, but is not limited to, a dedicated microcontroller responsible for server management, monitoring, and control functions, and the controller may include, but is not limited to, a BMC. BMC is a dedicated controller embedded in the server motherboard, used to monitor and manage the server hardware status, including but not limited to temperature, voltage, fan speed, etc., and can remotely control the server's power on, power off, reset, and other operations. Since the startup system only runs during the server's startup process, the startup system will be shut down after the server startup is completed. Displaying the display configuration tab in the startup system's configuration tab on the startup system will result in the configuration file to be displayed only being selected during the server's startup process. Displaying the display configuration tab in the startup system's configuration tab on the server's controller will provide the user with the opportunity to select the configuration file to be displayed during the entire server operation process. The user can select the configuration file to be displayed on the server's startup interface at any stage of the server's operation, and each selection will take effect the next time the server starts.

[0073] Optionally, in this embodiment, displaying the configuration tab in the configuration tab of the startup system on the server's controller may be, but is not limited to, displaying the configuration tab directly on the controller's display interface. A user or operation and maintenance personnel may, but is not limited to, directly perform a selection operation on the controller's display interface to determine a target identifier from multiple identifiers. The selection operation in this case may be, but is not limited to, clicking, etc. Alternatively, a user or operation and maintenance personnel may, but is not limited to, determine the target identifier from multiple identifiers through the server's operating system and send an IPMI command or an API (Application Programming Interface) command to the BMC through the operating system to select the target identifier from multiple identifiers. This operation may be performed by entering a specific IPMI command in a command line interface or by using a graphical management tool on the operating system.

[0074] Optionally, in this embodiment, each configuration file may have, but is not limited to, multiple forms of identifiers, which may be in numerical form or text form. For example, the identifier of a configuration file may be the text "basic information" and the numerical value "1". Numerical identifiers and text identifiers may be, but are not limited to, directly recognized in different devices. For example, the controller and the boot system may be, but are not limited to, directly recognized in numerical form, while the server's operating system may be, but are not limited to, directly recognized in text form. When a user or operation and maintenance personnel uses the server's operating system to determine a target identifier from multiple identifiers, the required text target identifier may be selected from the multiple text identifiers, and the text target identifier may be sent to the controller through the IPMI command under the operating system. After receiving the text target identifier, the controller matches the text target identifier with a corresponding numerical target identifier from the text identifiers and numerical identifiers that have a corresponding relationship.

[0075] As an optional implementation, an identifier among multiple identifiers that has triggered a selection operation is determined as a target identifier, including: the controller saving the target identifier to the option information of the startup system on the controller; the controller sending a modification instruction to the startup system through a transmission channel between the controller and the startup system, wherein the modification instruction is used to instruct to modify the identifier configured by the target configuration item to the target identifier; and the startup system executing the modification instruction.

[0076] Optionally, in this embodiment, the target identifier selected by the user through the display configuration tab displayed by the configuration tab of the controller's startup system can be transmitted to the startup system by sending a modification instruction, but is not limited to the method. After receiving the modification instruction, the startup system can, but is not limited to, modify the identifier configured in the target configuration item to the target identifier.

[0077] Optionally, in this embodiment, Figure 4 Schematic diagram of the interaction between a controller and a startup system according to an embodiment of the present application. Figure 4 As shown, a display configuration tab can be added in the BIOS (i.e., the boot system) but is not limited to, and is used to select various configuration files. A display configuration tab can also be added in the BMC (i.e., the controller) interface to support users in selecting different configuration files. Figure 4As shown, operators can select a configuration file (i.e., the target configuration file) by sending IPMI commands to the BMC in-band within the operating system (OS) or through the BMC interface. Users or operators can also query configuration files using IPMI commands. The IPMI commands used to read or write these configuration files are OEM (Original Equipment Manufacturer) commands and are provided to users or operators by the server manufacturer.

[0078] Optionally, in this embodiment, Figure 5 This is a process of a method for selecting a configuration file on a startup interface through a controller according to an embodiment of the present application. Figure 1 .like Figure 5 As shown, after the operation and maintenance personnel complete the selection of the display configuration tab (i.e., "Display Configuration" selection) on the BMC (i.e., controller) interface, the BMC will modify the locally saved BIOS option information (i.e., the system startup option information) and store the modified BIOS option information in the BMC's EEPROM (Electrically Erasable Programmable Read-Only Memory). The BMC will also send the modified option information (i.e., the target identifier modification) to the BIOS in the format of a JSON (JavaScript Object Notation) file through the Redfish channel. Before this process is completed, the BMC will reject operations from IPMI commands to read or modify the target identifier in the option information. Figure 6 This is a process of a method for selecting a configuration file on a startup interface through a controller according to an embodiment of the present application. Figure 2 .like Figure 6As shown, when an operator sends an IPMI command to the BMC under the OS (operating system) to read the value of the Display Configuration tab (i.e., read the target identifier in the Display Configuration tab), the BMC returns the option name based on the currently saved BIOS option information (i.e., the boot option information). For example, if the current Display Configuration tab value is "1" (in numerical form), the returned content is "Basic Information" (in text form) or the corresponding English name. When an operator sends an IPMI command to the BMC under the OS to set the value of the Display Configuration tab (i.e., to select the target identifier), the IPMI command under the OS can be used to set the name corresponding to the option value. For example, if the desired Display Configuration tab value is "1," the setting content is "Basic Information" or the corresponding English name. After receiving the command, the BMC modifies the locally saved BIOS option information based on the name-value correspondence and sends the modified option information to the BIOS in JSON format via the Redfish channel.

[0079] When the operator selects a target identifier through the Display Configuration tab on the system's display interface, the BIOS saves the selected value (i.e., the target identifier) ​​in the corresponding variable after completing the Display Configuration tab selection in the BIOS Setup interface. This variable data is physically stored in the NVRAM (Non-Volatile Random Access Memory) area on the flash memory chip that stores the BIOS code and is protected from power failures. After completing the Display Configuration tab selection in the BIOS Setup interface, an IPMI command is sent to the BMC to notify it of the target identifier change. The next time the server boots, the modified target identifier takes effect. During the boot process, the BIOS reads the value of the variable corresponding to the Display Configuration tab in the NVRAM area and displays the contents of different profiles based on the variable value. If the variable is not modified during the next boot (i.e., not modified in the BIOS Setup interface), but an option modification JSON file (i.e., modification instructions) is received from the BMC, the BIOS parses the JSON file and displays the contents of different profiles based on the target identifier indicated in the JSON file. At the same time, the BIOS will write the value of the modified option card into the corresponding variable for storage.

[0080] Optionally, in an embodiment of the present application, in addition to providing a selection of multiple identifiers to implement the selection of a configuration file for the startup interface, it is also possible but not limited to providing a selection of the file content within the configuration file. That is, the file content within each configuration file can be, but is not limited to, modifiable. Users or operation and maintenance personnel can, but are not limited to, modify the file content of each configuration file on the startup system, or can, but are not limited to, modify the file content of each configuration file on the controller. The controller will modify the locally saved configuration file information, which is used to record the file content of each configuration file. The controller will send the modified configuration file information to the startup system in the format of a file via a communication channel with the startup system.

[0081] Optionally, in this embodiment, in addition to the aforementioned user-selectable fixed configuration file and user-selectable modifiable configuration file, the target configuration file to be displayed during the server startup phase may also be, but is not limited to, automatically generated and automatically updated according to the operation status of the server.

[0082] Optionally, in this embodiment, an intelligent display configuration identifier can be added to the display configuration tab, but is not limited to it. By selecting the intelligent display configuration identifier, the user can realize automatic generation and automatic update of the target configuration file.

[0083] As an optional implementation, the automatic update of the target configuration file can be achieved in the following manner, but is not limited to: before searching for the target configuration file corresponding to the target identifier from the identifiers and configuration files with corresponding relationships, the server controller updates the target configuration file according to the fault condition recorded in the system log of the server during the last operation of the server, wherein the target identifier is used to indicate that the startup system is started in an intelligent display configuration manner.

[0084] Optionally, in this embodiment, the server may be configured to start the system using the smart display configuration by default, but is not limited to the default. If the user does not select any of the tabs in the display configuration tab, the smart display configuration automatically takes effect. The target configuration file to be displayed during the server startup phase is generated and updated by the server controller during the server's last run based on the fault conditions recorded in the server's system log.

[0085] Optionally, in this embodiment, the user may, but is not limited to, select an identifier corresponding to the smart display configuration in the display configuration tab. The target identifier is used to indicate that the system should be started using the smart display configuration. The target configuration file may be updated by the server controller based on a fault condition recorded in the server's system log during a previous server operation, but is not limited to, when the system is started using the smart display configuration.

[0086] Optionally, in this embodiment, the system log may, but is not limited to, also record the fault resolution status. When the target identifier is used to indicate that the startup system is started in an intelligent display configuration manner, the server controller may update the target configuration file according to the fault status and fault resolution status recorded in the server system log during the last operation of the server, but is not limited to.

[0087] Optionally, in this embodiment, the target configuration file is updated by the controller of the server according to the fault condition recorded in the system log of the server during the last operation of the server, which may include but is not limited to: detecting the startup attributes of the server, wherein the startup attributes are used to indicate the number of times the server is started; when it is detected that the startup attributes of the server are used to indicate that the server is started for the first time, the file content of the target configuration file is updated to the basic information of the server, wherein the basic information includes the processor version of the server, the processor generation of the server, the memory capacity of the server, the memory model of the server, the controller firmware version of the server, the firmware version of the startup system of the server, and the network configuration initialization status of the server; when it is detected that the startup attributes of the server are used to indicate that the server is not started for the first time, the target configuration file is updated by the controller according to the fault condition recorded in the system log of the server during the last operation of the server.

[0088] Through the above content, the target configuration file is updated according to the fault conditions recorded in the system log of the server during the last operation of the server, so that the server information displayed during the startup phase is more in line with the operation status of the server, which can better help users understand the operation characteristics of the server more quickly.

[0089] Optionally, in this embodiment, each configuration file may be, but is not limited to, stored in the startup system, and the smart configuration file corresponding to the identifier corresponding to the smart display configuration may be, but is not limited to, also stored in the startup system. During the current operation of the server, the startup system stores a historical smart configuration file. The controller generates an updated smart configuration file based on the fault condition recorded in the server's system log, modifies the historical smart configuration file locally stored by the controller to the updated smart configuration file, and further transmits the updated smart configuration file to the startup system via a communication channel with the startup system. Upon receiving the updated smart configuration file, the startup system replaces the historical smart configuration file corresponding to the identifier corresponding to the smart display configuration with the updated smart configuration file.

[0090] Optionally, in this embodiment, the controller may, but is not limited to, only update the controller's local smart configuration file. The startup system accesses the controller's local storage space at each startup. After obtaining the updated smart configuration file from the controller's local storage space, the startup system updates the smart configuration file corresponding to the identifier corresponding to the smart display configuration stored in the startup system. Alternatively, the controller may record the storage address of the startup system's smart configuration file. After updating the local smart configuration file, the controller may write the updated smart configuration file to the storage address of the startup system's smart configuration file.

[0091] As an optional implementation, the target configuration file is updated according to the fault conditions recorded in the system log of the server, including: detecting the log level of the collected system log; adjusting the fault weight of the fault subject corresponding to the system log according to the log level, wherein the fault weight is used to indicate the fault degree of the fault subject; adding the fault information of the target fault subject whose fault weight is greater than or equal to the first threshold to the target configuration file, and deleting the fault information of the reference fault subject whose fault weight is less than the second threshold from the target configuration file.

[0092] Optionally, in this embodiment, the log level may be, but is not limited to, a fault level used to indicate a fault object.

[0093] Optionally, in this embodiment, the log level may include, but is not limited to, an information level, a warning level, and a severity level, wherein the information level may be, but is not limited to, used to indicate that there is no fault in the subject in the server involved in the log, the warning level may be, but is not limited to, used to indicate that there is a risk of fault in the subject in the server involved in the log, and the severity level may be, but is not limited to, used to indicate that a serious fault has occurred in the subject in the server involved in the log.

[0094] Optionally, in this embodiment, the fault subject may be, but is not limited to, a hardware device, a software program, or a server structure.

[0095] Optionally, in this embodiment, adjusting the fault weight of the fault subject corresponding to the system log according to the log level may include, but is not limited to: when it is detected that the log level of the collected first system log is the information level, adjusting the fault weight of the first subject corresponding to the first system log to a first value, wherein the first value is less than the second threshold value; when it is detected that the log level of the collected second system log is the warning level or the serious level, adjusting the fault weight of the fault subject according to the subject type and log level of the fault subject, wherein the subject type includes hardware type and non-hardware type.

[0096] Optionally, in this embodiment, when the fault weights of the fault subjects corresponding to all system logs in the server are all the first value, but not limited to, the file content of the target configuration file can be updated to the basic information of the server, wherein the basic information includes the hardware configuration of the server, the controller version of the server and the network status of the server.

[0097] Optionally, in this embodiment, adjusting the fault weight of the fault subject according to the subject type and log level of the fault subject may include, but is not limited to: when the subject type of the fault subject is a non-hardware type, adjusting the fault weight of the fault subject according to the fault recovery capability of the startup system for the fault subject; when the subject type of the fault subject is a hardware type, detecting duplicate information of the fault corresponding to the second system log, wherein the duplicate information is used to indicate whether the fault corresponding to the second system log is a new fault; when the duplicate information is used to indicate that the fault corresponding to the second system log is a new fault, adjusting the fault weight of the fault subject corresponding to the second system log according to the log level of the second system log; when the duplicate information is used to indicate that the fault corresponding to the second system log is not a new fault, not adjusting the fault weight of the fault subject corresponding to the second system log.

[0098] Optionally, in this embodiment, adjusting the fault weight of the fault subject according to the fault recovery capability of the starting system for the fault subject may include, but is not limited to: when the starting system does not have the capability to recover the fault of the fault subject, adjusting the fault weight of the fault subject to a second value, wherein the second value is greater than or equal to the first threshold value; when the starting system has the capability to recover the fault of the fault subject, not adjusting the fault weight of the fault subject.

[0099] Optionally, in this embodiment, when the fault weight is the second value, the reference alarm may be added to the target configuration file, but is not limited to the case.

[0100] Optionally, in this embodiment, adjusting the fault weight of the fault subject corresponding to the second system log according to the log level of the second system log may include, but is not limited to: when the log level of the second system log is a warning level, adjusting the fault weight of the fault subject from the initial fault weight to the sum of the initial fault weight and the weight adjustment increment; when the log level of the second system log is a serious level, adjusting the fault weight of the fault subject to the maximum value of the fault weight, wherein the maximum value is greater than the first threshold.

[0101] Optionally, in this embodiment, adding the fault information of the target fault subject whose fault weight is greater than or equal to the first threshold to the target configuration file may include, but is not limited to: adding all the fault information of the target fault subject whose fault weight is greater than or equal to the third threshold to the target configuration file, and adding part of the fault information of the target fault subject whose fault weight is less than the third threshold and greater than or equal to the first threshold to the target configuration file, wherein the third threshold is greater than the first threshold.

[0102] Optional, Figure 7 FIG is a schematic diagram of a fault weight adjustment method according to an embodiment of the present application. Figure 7 As shown, the BMC controls the content displayed on the startup page during the BIOS boot process based on the log severity level (i.e., log level) in real time. Each time a log entry is generated, the BMC determines the severity level of the log. If the log entry is only at the "Info" level (i.e., information level), it represents basic server information and skips further analysis. If the log entry is at the "Warning" or "Critical" level, the BMC analyzes the log content to determine whether it includes information about system hardware (such as fans, CPUs, PSUs, add-in cards, memory, disks, mainboards, PCIe devices, BMCs, integrated south bridges, cables, and graphics cards). The BMC then records the hardware device that generated the alarm and the corresponding fault status (such as overheating, error, speed reduction, bandwidth reduction, or connection loss). Duplicate information is not recorded. The "Warning" and "Critical" levels are assigned different weights (i.e., weight adjustment increments). When a hardware device generates a "Warning" alarm, the weight increases by one. When a device generates a "Critical" alarm, the weight increases by three, capping the weight at three. Repeated alarms (for the same hardware device and the same fault status) do not increase the weight. Different weight values ​​represent the amount of fault information displayed during the BIOS boot process: zero weight displays no fault information, three weights display all fault information, and one and two weights display fewer and more fault information, respectively. The hardware fault type and the corresponding hardware weight (i.e., fault weight) recorded by the BMC (controller) are sent to the BIOS via IPMI when a reboot is triggered (i.e., the next time the server boots). The BIOS receives this information and switches the amount of fault information displayed.

[0103] For other alarms not related to hardware devices, such as "Chassis lid open, intrusion alarm," "Watchdog timeout alarm," "Air inlet overheat," and "Firmware refresh failure," the display content is pre-set based on the specific information. For alarms or faults such as "Chassis lid open, intrusion alarm," "Air inlet overheat," and "Firmware refresh failure" that the BIOS cannot process (i.e., the system cannot recover from the fault after booting), fixed alarm content (i.e., reference alarm) is printed and displayed during the boot process. For alarms or faults such as "Watchdog timeout alarm" that the BIOS can analyze and process, the fault type and corresponding weight are sent to the BIOS via IPMI when a reboot is triggered, and the information is displayed on the BIOS boot interface. It should be noted that the "hardware fault type, corresponding hardware weight" and "fault type and corresponding weight" sent via IPMI are transmitted and parsed using a pre-set encoding method to avoid significantly increasing boot time due to sending overly long strings.

[0104] Optionally, in this embodiment, the BMC may, but is not limited to, log the alarm clear when a fault is resolved. Similarly, when a "Warning" alarm is resolved for a hardware device, the weight is reduced by one. When a "Critical" alarm is resolved for a device, the weight is reduced by three, until the weight reaches zero. The BMC updates fault and weight information in real time, but only sends the latest information to the BIOS via IPMI when a reboot is triggered.

[0105] Optionally, in this embodiment, the BIOS may, but is not limited to, perform the early video graphics array function in the PEI phase (initialization phase) before memory initialization during the startup process, so that the server can display and output within 10 seconds of pressing the power button. During the subsequent startup process, the BIOS will determine the target identifier for each key information that needs to be output to the display screen. The display content will only be output when the identifier configured by the system configuration item is consistent with the target identifier. The display content may include, but is not limited to, a customer-customized logo or server manufacturer logo, shortcut key prompt information (shortcut keys for entering the BIOS Setup function, shortcut keys for selecting startup items, shortcut keys for entering the PXE (Preboot eXecution Environment) startup environment), a progress bar, a startup process stage code, etc. These contents are distributed in the surrounding areas, and the large area in the middle is the server key information display area.

[0106] As an optional implementation, displaying startup progress information on the startup interface includes: displaying percentage information and stage information on the startup interface, wherein the startup progress information includes: percentage information and stage information, the percentage information is used to dynamically display the percentage of the server's startup progress in the total startup progress, and the stage information is used to display the startup stage that the startup progress is currently in among the multiple startup stages of the server.

[0107] Optionally, in this embodiment, the startup progress information displayed on the startup interface may include, but is not limited to, percentage information and stage information. By dual displaying the percentage information and stage information, a clearer progress display can be provided to the user.

[0108] As an optional implementation, the startup progress information is updated according to the operation status of the startup system, including: updating the proportion information of the startup code of the startup system according to the operation progress to match the proportion of the started progress in the total startup progress with the operation progress; and updating the stage information using the stage identifier of the target startup stage corresponding to the operation progress in multiple startup stages.

[0109] Optionally, in this embodiment, each startup stage may have, but is not limited to, a corresponding stage identifier, and the user may be prompted with the current startup stage by displaying the stage identifier.

[0110] As an optional implementation, the multiple startup stages include: a security stage, an initialization stage, a driver execution environment stage, and a boot device selection stage, wherein the stage identifier of the security stage is SEC, the stage identifier of the initialization stage is PEI, the stage identifier of the driver execution environment stage is DXE, and the stage identifier of the boot device selection stage is BDS.

[0111] Optionally, in this embodiment, the security phase is identified as SEC (Security Phase). The SEC phase focuses on initializing server security, including but not limited to setting up a secure environment, verifying the integrity and legitimacy of the boot code, and processing the platform trust chain. This is the first step in the boot process, and its purpose is to ensure that the boot code in subsequent stages has not been tampered with, thereby preventing malware or attackers from gaining control during system startup.

[0112] Optionally, in this embodiment, the initialization phase is identified as PEI (Pre-EFI Initialization Phase), which is the initialization phase before starting the EFI (Extensible Firmware Interface) interface. The PEI phase is responsible for initializing the server's hardware resources, including but not limited to the CPU, memory, and PCIe bus, and provides early video and serial output capabilities. The goal of this phase is to prepare a stable hardware environment for the subsequent DXE phase.

[0113] Optionally, in this embodiment, the Driver Execution Environment (DXE) phase is designated as the Driver Execution Environment (DXE) phase. The DXE phase primarily involves loading and executing drivers, which are responsible for managing specific hardware devices and providing advanced services such as boot disks and network devices. The DXE phase also includes identifying hardware devices, configuring them, and loading appropriate drivers.

[0114] Optionally, in this embodiment, the boot device selection phase is identified as BDS (Boot Device Selection Phase). The BDS phase is responsible for determining the boot sequence and selecting boot devices, such as hard disks, network devices, and USB devices. The BDS phase not only selects the optimal boot device based on the user-set boot sequence but also performs error recovery and boot device redundancy checks.

[0115] Optionally, in this embodiment, verification information for startup protection may be displayed on the startup interface, but is not limited to the display.

[0116] As an optional implementation, the verification information can be displayed in the following manner, but is not limited to: after the startup system of the running server is started, the verification information of the startup protection is displayed on the startup interface; after the stage information shows the stage identification target duration of the boot device selection stage, the verification information is stopped from being displayed.

[0117] Optionally, in this embodiment, the verification information may be, but is not limited to, used to indicate whether the startup protection verification succeeds or fails.

[0118] Optionally, in this embodiment, the startup protection verification information can be displayed on the startup interface only when, but not limited to, the verification information is used to indicate that the startup protection verification has failed, and the startup protection verification information is not displayed on the startup interface when the verification information is used to indicate that the startup protection verification has succeeded.

[0119] As an optional implementation, displaying server information on the startup interface of the startup system and displaying startup progress information on the startup interface includes: displaying server information in the first area of ​​the startup interface; displaying startup progress information in the second area of ​​the startup interface.

[0120] Optionally, in this embodiment, the server information may be displayed in the first area of ​​the startup interface, but is not limited to being displayed first, and then the startup progress information may be displayed in the second area of ​​the startup interface; or the server information may be displayed in the first area of ​​the startup interface while the startup progress information may be displayed in the second area of ​​the startup interface, but is not limited to being displayed.

[0121] Optionally, in this embodiment, Figure 8 This is a schematic diagram of a startup interface according to an embodiment of the present application. Figure 1 .like Figure 8 As shown, the startup interface may include, but is not limited to, a first area and a second area. The server information may be displayed in the first area, but is not limited to, and the startup progress information may be displayed in the second area, but is not limited to.

[0122] Optionally, in this embodiment, on the basis of displaying the server information and the startup progress information on the startup interface, shortcut key information may be displayed on the startup interface, but is not limited to being displayed.

[0123] As an optional implementation, shortcut key information can be displayed in the following manner, but is not limited to: after displaying the startup progress information in the second area of ​​the startup interface, shortcut key information is displayed in the third area of ​​the startup interface, wherein the shortcut key information is used to display system operations that are allowed to be triggered during the server startup process and shortcut keys used to trigger system operations.

[0124] Optionally, in this embodiment, Figure 9 This is a schematic diagram of a startup interface according to an embodiment of the present application. Figure 2 .like Figure 9 As shown, the startup interface may include but is not limited to a first area, a second area, and a third area. The server information may be displayed in the first area, the startup progress information may be displayed in the second area, and the shortcut key information may be displayed in the third area.

[0125] Optionally, in this embodiment, the shortcut key information may be used, but is not limited to, to display system operations that are allowed to be triggered during the server startup process and the shortcut keys used to trigger the system operations. For example, the shortcut key information may include, but is not limited to, pressing the F11 key to enter the startup system settings interface, etc.

[0126] Optionally, in this embodiment, Figure 10 This is a schematic diagram of a startup interface according to an embodiment of the present application. Figure 3 .like Figure 10 As shown, the startup interface may include but is not limited to a first area, a second area, a third area, and a fourth area. The server information may be displayed in the first area, the startup progress information may be displayed in the second area, the shortcut key information may be displayed in the third area, and the aforementioned startup protection verification information may be displayed in the fourth area, but is not limited to.

[0127] Optionally, in this embodiment, Figure 11 This is a schematic diagram of a startup interface according to an embodiment of the present application. Figure 4 .like Figure 11 As shown, the startup interface may include, but is not limited to, a first area, a second area, a third area, a fourth area, and a fifth area. The first area may display, but is not limited to, server information; the second area may display, but is not limited to, startup progress information; the third area may display, but is not limited to, shortcut key information; the fourth area may display, but is not limited to, the aforementioned startup protection verification information; and the fifth area may display, but is not limited to, customized information. The customized information may include, but is not limited to, a customized logo, a server vendor logo, a business description of the client, or a business description of the server vendor. When the server is started, the first area may display, but is not limited to, server information and the fifth area may display customized information. Subsequently, the fourth area may display startup protection verification information and the second area may display startup progress information. Finally, the third area may display shortcut key information.

[0128] As an optional implementation, displaying shortcut key information in the third area of ​​the startup interface includes: displaying shortcut key information in the third area of ​​the startup interface within a target time period, wherein the target time period is a time interval allowing triggering system operations; and stopping displaying shortcut key information after the target time period.

[0129] Optionally, in this embodiment, system operations may be, but are not limited to, executable not during the entire server startup process, but rather within a target time period during the startup process. By displaying the shortcut key information only within the target time period and stopping displaying the shortcut key information after the target time period, that is, displaying the shortcut key information only during the time period when the system operation can be executed and not displaying the shortcut key information during the time period when the system operation cannot be executed, the user experience is improved by avoiding the situation where the user cannot execute the system operation after referring to the shortcut key information and pressing the shortcut key.

[0130] Optionally, in this embodiment, each system operation may, but is not limited to, not be executable within the target time period. Each system operation may, but is not limited to, have a corresponding executable time interval within the target time period. That is, each system operation may, but is not limited to, have a corresponding time interval that allows triggering of the system operation. Each time interval within the target time period may, but is not limited to, display the system operations that are allowed to be triggered within that time interval.

[0131] As an optional implementation, after the shortcut key information is displayed in the third area of ​​the startup interface, the shortcut key information can be refreshed as trigger information, but is not limited to, when it is detected that the target shortcut key is triggered, wherein the trigger information is used to show that the target shortcut key has been triggered and the server will execute the target system operation corresponding to the target shortcut key. After the trigger information is displayed, the server is set not to respond to the triggering of other shortcut keys.

[0132] Optionally, in this embodiment, Figure 12 This is a schematic diagram of a startup interface according to an embodiment of the present application. Figure 5 .like Figure 12 As shown, the shortcut key information in the third area can be refreshed as trigger information when the target shortcut key is triggered, but is not limited to this. On the one hand, the trigger information is used to inform the user that the target shortcut key has been triggered and the target system operation corresponding to the target shortcut key that the server will execute, thereby improving the user experience. On the other hand, after the trigger information is displayed, the server is configured not to respond to the triggering of other shortcut keys, avoiding operational conflicts between multiple system operations and ensuring that the target system operation can be accurately executed.

[0133] As an optional embodiment, displaying server information in the first area of ​​the startup interface includes: displaying server information line by line in the first area of ​​the startup interface; when the number of rows of server information is greater than the number of rows in the first area, displaying the latest content that meets the number of rows in the first area in the first area and displaying first prompt information in the first area, wherein the first prompt information is used to indicate that the first area allows page turning to display.

[0134] Optionally, in this embodiment, the server information may be displayed in the first area in a row-by-row manner, but is not limited to being displayed. If the number of rows of server information exceeds the number of rows in the first area, that is, if there is too much server information to be displayed simultaneously on the display device, the most recent content that fits within the number of rows in the first area may be displayed in the first area, and a first prompt indicating that the first area allows page flipping may be displayed in the first area.

[0135] Optionally, in this embodiment, the first prompt information may be, but is not limited to, a text description, such as "Press the U key to turn the page." The first prompt information may also be, but is not limited to, an icon. Figure 13 This is a schematic diagram of a startup interface according to an embodiment of the present application. Figure 6 .like Figure 13 As shown, the first prompt information may be displayed in the first area, but is not limited to, when the number of rows of the server information is greater than the number of rows of the first area.

[0136] Optionally, in this embodiment, when the BIOS (i.e., the boot system) outputs display content during the boot process, two function commands are used to print the display content to the display screen: a general type and a custom type. The custom type print function command specifies the x and y coordinates and the print string as function input parameters and outputs the content. The general type print function, on the other hand, uniformly calls a basic print function, which only specifies the print string as the function input parameter. In the basic print function, appropriate coordinates are automatically calculated based on the current screen resolution, the specified font size, and other information. Printing is performed sequentially from left to right and from top to bottom. Each print will directly display the entire string passed in by the function call. If the string passed in as a parameter contains a line break character '\n', a line break operation will be automatically performed. The line break is to switch coordinates and continue to display the content. It's also important to emphasize that during startup, the basic print function saves the content and coordinate data for each print in a dynamic memory area in the form of a structure. During printing, the appropriate coordinate information required for the current print is calculated based on this saved data (i.e., the x and y coordinates of the current printed line are calculated based on the number of displayed lines and the screen resolution). Optionally, when the printed information exceeds the maximum range supported by the current screen resolution, a scrolling operation is required. This first clears the screen content, then subtracts one line from all y coordinates in the printed content information data structure (it should be noted that if the y coordinate is less than the y coordinate of the first line at this resolution, the string is not printed). The content information data structure is then printed and displayed, and finally the newly added string is printed. It should be noted that after a scrolling operation is performed, a global variable is set from the default value of 0 to 1, indicating that scrolling has occurred. When the BIOS displays content during the boot process and encounters scrolling, a page-up shortcut key (the first prompt) is provided during the BDS phase (late boot phase) of the BIOS boot process. At this stage, the boot process information has essentially been output. Because the BIOS executes code in a single thread and cannot continuously respond to dynamic key presses, after the printing of key information has essentially been completed in the late boot phase, if it cannot be fully displayed at the current resolution, indicating scrolling, a page-up shortcut key is provided. Specifically, during the late BDS phase, the scrolling behavior global variable is determined. If the value is 1, a prompt box containing the text "Page Up" (the first prompt) is printed at the right edge of the display. When the PageUp key is pressed on the keyboard or remote console, the corresponding shortcut key action is performed.The shortcut key action is to first clear all the contents on the screen, then increase all the y coordinates in the printed content information data structure by k lines, where k is equal to the number of times the scrolling operation is performed (it should be noted that when the y coordinate is greater than the y coordinate of the last line at the resolution, this string will not be printed), and then print and display it according to the printed content information data structure. At the same time, the cleared shortcut key-related content (i.e., the first prompt information) will no longer be displayed. It should be noted that when the startup display strategy of this application is adopted, generally speaking, there will not be content that exceeds twice the number of lines that the display resolution can display. Therefore, the page-up shortcut key will only respond once, which will not have a significant impact on the boot time.

[0137] As an optional embodiment, after the prompt information is displayed in the first area, it is possible, but not limited to, when it is detected that the page-up operation is triggered, to obtain target information that matches the trigger information and the number of rows in the first area from the server information according to the trigger information of the page-up operation; display the target information in the first area and display the second prompt information in the first area, wherein the second prompt information is used to indicate that the first area allows page-down display.

[0138] Optionally, in this embodiment, the second prompt information may be, but is not limited to, a text description, such as "Press the D key to scroll down the page", and the second prompt information may also be, but is not limited to, an icon. Figure 14 This is a schematic diagram of a startup interface according to an embodiment of the present application. Figure 7 .like Figure 14 As shown, the second prompt information can be displayed in the first area, but is not limited to, when it is detected that the page-up operation is triggered and the information displayed in the first area is changed to the target information that meets the trigger information and the number of rows in the first area.

[0139] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method.

[0140] The embodiment of the present application also provides a server startup display device, Figure 15 This is a structural block diagram of a server startup display device according to an embodiment of the present application. Figure 15 As shown, the device includes:

[0141] The running module 1502 is used to run the server startup system when the server is started;

[0142] The first display module 1504 is used to display server information on the startup interface of the startup system and to display startup progress information on the startup interface, wherein the server information is used to display the configuration of the server and the startup progress information is used to display the startup progress of the server;

[0143] The updating module 1506 is configured to update the startup progress information according to the operation status of the startup system.

[0144] By means of the above device, when the server is started, the server startup system is run, server information for displaying the configuration status of the server is displayed on the startup interface of the startup system, and startup progress information for displaying the startup progress of the server is displayed on the startup interface. The startup progress information is updated according to the operation status of the startup system. The user can also obtain the configuration status of the server and the startup progress of the server during the startup process of the server, thereby improving the transparency of the startup process of the server. Therefore, the technical problem of poor transparency of the startup process of the server in the related art can be solved, thereby achieving the technical effect of improving the transparency of the startup process of the server and thus improving the user experience.

[0145] Optionally, the first display module includes: a first display unit, configured to display the target configuration item as server information on the startup interface, wherein the system configuration items of the startup system include the target configuration item.

[0146] Optionally, the target configuration item includes at least one of the following: first version information, generation information, memory information, second version information, third version information, fourth version information, and address information. The first version information is used to indicate the processor version of the server, the generation information is used to indicate the processor generation of the server, the memory information is used to indicate the memory capacity of the server, the second version information is used to indicate the version number of the startup system, the third version information is used to indicate the version release time of the startup system, the fourth version information is used to indicate the controller version of the server, and the address information is used to indicate the controller address of the server.

[0147] Optionally, the first display unit is further used to: read the target identifier configured by the target configuration item from the system configuration item; search for the target configuration file corresponding to the target identifier from the identifiers and configuration files with corresponding relationships; and display the file content of the target configuration file as server information on the startup interface.

[0148] Optionally, the first display unit is also used to: before reading the target identifier configured by the target configuration item from the system configuration item, display a display configuration tab in the configuration tab of the startup system, wherein the display configuration tab is used to select the identifier of the configuration file to be displayed in the server startup phase from multiple identifiers; and determine the identifier among the multiple identifiers that is triggered by the selection operation as the target identifier.

[0149] Optionally, the first display unit is further configured to: display a display configuration tab in a configuration tab of a startup system on a controller of the server;

[0150] Optionally, the first display unit is also used for: the controller saving the target identifier to the option information of the startup system on the controller; the controller sending a modification instruction to the startup system through the transmission channel between the controller and the startup system, wherein the modification instruction is used to instruct to modify the identifier configured by the target configuration item to the target identifier; and the startup system executing the modification instruction.

[0151] Optionally, the first display unit is also used to: before searching for the target configuration file corresponding to the target identifier from the identifiers and configuration files with corresponding relationships, the server controller updates the target configuration file according to the fault condition recorded in the system log of the server during the last operation of the server, wherein the target identifier is used to indicate that the startup system is started in an intelligent display configuration manner.

[0152] Optionally, the first display unit is also used to: detect the log level of the collected system log; adjust the fault weight of the fault subject corresponding to the system log according to the log level, wherein the fault weight is used to indicate the fault degree of the fault subject; add the fault information of the target fault subject whose fault weight is greater than or equal to the first threshold to the target configuration file, and delete the fault information of the reference fault subject whose fault weight is less than the second threshold from the target configuration file.

[0153] Optionally, the first display module also includes: a second display unit, used to display proportion information and stage information on the startup interface, wherein the startup progress information includes: proportion information and stage information, the proportion information is used to dynamically display the proportion of the server's startup progress in the total startup progress, and the stage information is used to display the startup stage that the started progress is currently in among the multiple startup stages of the server.

[0154] Optionally, the update module includes: a first update unit, used to update the proportion information of the started progress in the total startup progress according to the running progress of the startup code of the startup system to match the running progress; a second update unit, used to update the stage information using the stage identifier of the target startup stage corresponding to the running progress in multiple startup stages.

[0155] Optionally, the multiple startup stages include: a security stage, an initialization stage, a driver execution environment stage, and a boot device selection stage, wherein the stage identifier of the security stage is SEC, the stage identifier of the initialization stage is PEI, the stage identifier of the driver execution environment stage is DXE, and the stage identifier of the boot device selection stage is BDS.

[0156] Optionally, the startup display device also includes: a second display module for displaying the verification information of the startup protection on the startup interface; and a stop module for stopping displaying the verification information after the stage information displays the stage identification target duration of the boot device selection stage.

[0157] Optionally, the first display module further includes: a third display unit, used to display server information in the first area of ​​the startup interface; and a fourth display unit, used to display startup progress information in the second area of ​​the startup interface.

[0158] Optionally, the first display module also includes: a fifth display unit, used to display shortcut key information in the third area of ​​the startup interface, wherein the shortcut key information is used to display system operations allowed to be triggered during the server startup process and shortcut keys used to trigger system operations.

[0159] Optionally, the fifth display unit is further used to: display shortcut key information in the third area of ​​the startup interface within a target time period, wherein the target time period is a time interval that allows triggering system operations; and stop displaying shortcut key information after the target time period.

[0160] Optionally, the fifth display unit is also used to: after displaying the shortcut key information in the third area of ​​the startup interface, when it is detected that the target shortcut key is triggered, refresh the shortcut key information to trigger information, wherein the trigger information is used to show that the target shortcut key has been triggered and the server will execute the target system operation corresponding to the target shortcut key. After the trigger information is displayed, the server is set not to respond to the triggering of other shortcut keys.

[0161] Optionally, the third display unit is also used to: display server information line by line in the first area of ​​the startup interface; when the number of rows of server information is greater than the number of rows in the first area, display the latest content that meets the number of rows in the first area in the first area and display a first prompt message in the first area, wherein the first prompt message is used to indicate that the first area allows page turning to display.

[0162] Optionally, the third display unit is also used to: after displaying the prompt information in the first area, when it is detected that the page-up operation is triggered, obtain target information that matches the trigger information and the number of rows in the first area from the server information according to the trigger information of the page-up operation; display the target information in the first area and display the second prompt information in the first area, wherein the second prompt information is used to indicate that the first area allows page-down display.

[0163] For the description of the features in the embodiment corresponding to the server startup display device, please refer to the relevant description of the embodiment corresponding to the server startup display method, which will not be repeated here.

[0164] An embodiment of the present application further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any of the above-mentioned server startup display method embodiments.

[0165] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any of the above-mentioned server startup display method embodiments when running.

[0166] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0167] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in any of the above-mentioned server startup display method embodiments are implemented.

[0168] An embodiment of the present application further provides another computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of any of the above-mentioned server startup display method embodiments are implemented.

[0169] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0170] The above is a detailed introduction to the server startup display method and device provided by this application. This article uses specific examples to illustrate the principles and implementation methods of this application. The description of the above embodiments is only used to help understand the method and core ideas of this application. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of this application, several improvements and modifications can be made to this application, and these improvements and modifications also fall within the scope of protection of the claims of this application.

Claims

1. A method for starting and displaying a server, characterized in that: include: When the server is started, running the startup system of the server; Displaying server information on a startup interface of the startup system and displaying startup progress information on the startup interface, wherein the server information is used to display the configuration status of the server and the startup progress information is used to display the startup progress of the server; updating the startup progress information according to the operation status of the startup system; The displaying of the server information on the startup interface of the startup system includes: reading a target identifier configured by a target configuration item from a system configuration item of the startup system, wherein the system configuration item includes the target configuration item; searching for a target configuration file corresponding to the target identifier from identifiers and configuration files having a corresponding relationship; and displaying the file content of the target configuration file as the server information on the startup interface. Before reading the target identifier configured for the target configuration item from the system configuration item, the method further includes: displaying a display configuration tab in the configuration tab of the startup system on the controller of the server, wherein the display configuration tab is used to select an identifier of a configuration file to be displayed during the startup phase of the server from a plurality of identifiers; saving the target identifier to the option information of the startup system on the controller by the controller; sending a modification instruction to the startup system by the controller via a transmission channel between the controller and the startup system, wherein the modification instruction is used to instruct to modify the identifier configured for the target configuration item to the target identifier; and executing the modification instruction by the startup system.

2. The server startup display method according to claim 1, characterized in that: The target configuration item includes at least one of the following: first version information, generation information, memory information, second version information, third version information, fourth version information, and address information. The first version information is used to indicate the processor version of the server, the generation information is used to indicate the processor generation of the server, the memory information is used to indicate the memory capacity of the server, the second version information is used to indicate the version number of the startup system, the third version information is used to indicate the version release time of the startup system, the fourth version information is used to indicate the controller version of the server, and the address information is used to indicate the controller address of the server.

3. The server startup display method according to claim 1, characterized in that: Before searching for the target configuration file corresponding to the target identifier from the identifiers and configuration files having a corresponding relationship, the method further includes: The controller of the server updates the target configuration file according to the fault condition recorded in the system log of the server during the last operation of the server, wherein the target identifier is used to instruct the startup system to start in a smart display configuration manner.

4. The server startup display method according to claim 3, characterized in that: The updating of the target configuration file according to the fault condition recorded in the system log of the server includes: Check the log level of the collected system logs; Adjusting the fault weight of the fault subject corresponding to the system log according to the log level, wherein the fault weight is used to indicate the fault degree of the fault subject; The fault information of the target fault subject whose fault weight is greater than or equal to a first threshold is added to the target configuration file, and the fault information of the reference fault subject whose fault weight is less than a second threshold is deleted from the target configuration file.

5. The server startup display method according to claim 1, characterized in that: The displaying of startup progress information on the startup interface includes: The proportion information and stage information are displayed on the startup interface, wherein the startup progress information includes: the proportion information and the stage information, the proportion information is used to dynamically display the proportion of the server's startup progress in the total startup progress, and the stage information is used to display the startup stage that the startup progress is currently in among the multiple startup stages of the server.

6. The server startup display method according to claim 5, characterized in that: The updating of the startup progress information according to the operation status of the startup system includes: According to the running progress of the startup code of the startup system, the proportion of the started progress in the total startup progress in the proportion information is updated to match the running progress; The stage information is updated using the stage identifier of the target startup stage corresponding to the running progress in the multiple startup stages.

7. The server startup display method according to claim 6, characterized in that: The multiple startup stages include: a security stage, an initialization stage, a driver execution environment stage and a boot device selection stage, wherein the stage identifier of the security stage is SEC, the stage identifier of the initialization stage is PEI, the stage identifier of the driver execution environment stage is DXE, and the stage identifier of the boot device selection stage is BDS.

8. The server startup display method according to claim 7, characterized in that: After the starting system of the server is run, the method further comprises: Displaying verification information of startup protection on the startup interface; After the stage information displays the target duration of the stage identification of the guiding device selection stage, the verification information stops being displayed.

9. The server startup display method according to claim 1, characterized in that: The displaying of server information on the startup interface of the startup system and displaying startup progress information on the startup interface includes: Displaying the server information in the first area of ​​the startup interface; The startup progress information is displayed in the second area of ​​the startup interface.

10. The server startup display method according to claim 9, characterized in that: After displaying the startup progress information in the second area of ​​the startup interface, the method further includes: Shortcut key information is displayed in a third area of ​​the startup interface, wherein the shortcut key information is used to display system operations that are allowed to be triggered during the server startup process and shortcut keys used to trigger the system operations.

11. The server startup display method according to claim 10, characterized in that: The displaying of shortcut key information in the third area of ​​the startup interface includes: Displaying the shortcut key information in the third area of ​​the startup interface within a target time period, wherein the target time period is a time interval that allows triggering the system operation; The shortcut key information is stopped from being displayed after the target time period.

12. The server startup display method according to claim 11, characterized in that: After displaying the shortcut key information in the third area of ​​the startup interface, the method further includes: When it is detected that the target shortcut key is triggered, the shortcut key information is refreshed as trigger information, wherein the trigger information is used to show that the target shortcut key has been triggered and the server will execute the target system operation corresponding to the target shortcut key. After the trigger information is displayed, the server is set to not respond to the triggering of other shortcut keys.

13. The server startup display method according to claim 9, characterized in that: The displaying of the server information in the first area of ​​the startup interface includes: Displaying the server information line by line in the first area of ​​the startup interface; When the number of rows of the server information is greater than the number of rows of the first area, the latest content that meets the number of rows of the first area is displayed in the first area and a first prompt message is displayed in the first area, wherein the first prompt message is used to indicate that the first area allows page turning to be displayed upward.

14. The server startup display method according to claim 13, characterized in that: After displaying the prompt information in the first area, the method further includes: When it is detected that a page-up operation is triggered, acquiring target information that matches the trigger information and the number of rows in the first region from the server information according to the trigger information of the page-up operation; The target information is displayed in the first area and second prompt information is displayed in the first area, wherein the second prompt information is used to indicate that the first area allows page turning to display downward.

15. A server startup display device, characterized in that: include: A running module, configured to run a startup system of the server when the server is started; a first display module, configured to display server information on a startup interface of the startup system and to display startup progress information on the startup interface, wherein the server information is used to display the configuration of the server, and the startup progress information is used to display the startup progress of the server; An updating module, configured to update the startup progress information according to the operation status of the startup system; The first display module includes: a first display unit configured to: read a target identifier configured by a target configuration item from a system configuration item of the startup system, wherein the system configuration item includes the target configuration item; search for a target configuration file corresponding to the target identifier from identifiers and configuration files having a corresponding relationship; and display the file content of the target configuration file on the startup interface as the server information; The first display unit is further used to: before reading the target identifier configured by the target configuration item from the system configuration item, display a display configuration tab in the configuration tab of the startup system on the controller of the server, wherein the display configuration tab is used to select the identifier of the configuration file to be displayed in the startup phase of the server from multiple identifiers; the controller saves the target identifier to the option information of the startup system on the controller; the controller sends a modification instruction to the startup system through a transmission channel between the controller and the startup system, wherein the modification instruction is used to instruct to modify the identifier configured by the target configuration item to the target identifier; and the startup system executes the modification instruction.

16. An electronic device, characterized in that: include: memory for storing computer programs; A processor, configured to implement the steps of the server startup display method according to any one of claims 1 to 14 when executing the computer program.

17. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the steps of the method for starting and displaying a server according to any one of claims 1 to 14 are implemented.

18. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the server startup display method according to any one of claims 1 to 14 are implemented.

Images