Vmware:linux start hint memory for Crashkernel (0*0 to 0*0) not within permissible

(virtualbox/vmware) linux start hint Memoryforcrashkernel (0*0 to 0*0) notwithinpermissible http://www.myexception.cn/ Linux-unix/477672.html

One. Virtual machines are created on VMware and the operating system is red Hat Enterprise Linux Server release 5.3, and the following information appears when you start the virtual machine:

Memory for crash kernel (0x0 to 0x0) Notwithin permissible range

Workaround:

This information is not compromised because there is no reason to configure the Kdump service. Kdump is a new, and very trustworthy, kernel crash dump mechanism. This article [kdump How to configure http://blog.csdn.net/cybertan/article/details/5661681] Describes how to configure and enable Kdump services, and we can also use the following The graphical interface to configure and enable the following steps:

(1) Configure the Kdump.

Select the menu "Applications"--"System Tools"-"kdump", pop Up the "Kernel Dump Configuration" window, select Enable Kdump, set new Kdump Memory (MB): 128MB (recommended size), Location:file:///var/crash (can also be set to a different location for storing the dump image when the system crashes).

(2) Reboot the system, the error disappears.

Two. The virtual machine is created on VirtualBox and the operating system is red Hat, and the following information appears when you start the virtual machines:

Memory for crash kernel (0x0 to 0x0) Notwithin permissible range

Workaround:

Select the menu "Settings"--"system"--"Extended properties" and check Enable IO APIC.

============================================================================

Kdump How to configure http://blog.csdn.net/cybertan/article/details/5661681

eg in CentOS:

1. Confirm that the Kexec-tools has been installed:
#rpm-Q Kexec-tools

[Email protected] jz2440]# rpm-q kexec-toolspackage kexec are not Installed[[email protected] jz2440]# Yum Install  kexec-tools

2. Configure the/etc/kdump.conf file to specify the path to which the vmcore will be dumped. It can be copied to another server via SCP, or it can be a bare device, or a local file system.

3. Modify some startup parameters to preserve a chunk of memory for the capture. For i386 and x86_64 schemas, edit the/etc/grub.conf and add [email protected] at the end of the kernel line.
         The following is an excerpt of a/etc/grub.conf file with the Kdump option:
         kernel/boot/vmlinuz-2.6.17-1.2519.4.21.el5 ro root=label=/rhgb quiet [email protected]
 & nbsp      
4. After the modification, restart the system. 128M of memory (starting from 16M) is not used by normal systems and is reserved for capturing the kernel. Note that the output of free-m shows that memory is less than 128M without parameters, which is what we expect.
Note: You can use less than 128M, but testing with only 64M is proven to be unreliable.

5. Now that the reserved memory is set, open the Kdump initial script, start the service:
# chkconfig Kdump on
# service kdump start; Note that disk space is sufficient.

 [[email protected "jz2440]# service kdump startno kdump initial ramdisk found. [WARNING] Rebuilding /boot/initrd-2.6 . 18 - . el5kdump.imgWarning:There  is   not         Enough space to save a vmcore. The size of /dev/sda2 should be much greater than 1035108  kilo bytes. 
 [[email protected] jz2440]# df /dev/sda2 
 filesystem            1k-blocks      used Available use% mounted on 
/dev/sda2               3960348   3032792    723132  81%/

6. The kernel image can be loaded via kexec, allowing the system to be ready to capture a crash-generated vmcore. You can force a system crash through SYSRQ:

# echo "C" >/proc/sysrq-trigger
This causes kernel panic, followed by the system reboot Kdump kernel. When the boot process enters the boot kdump server, Vmcore will be copied to the location you specified in the/etc/kdump.conf file.

Attention:
Terminal Frame-buffer and X will not run properly. When running a system that is similar to adding "Vga=791″" or "Running X" on the kernel configuration, the terminal display will not be clear when booting the kernel via kexec. Remember, the Kdump kernel is still able to create dumps. When the system restarts, the display will return to its normal state.

Vmware:linux start hint memory for Crashkernel (0*0 to 0*0) not within permissible