CN112068889A

CN112068889A - Network starting realization of Loongson host

Info

Publication number: CN112068889A
Application number: CN202010760789.6A
Authority: CN
Inventors: 张辰; 吴少刚; 石丹; 潘志凌; 尹怡哲; 徐超辉
Original assignee: Jiangsu Lemote Information Technology Co ltd
Current assignee: Jiangsu Lemote Information Technology Co ltd
Priority date: 2020-07-31
Filing date: 2020-07-31
Publication date: 2020-12-11

Abstract

The invention discloses a network startup realization of a Loongson host, which comprises the following specific steps: s1, starting the firmware to request to obtain the IP address; s2, acquiring an installation system version from the EC; s3, loading a Grub file from the server; s4, selecting a needed inner core; s5, loading a kernel and a file system from the server; and S6, starting the Loongson host. The invention does not need a USB flash disk and an optical drive, acquires the kernel and the file system through the network, realizes diskless startup, realizes batch installation of the operating system by means of network startup, and saves labor cost.

Description

Network starting realization of Loongson host

Technical Field

The invention relates to the field of computer network starting, in particular to a network starting implementation of a Loongson host.

Background

Network booting refers to allowing a client to load a boot image from a remote server over a network and thereby support booting an operating system over the network. The diskless starting can be realized through a network starting mode, the automatic installation of the system is also realized, compared with the traditional manual installation, the whole installation process does not need manual intervention, and the working efficiency and the accuracy are greatly improved.

At present, the Loongson platform is mainly used for system installation in a USB flash disk and CD-ROM mode. If a large number of loongson machines need to install the operating system, the efficiency of the method using the usb disk and the optical disk drive is extremely low, and because the installation setting items of the system need to be configured manually, it is not guaranteed that the system installation configuration of each machine is completely consistent.

Disclosure of Invention

The invention aims to provide a network start realization method of a Loongson host, which can effectively solve the problems.

In order to achieve the above object, the present invention provides a network boot implementation of a Loongson host, which comprises the following specific steps:

s1, starting the firmware to request to obtain the IP address;

s2, acquiring a system version from the EC;

s3, loading a Grub file from the server;

s4, selecting a needed inner core;

s5, loading a kernel and a file system from the server;

and S6, starting the Loongson host.

Further, step S1 is preceded by a server environment building step, which includes the following steps:

SA1, server installation DHCP service and TFTP service;

SA2, a specified tftp root directory and a network boot file;

SA3, configuring directory structure, and setting cfg file and efi file in the same level directory.

Furthermore, the firmware is UEFI-based firmware, supports PXE network starting, and requests to acquire IP through a PXE protocol.

Further, the EC is a single chip microcomputer and interacts with firmware through an i2c bus.

Further, the common Grub file includes core.

Further, the system version has a corresponding dedicated Grub file, which is numbered for different system versions, corresponding to the dedicated. efi file path.

Further, step S3 is preceded by the following steps:

SB1, judging whether a system version is acquired;

SB2, if the system version is returned to the corresponding serial number, determining the configuration path of the efi file according to the serial number, and entering the step S3;

SB3, if not, directly proceeds to step S3 using the default configuration path of the common file core.

Further, the loading of the Grub file includes loading and executing the efi file, loading the cfg file under the same-level directory and providing a visualized Grub menu.

Further, the Grub menu has only one kernel option when the executed. efi file is a private file.

Further, the Grub menu provides various kernel launch options, configured via the grub.cfg file, when executing the default core.efi universal file.

Further, when the required kernel is selected, the kernel is selected through an input device of the Loongson host.

Further, if the required kernel is not selected, the default kernel and the file system are loaded.

Furthermore, the kernel and the file system are customized operating systems and can be directly used after being loaded.

Furthermore, the customized operating system is replaced by an installation program of the operating system, and the system can be installed after the installation program is loaded.

