Kexec-tools rpm download.Download - kk Blog —— 通用基础
Note that firmware and the boot loader are not used when the system reboots with Kexec. Any changes you make to the boot loader configuration will be ignored until the computer performs a hard reboot.
You can use Kdump to save kernel dumps. If the kernel crashes, it is useful to copy the memory image of the crashed environment to the file system. You can then debug the dump file to find the cause of the kernel crash. Kdump works similarly to Kexec see Chapter 17, Kexec and Kdump.
The capture kernel is executed after the running production kernel crashes. The difference is that Kexec replaces the production kernel with the capture kernel. With Kdump, you still have access to the memory space of the crashed production kernel. You can save the memory snapshot of the crashed kernel in the environment of the Kdump kernel. In environments with limited local storage, you need to set up kernel dumps over the network. Kdump supports configuring the specified network interface and bringing it up via initrd.
This location must be mounted when configuring Kdump, otherwise the configuration will fail. To make sure that Kdump works on your system, its default configuration is sufficient. To use Kdump with the default settings, follow these steps:.
Determine the amount of memory needed for Kdump by following the instructions in Section Make sure to set the kernel parameter crashkernel. Reading the comments will help you understand the meaning of individual options. Execute the init script once with sudo systemctl start kdump , or reboot the system. After configuring Kdump with the default values, check if it works as expected. Make sure that no users are currently logged in and no important services are running on your system.
Then follow these steps:. Switch to the rescue target with systemctl isolate rescue. Without compression, the size of the dump can take up to the size of the physical RAM memory.
The capture kernel boots and the crashed kernel memory snapshot is saved to the file system. Otherwise, the changes will only take effect next time you reboot the system. Using this configuration, Kdump fails to reach the network when trying to write the dump to the FTP server. The general pattern for this looks like the following:. To configure Kdump with YaST, you need to install the yast2-kdump package. In the Start-Up window, select Enable Kdump.
The values for Kdump Memory are automatically generated the first time you open the window. However, that does not mean that they are always sufficient. To set the right values, follow the instructions in Section If you have set up Kdump on a computer and later decide to change the amount of RAM or hard disks available to it, YaST will continue to display and use outdated memory values.
To work around this, determine the necessary memory again, as described in Section Then set it manually in YaST. Click Dump Filtering in the left pane, and check what pages to include in the dump. You do not need to include the following memory content to be able to debug kernel problems:.
In the Dump Target window, select the type of the dump target and the URL where you want to save the dump. It is possible to specify a path for saving Kdump dumps where other applications also save their dumps.
When cleaning its old dump files, Kdump will safely ignore other applications' dump files. Fill the Email Notification window information if you want Kdump to inform you about its events via e-mail and confirm your changes with OK after fine tuning Kdump in the Expert Settings window. Kdump is now configured. Dump files usually contain sensitive data which should be protected from unauthorized disclosure. To allow transmission of such data over an insecure network, Kdump can save dump files to a remote machine using the SSH protocol.
The target host identity must be known to Kdump. This is needed to ensure that sensitive data is never sent to an imposter. Kdump must be able to authenticate to the target machine. Only public key authentication is currently available. By default, Kdump will use root 's private key, but it is advisable to make a separate key for Kdump.
This can be done with ssh-keygen :. Press Enter when prompted for passphrase that is, do not use any passphrase. The target host must enable the sftp subsystem SLE default. Some other distributions use SSH to run some commands on the target host. The Kdump user on the target host must have a login shell that can execute these commands: mkdir , dd and mv. The original tool to analyze the dumps is GDB. You can even use it in the latest environments, although it has several disadvantages and limitations:.
That is why the crash utility was implemented. It analyzes crash dumps and debugs the running system as well. It provides functionality specific to debugging the Linux kernel and is much more suitable for advanced debugging.
If you want to debug the Linux kernel, you need to install its debugging information package in addition. Check if the package is installed on your system with:. Use YaST to enable the repository. To open the captured dump in crash on the machine that produced the dump, use a command like this:.
The first parameter represents the kernel image. The second parameter is the dump file captured by Kdump. SUSE Linux Enterprise Server ships with the utility kdumpid included in a package with the same name for identifying unknown kernel dumps. It can be used to extract basic information such as architecture and kernel release. It supports lkcd, diskdump, Kdump files and ELF dumps.
When called with the -v switch it tries to extract additional information such as machine type, kernel banner string and kernel configuration flavor. This file is usually called vmlinux and is directly generated in the compilation process. This is the file executed by the boot loader. The Linux kernel consists of two parts: the kernel itself vmlinux and the setup code run by the boot loader.
Source1: kdumpctl. Source2: kdump. Source3: kdump. Source7: mkdumprd. Source8: kdump. Source9: makedumpfile Source kexec-kdump-howto. Source mkdumprd. Source kexec. Source kdump. Source kdump-lib. Source kdump-in-cluster-environment. Source supported-kdump-targets. Source kdump-dep-generator. Source kdump-lib-initramfs. Source kdump-anaconda-addong4cc5.
Source kdumpctl. These are sources for mkdumpramfs. Which is currently in development. Source dracut-kdump. Source dracut-module-setup.
Source dracut-kdump-error-handler. Source dracut-kdump-emergency. Source dracut-kdump-capture. Requires post : systemd-units. Requires preun : systemd-units. Requires postun : systemd-units. Requires pre : coreutils sed zlib. Requires: ethtool. BuildRequires: zlib-devel zlib zlib-static elfutils-devel-static glib2-devel bzip2-devel ncurses-devel bison flex lzo-devel snappy-devel. BuildRequires: pkgconfig intltool gettext. BuildRequires: systemd-units.
Obsoletes: diskdumputils netdump. Patches 0 through are meant for x86 kexec-tools enablement. Patches through are meant for arm64 kexec-tools enablement. Patches onward are generic patches. Patch through are meant for kdump anaconda addon. Summary: Kdump configration anaconda addon. Security 4. Devices 4. Kernel 4. Virtualization 5. Deprecated Functionality 6. New Packages Expand section "6. New Packages" Collapse section "6. New Packages" 6.
RHEA — new packages: clufter 6. RHEA — new packages: lshw 6. RHEA — new package: python-argparse 6. RHEA — new packages: python-requests and dependencies 6. RHEA — new package: redhat-access-insights 6.
RHEA — new packages: scap-workbench 7. Updated Packages Expand section "7. Updated Packages" Collapse section "7. Updated Packages" 7. ImageMagick 7.
❿
