5

RHEL 3.4 Guest cannot allocate memory from Centos with xen kernel

view full story
linux-howto

https://www.centos.org – Best of my knowledge you have to run a paravirtualized guest to have it take advantage of memory adjustment. For PV guests you have to load the xen-balloon kernel module to catch memory adjustments. [by TrevorH] (Distributions)

ziyi's picture
Submitted by ziyi on 02/10/2010 – Made popular on 02/10/2010

Stories similar to RHEL 3.4 Guest cannot allocate memory from Centos with xen kernel

The kernel configuration option:

VMware Balloon Driver (VMWARE_BALLOON) [N/m/y/?] (NEW) ?

CONFIG_VMWARE_BALLOON:

This is VMware physical memory management driver which acts like a "balloon" that can be inflated to reclaim physical pages by reserving them in the guest and invalidating them in the monitor, freeing up the underlying machine pages so they can be allocated to other guest

How Secure Is Chroot()? 1 year 39 weeks ago

I know this post is old, but: Before you completely drop virtual machines as an option, have a look at the linux-vserver project.

I have a VMware ESXi 3.5 hypervisor host with a bunch of guest VMs on it.

I am trying to use the mamp() functionality provided in linux-kernel. As we call mmap() in user-space we try to map virtual memory area of user-space process to the memory in the kernel-space.

the definition of mamp() inside kernel is done in my kernel module which try to allocate some memory in pages & maps it during mmap system call.

I've got a user-mode process and kernel module.

Quote:ldajnowski wrote:... when I change the memory allocation for the Guest in the Virtual Machine Manager and shut down the Guest ...

To allocate memory to dom 0 9 weeks 5 days ago

That one is even more in need of yum updating than the other! That looks like the Centos 5.1 kernel from 2007. [by TrevorH]

You are running `free` on Dom0 and this is actually a specialised DomU guest so only reports what Xen wishes it to see. The amount of memory reported by xm top is correct and what is really detecte... [by TrevorH]

Embedded system, no swap, kernel v2.6.36, memory compaction enabled.

Under heavy usage, all the RAM is tied up in cache. Cache was using about 70M of memory. When a user space process allocates memory, no problem, cache gives it up.

But there's a 3rd party device driver that seems to try to allocate a physical 5th order page, and fails with OOM. A quick look at buddyinfo confirms this...