The technical scheme provided by the invention has the advantages that: a kernel and a file system are acquired through a network without a USB flash disk and an optical drive, and diskless starting is realized; the large-scale Loongson host machines are networked to realize batch starting; and the batch installation of the operating system of the Loongson host is realized by the diskless startup.

Drawings

Fig. 1 shows a network startup flow diagram of an implementation of the present invention.

Detailed Description

The following detailed description of the preferred embodiments of the present invention, taken in conjunction with the accompanying drawings, will make the advantages and features of the invention easier to understand by those skilled in the art, and thus will clearly and clearly define the scope of the invention.

In a preferred embodiment of the invention, the server environment is built as follows:

s1, the server installs DHCP service and TFTP service;

s2, designating a tftp root directory and a network starting file;

s3, configuring a directory structure, and placing the cfg files and the efi files in the same level directory.

The general Grub file is configured with two options:

firstly, BOOTMIPS.efi and grub.cfg are selected, and the placement path is tftp root directory/EFI/BOOT/BOOTMIPS.efi and tftp root directory/EFI/BOOT/grub.cfg;

and secondly, selecting core.efi and grub.cfg, and placing paths of tftp root directory/core.efi and tftp root directory/grub.cfg.

Cfg files are used to configure different cores, and default cores can be set.

Referring to fig. 1, in the preferred embodiment of the present invention, the process of network boot of the Loongson host is as follows:

s1, checking the server configuration, and running DHCP service and TFTP service;

s2, starting firmware, selecting network to start;

s3, sending a request to acquire an IP address;

s4, judging whether the IP address is acquired, if so, entering the step S5, and if not, returning to the step S1;

s5, acquiring a system version from the EC;

s6, judging whether a system version is acquired, if so, loading a special Grub file from a server, and entering the step S7, otherwise, entering the step S8;

s7, judging whether the special file is loaded, if yes, entering the step S9, and if no, entering the step S8;

s8, loading the general Grub file from the server;

s9, judging whether the Grub menu is executed, if yes, entering the step S10, and if no, returning to the step S1;

s10, selecting a starting kernel;

s11, judging whether the kernel and the file system (initrd) are loaded, if so, entering the step S12, and if not, returning to the step S1;

and S12, waiting for the kernel to run, and entering the system.

The firmware is UEFI-based firmware, supports PXE network starting, automatically executes the PXE network starting when no USB flash disk or optical drive exists, and requests to acquire an IP (Internet protocol) through a PXE protocol.

And the EC is a single chip microcomputer, is positioned on the same mainboard with the UEFI firmware, and interacts with the firmware through an i2c bus.

The system versions are provided with corresponding special Grub files comprising special efi and cfg files, numbers are set for different system versions and correspond to a special efi file configuration path, and the special Grub files are placed in a designated directory in the server building process and are used when different systems are required to be installed on different types or batches of mainboards.

Wherein loading the Grub file includes loading and executing the efi file, loading the cfg file under the same level directory and providing a visual Grub menu.

In the preferred embodiment of the present invention, the commonly used kernels are uos, labeled as kylin, Fedora, longnix, including but not limited to, these four commonly used kernels are configured in Grub. cfg file of general Grub, and the default choice is uos kernels.

In the preferred embodiment of the present invention, a batch of 100 loongson hosts need to be booted without a disk, a kernel uos is selected, and the EC does not specify a system version, and the specific flow is as follows:

s1, accessing 100 Loongson hosts into the network where the server is located;

s2, starting a host, and executing PXE network starting by firmware;

s3, directly loading the general Grub file without acquiring the system version, and executing a Grub menu;

s4, executing a default uos kernel;

and S5, starting the Loongson host.

Specifically, the default kernel in batch diskless startup is changed by modifying the order of the kernels in the grub.

In the preferred embodiment of the present invention, there are 100 loongson hosts that need to be started without disks in batch, wherein 50 hosts designate the kylin as the winning kernel, and the specific flow is as follows:

