i have installed kernel-xen to my centos 5.4 server ( with yum install kernel-xen ). My server has got 8192 mb pyschal ram with PAE kernel; but after i installed xen kernel to system, my ram is being 7919664KB....how can i fix this ? i want see 8192MB RAM with xen kernel
I have a server for virtualization (Xen) and when I do a free -m it does not show all the memory (which should be 64GB), it shows 32GB (a considerable difference, isnt it?).
My hardware is a Dell R410 server: Dual Xeon 5530 64GB DDR3 4x SAS 500GB in RAID 10
I tried to compile Xen 4.0.1 but I can't solve a compile error that it gives me (if you want to take a look: [URL]) that is the end of the compilation including the error. But, I installed Xen from yum directly after reformating the HD and it works fine now.
My kernel version: 2.6.18-194.26.1.el5xen x86_64 CentOS 5.5 64 bit [root@server1 xen-4.0.1]# cat /proc/meminfo MemTotal: 33554432 kB
After CentOS5.3 install to /sdb7 partition (on 2nd HD) and using Ubuntu Grub(on 1st HD mbr) to boot CentOS, I get "memory for crash kernel 0x0 to 0x0 not within permissible range" as soon as CentOS starts. I have 2G of ram. The message is on every boot. I've had several other linuxes on that partition without such an error message. Otherwise the OS starts fine. Is the message of concern/import?
Is that possible that SHM shared memory is counted as cache memory on Linux with kernel 2.6.18?If find it really odd since this memory is not file backed, but I have a piece of code that loads data using shm_open+mmap, and it generates an amount of cache memory in /proc/meminfo that corresponds exactly to the amount of shared memory (I load that data from a file but I am using posix_fadvise(fd,0,0,POSIX_FADV_DONTNEED) to ensure this file is not cached and I made sure that it is working as expected). As far as I know SHM memory was not tagged as cache memory with kernel 2.6.9.If it is the case it is really unfortunate since normally cache memory can be considered to be part of the "available" memory since it can be flushed promptly but this is clearly not the case with SHM memory... Is there an easy way to get the total amount of used SHM memory on a system?
I'm fairly new to linux Red Hat. We are running Rhel 3 on our VM's. We ran into a issue, (Bug 121801 - athlon-smp kernel does not support >4GB of RAM. what the stepos are to upgrade the existing kernel to the new i686? .
I just ran into a weird problem with a CentOS 5.5 64-bit server running VirtualBox 3.2.8 (I would run Vmware Server 2.0.2 if not for the well known fact that Vmware doesn't care about its Server line anymore and it doesn't run on CentOS > 5.3 without major splits). I currently have two guests in that VirtualBox setup, a CentOS 5.5 64-bit and a Fedora 13 64-bit. The CentOS 5.5 guest shows less memory available than configured. If, for example, I give the virtual machine 512MB of memory the guest OS only recognizes 380MB. If I give it 768MB it only recognizes 637MB, and so on. I don't have that problem on the Fedora guest - 1024MB configured, 1024MB available.
My computer has 4GB installed but for some reason I could only see the 2 of the 4. At first I thought that this was because the XEN virtual operating system manager was running but even after I turned it off the problem exists. I could only see and use the 2GB of memory.
Why my 10.04 install runs out of memory when it has hardly had chance to load the kernel. The symptoms were that it sometimes will hang after the grub screen with a blinking cursor. My user space splash screen doesn't appear either, it was when I was trying to fix that that I spotted the problem:
from my dmesg file: Code: [5.778823] lowmem_reserve[]: 0 0 24846 24846 [5.778829] HighMem free:3204284kB min:512kB low:3852kB high:7196kB active_anon:192kB inactive_anon:256kB active_file:596kB inactive_file:2288kB unevictable:0kB isolated(anon):0kB isolated(file) :0kB present:3180408kB mlocked:0kB dirty:0kB writeback:0kB mapped:1240kB shmem:144kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:356kB unstable:0kB bounce:0kB writeback_ tmp:0kB pages_scanned:0 all_unreclaimable? no ..... This is a few seconds after loading the kernel.
How do I get rid of this message during boot. I have tried the system-config-kdump command but it gives me a "no command found" reply. I am using CentOS 5.4
I'm using centos 5.4 on an Hp Compaq 500B, 4GB ram,I have just installed centos when i try to boot the pc it says "memory for crash kernel not in permissible range, pci not using mmconfig" then it shuts down after a while.
I've installed LINUX for the very first time and when i rebooted it, i found this message on my screen "Memory for crashkernel notwithin permissible range" I tried all my attempt like given memory to kernel with this command "crashkernel=64M@16M" but no luck... Finally i tried to boot into single user mode might be it helped me..but same results
I am having a problem with lockups on a new FC12 box (dual core 3 ghz, 4 gb memory,HDPVR,nvidia 8400gs). This happens reliably when replaying MythTV videos, but also randomly at other times using other apps (I suspect also boot but I can't be sure; it just occasionally stalls part way through the boot display).
Usually but not always this is accompanied by a kernel panic (caps lock + scroll lock lights flash on keyboard).
I did a core dump with kdump and it reports:
Thread 1 (<main task>): Cannot access memory at address 0xffff880028025b70
I am in the process of running memtest86+ right now, and it's been through several passes without errors. I know it needs to run more, but given the reliability of this problem with MythTV video playback I am wondering if the problem could be in the video card memory.
Does anyone know of a linux (or bootable) tester for video memory? All I am able to find are some things for windoze like this.
Also is there any way to track that address from the core dump back to a physical location?
this is a dual boot XP/UBUNTU 10.04. while using XP, the computer rebooted itself. the GRUB's screen appears, but neither the ubuntu nor the XP option works.
Ubuntu gives this error message:
Code: 0.797795 kernel panic-not syncing: vfs: enable to mount root fs on unknown-block (0,0)
XP hangs on a black screen... and that is it (thanks for support windows!) UBUNTU 10.04 live CD hangs when the 5 processing dots appears bellow the ubuntu logo. hangs the same way with the processing bar in UBUNTU 9.04 live CD. memory check (memtest86) is showing thousands of errors right from the start.
I am having a problem with lockups on a new FC12 box (dual core 3 ghz, 4 gb memory, HDPVR, nvidia 8400gs). This happens reliably when replaying MythTV videos, but also randomly at other times using other apps. Usually but not always this is accompanied by a kernel panic (caps lock + scroll lock lights flash on keyboard).
I did a core dump with kdump and it reports: Thread 1 (<main task>):
Cannot access memory at address 0xffff880028025b70I am in the process of running memtest86+ right now, and it's been through several passes without errors. I know it needs to run more, but given the reliability of this problem with MythTV video playback I am wondering if the problem could be in the video card memory. Any linux (or bootable) tester for video memory? All I am able to find are some things for windoze such as this. Also is there any way to track that address from the core dump back to a physical location?
I installed CentOS 5.4.. I saw this message: Memory for crash kernel (0x0 to 0x0) notwithin permissible range Is it ok? I google around it said that it is a known issue and harmless. I installed CentOS 5.2 before. It was ok. Kernel is 2.6.18 too. Just wonder why Kernel version: Linux phot1-nec4 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
Aug 16 21:41:14 server1 kernel: __ratelimit: 6 callbacks suppressed Aug 16 21:41:14 server1 kernel: Out of socket memory Aug 16 21:41:29 server1 last message repeated 21 times
As i undertsand - out of 1GB of the virtual Address space for Kernel from 3GB to 4GB of the process address space, Kernel image (code, data, bss, stack, heap) resides staring @0x0 address. Vmalloc area starts either at the end of Physical ram size or at 896M. This 896M cap is mandated to ensure that minimum of 128MB is reserved as vmalloc_reserve for vmalloc,kmap etc.
Is the understanding correct? Now trying to map Physical Zones into this 1GB address space
Initial 16MB is mapped to ZONE_DMA 16MB - 896MB is mapped to ZONE_NORMAL 896MB - 1024MB is mapped to ZONE_HIGHMEM
Does this mean that Kernel image is residing in ZONE_DMA area? Any call to vmalloc() in kernel code will return address beyond 896M? insmod of any LKM will internally invoke vmalloc() to obtain contiguous area - where will this code physically located along with rest of kernel code in ZONE_DMA or in ZONE_HIGHMEM?
I used mkinitrd to build an initrd from the slackware 2.6.37.6 sources. Lilo throws the following: "Warning: The initial RAM disk is too big to fit between the kernel a the 15M-16M memory hole. It will be loaded in the highest memory as though the configuration file specified "large-memory" and it will be assumed that the BIOS supports memory moves above 16M."
Also, I am running swap, / and home on an encrypted volume group. When the initrd boots (but prior to mounting the encrypted vg) I get a message saying that no modules are found-sounds like a daft question but is this expected? I expect that this is because initrd is looking for modules, but can't find them because the relevant partition isn't mounted.
after update to kernel-2.6.18-164.el5 one of the 2 NIC's of my machine are only found at 1 of 4 reboots. Using the old one kernel-2.6.18-128.7.1.el5 all is fine. This are the to NIC's:
I compiled my kernel, compiled scsi support into kernel, used the new kernel and initrd, the boot failed.Then ,i unzip my initrd, found that sd_mod.ko can't be insert, i added it manual, and reboot OK.so, why! in the kernel configure , the sd_mod.ko is set to <M> , but why it can't be found in initrd?
The server runs# uname -r2.6.18-128.4.1.el5However, today I executed yum update kernel*due to security advisory. I was just about to reboot the system when I realized that it runs VMWare Server Instance that will most likely fail to restart after kernel upgrade (I had a hard time fixing it after previous kernel update). Now I want to keep 2.6.18-128.4.1.el5 after reboot.I see that new kernel is scheduled for booting:
I'm running CentOS 5.3 and would like to know what the "best" or "proper" method is to build a custom kernel using the generic kernel sources from kernel.org. Most of the references I've found talk about modifying the current CentOS kernel using the RPM way. I really want to have the latest kernel due to some important security issues that haven't been addressed in the current CentOS 5.3 kernel.
The problem seems to be a memory issue. Seems the problem only started happening after the last few updates. I have tested the memory with memtest and both servers passed. There hasn't been any new software put on the servers for over 12 months. Server 1 - 3 gig of memory CentOS 5.2 - Linux version 2.6.18-92.1.18.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Wed Nov 12 09:19:49 EST 2008 Errors in log
I ma porting an application from SUSE 10 Professional 64-bit to CentOS 5.3 x64 version. We have set the /etc/php.ini as in old server and set the maximum memory limit to 5GB (yes! We have ample of memory) for the process.It was working fine in old server but in new server, the Apache log always showed that it failed to allocate more memory for the application.We noticed that the error coming out while the application uses up to 1GB memory.Just wish to ask if the PHP in CentOS 5.3 has any restriction on memory usage?
I installed new CentOS 5.5(X86_64) on my server. My server has 48 G RAM (12*4G) and can be found when starting server. Moreover, I installed dmidecode software to detect the memory. This software can find all the memory. I used command (top, cat /proc/meminfo) to check memory. Both commands can only find 33G RAM. uname -a command output like this: 2.6.18-194.el5xen #1 SMP Fri Apr 2 15:34:40 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
I have xen kernel on a 5.4_64 though it seems to have always done this regardless of version. When I add a virt the control set shows the total machine memory minus what I just allocated to the new virt. This also shows up in the system monitor as total available ram. Problem arises in deleting and making new virts. The memory never reappears as usable after deleting virts. So now after testing several different setups I'm down to 1.4 gigs showing available on the dom0. What can I do to recover this lost memory? I've searched, read, looked every where I could think of and there just doesn't seem to be any information about deleting virts only adding them.
root@XXXXX:~# uname -a Linux myserver 2.6.18-194.11.4.el5 #1 SMP Tue Sep 21 05:40:24 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux I'm having serious memory leak issues on a server running CentOS. Running 'top' I can't find any proccess with an unusual memory usage. Is there any other way to check what is using this memory? Right now it shows that I have 4.8GB of RAM used, but top shows only few proccesses, one with 4% and lots of 0.0%.
I have a web server with the specs below and my apache server is being a hog using all my RAM 7gigs or 8gigs of ram. When there is a rush of traffic at once my whole server crashes and I have to reboot apache. The way my site is set up I have a tube script and I use the tube script to host videos on my forum I have 1000 videos on the tube script. I brought a bigger server and more ram because of the down time I been having . I am really trying to figure out why its crashing and using so much ram. I installed eAccelerator didn't seem to help with the apache server.
Intel Quad Core Xeon X3430 (4 x 2.40 GHz, 8MB Cache) > 2-bay Supermicro Chassis and Motherboard > 8 GB REG ECC DDR3 (twice your current setup) > 250 GB Enterprise Grade SATA II > 10 TB Bandwidth 1gig Uplink Port > CentOS 64 Bit (Latest Stable)
TOP Command and free -m command screenshots are attached this is with only 160 people online at once