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
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]
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]
I have a KVM machine with CentOS 6.4 (64bit), I have a Linux guest running
well on this, I created a Windows 2008 R2 guest and once I start it, after
sometime all the host memory get exhausted and both the guests (linux+win)
Host has 32 GB RAM, 8 GB is allocated to Linux guest and 8 GB to Windows.
Running Ubuntu 13.04 Host and vm Guest.
Using virtio for hdd, nic. Max-allocaion CPU cores is 6, minimum is 2.
Ive made a vm with virt-manager just to play with, and to test out kvm.
Alright, I have a decent understand how the memory balloon driver works, but I still dont know how to test if the guest OS can utilize the max setting for cpu cores.
First impression of relase candidate: Fedora 12 seems to be fine!
Reasons for Fedora 12:
I've chosed fedora (12) because of "unofficial?" dom0 support provided by m.young.
I would like to use fedora 12 as (xen) host for virtual guests (centos 5.x) because of "better" hardware support in newer (dom0) kernels.