Hi Motty, I just saw your other email, found this ( https://issues.apache.org/jira/browse/CLOUDSTACK-5968) this morning, might be worth upgrading CS to the latest master? (or 4.3 forward?) Not sure why I haven't been hit by these memory commit issues, I have several VMS with 20GB and 60GB RAM with no issues. Host: Ubuntu 12.04, various Guests.
Below is my overprovisioning factor: mem.overprovisioning.factorUsed for memory overprovisioning calculation1.5 I feel there is some confusion in the mailing list about this issue. My understanding is that the overprovisioning factor effects the overall statistics of the host, therefore, if a host had 10GB of RAM and a mem.overprovisioning.factor of 1.5, CS could allocate upto 15GB of VM memory. Is this incorrect? I came to this conclusion by the normal terminology of 'over-provisioning' and the basis that CPU is done in that fashion 'Used for CPU overprovisioning calculation; available CPU will be (actualCpuCapacity * cpu.overprovisioning.factor)', also storage Used for storage overprovisioning calculation; available storage will be (actualStorageSize * storage.overprovisioning.factor). It seems odd the random spike of people complaining about this issue, I personally have never seen CS do this before, either in real life or on the mailing lists last year. Marty On Thu, Feb 6, 2014 at 4:11 PM, motty cruz <motty.c...@gmail.com> wrote: > Hi Marty, > > I am running CentOS 6.5 64bit host with CloudStack 4.2.0, I am having a lot > of issues. I can't install FreeBSD 10 64bit only FreeBSD 9.2 i386. > > can't allocate more than 3GB of RAM on guest instances, running 64bit > Centos on guest. > > any recommendations? > > > On Wed, Feb 5, 2014 at 1:24 PM, Marty Sweet <msweet....@gmail.com> wrote: > > > This was brought up last month in the dev mailing list, look for 'KVM > > memory overprovision breaking me'. > > > http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201401.mbox/date?16 > > > > This explains the background behind it quite well: > > http://blog.braastad.org/?p=211 > > > > 'rmmod virtio-balloon' is a temporary fix, however I am running KVM with > > 4.2.0 > > and I have never had this issue (currentMemory always equals memory). > > > > Marty > > > > > > > > > > On Wed, Feb 5, 2014 at 8:10 PM, motty cruz <motty.c...@gmail.com> wrote: > > > > > Hi, Thanks for your reply > > > <name>i-2-95-VM</name> > > > <uuid>129a3e1b-ce45-4d9f-9f3f-af95b82dfe09</uuid> > > > <description>Other PV (64-bit)</description> > > > <memory unit='KiB'>8388608</memory> > > > <currentMemory unit='KiB'>4194304</currentMemory> > > > <vcpu placement='static'>2</vcpu> > > > <cputune> > > > <shares>2000</shares> > > > </cputune> > > > <os> > > > <type arch='x86_64' machine='rhel6.5.0'>hvm</type> > > > <boot dev='cdrom'/> > > > > > > > > > in the machines : > > > [root@hdp1 ~]# free -m > > > total used free shared buffers > cached > > > Mem: 3774 3610 164 0 4 > 553 > > > -/+ buffers/cache: 3052 722 > > > Swap: 7999 1692 6307 > > > > > > [root@hdp1 ~]# uname -a > > > Linux hdp1.fqdn.com 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 > 21:39:27 > > > UTC > > > 2014 x86_64 x86_64 x86_64 GNU/Linux > > > > > > > > > > > > > > > On Wed, Feb 5, 2014 at 11:46 AM, Marty Sweet <msweet....@gmail.com> > > wrote: > > > > > > > Also, it might be worth confirming the VM is 64bit. > > > > > > > > # uname -a > > > > > > > > Marty > > > > > > > > > > > > On Wed, Feb 5, 2014 at 7:44 PM, Marty Sweet <msweet....@gmail.com> > > > wrote: > > > > > > > > > Hi, > > > > > > > > > > Can you run the following command on the hypervisor where the VM > > > resides: > > > > > > > > > > # virsh dumpxml i-X-XX > > > > > > > > > > Where i-X-XX is the internal system name of the VM. > > > > > > > > > > Marty > > > > > > > > > > > > > > > On Wed, Feb 5, 2014 at 6:55 PM, motty cruz <motty.c...@gmail.com> > > > wrote: > > > > > > > > > >> Hello All, > > > > >> I created a System Offering with 2 Core CPU and 8GB or RAM. > > > > >> > > > > >> when I build the first Instance it only had 3GB, a CentOS VM 64bit > > > > >> less /proc/meminfo > > > > >> MemTotal: 3865376 KB. > > > > >> > > > > >> any idea how to fix this issue? > > > > >> > > > > > > > > > > > > > > > > > > > >