s1, configuring Grub files, core _ lm _ NeoKylin.efi and Grub _ lm _ NeoKylin.cfg of the winning kylin at the server side, wherein the path is tftp root directory/core _ lm _ NeoKylin.efi and tftp root directory/Grub _ lm _ NeoKylin.cfg;

s2, accessing 100 Loongson hosts into the network where the server is located;

s3, starting a host, and executing PXE network starting by firmware;

s4, 50 stations acquire system versions and load special Grub files, and 50 stations directly load general Grub files without acquiring system versions;

s4, executing a Grub menu, wherein 50 kernels are defaulted to win kylin and 50 kernels are defaulted to uos;

and S5, starting the Loongson host.

Specifically, a specific operating system pointed by the Grub menu is configured in the cfg file, and in the above diskless startup embodiment, the started operating system is a customized operating system, and the operating system can be directly used after loading.

In the preferred embodiment of the present invention, a conference system has 20 loongson hosts, a kernel system started by a diskless is Fedora, and system upgrade is needed at present, and the specific flow is as follows:

s1, updating the upgraded Fedora system to a server to replace the original Fedora system;

s2, loading the data to the host in batch in a diskless starting mode;

specifically, the operating system can be installed in batch on the Loongson host by means of diskless startup, the customized operating system is replaced by a corresponding installation program by modifying the cfg file, and the host enters the system installation after the cfg file is loaded.

The network startup realization of the Loongson host machine has the advantages that a USB (Universal Serial bus) disk and an optical drive are not needed, the kernel and the file system are acquired through the network, the diskless startup is realized, the effects on the schemes of a conference system and the like can be greatly embodied, the operation system is installed in batches through the network startup, the installation and the configuration are not needed one by one, the labor cost can be greatly saved, and the system with uniform configuration can be installed.

The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes performed by the present specification and drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims

1. The network starting realization of the Loongson host is characterized by comprising the following specific steps:

s1, starting the firmware to request to obtain the IP address;

s2, acquiring a system version from the EC;

s3, loading a Grub file from the server;

s4, selecting a needed inner core;

s5, loading a kernel and a file system from the server;

and S6, starting the Loongson host.

2. The network boot implementation of the Loongson host computer according to claim 1, wherein step S1 is preceded by server environment building, and the steps are as follows:

SA1, server installation DHCP service and TFTP service;

SA2, a specified tftp root directory and a network start configuration file;

SA3, configuring directory structure, and setting Grub file in the same level directory.

3. The network boot implementation of the Loongson host as claimed in claim 1, wherein the firmware is UEFI-based firmware, supports PXE network boot, and requests to obtain IP via PXE protocol.

4. The network boot implementation of a Loongson host as claimed in claim 1, wherein the EC is a single chip microcomputer, and interacts with firmware through i2c bus.

5. The network boot implementation of the Loongson host as claimed in claim 2, wherein the Grub files are divided into generic Grub files and specific Grub files, the generic Grub files corresponding to multiple kernel choices, and the specific Grub files corresponding to system versions.

6. The network boot implementation of the Loongson host as claimed in claim 5, wherein the step S3 further comprises the following steps:

SB1, judging whether a system version is acquired;

SB2, if yes, determining the path of the special Grub file according to the system version, and entering the step S3;

SB3, if not, the default path of the general Grub file is used, and the process proceeds to step S3.

7. The network boot implementation of claim 6, wherein the Grub files comprise a. efi file and a.cfg file, and loading the Grub file comprises loading and executing a. efi file, loading the.cfg file under the same level directory and providing a visual Grub menu.

8. The network boot implementation of claim 7, wherein the Grub menu has only one kernel option when the Grub file is a dedicated Grub file.

9. The network boot implementation of claim 7, wherein when the Grub file is a generic Grub file, the Grub menu provides multiple kernel boot options.