Hi Dinu,
you can change the system service offering in 4.2.
refer to this link
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.1/html/Admin_Guide/system-service-offerings.html
This is for 4.1 but will work with 4.2 as well.
As per the overcommit settings getting applied to the rou
Thanks Bharat,
As far as I'm aware, the only way to change the default system VM offering for
a domain router can be done by modifying the database (altering the
disk_offerings table). One can change it when a router is not running, but with
multiple routers in a cloud it may become tedious.
Thanks Bharat. It would be nice if you can add an example in the FS [1],
an example of calculation.
Say admin decides an overcommit ration for memory = 2. Similarly for cpu.
What does it mean for the capacity of his cluster ?
What does it mean when a vm gets deployed with service offering 1 gb
Wha
Hi Dinu,
you can modify the system service offering for the systems vms and change it to
512MB so that when using overcommit (of 4 ) its memory is set to 128 MB.
you are right the current memory is set to system offering divided by the over
provisioning factor.
On Aug 22, 2013, at 2:05 AM,
Hi Dinu,
I agree that overprovisioning factors should not affect system VMs
Jerry
-邮件原件-
发件人: Dinu Arateanu [mailto:dinu.arate...@gmail.com]
发送时间: 2013年8月22日 星期四 4:36
收件人: users@cloudstack.apache.org
主题: KVM/mem.overprovisioning.factor
Hello,
I'm testing ACS 4.2 with kvm. I no
Hello,
I'm testing ACS 4.2 with kvm. I noticed that when one configures
mem.overprovisioning.factor Global/Cluster setting, chances are that the System
VMs configured with an offer of 128 MB RAM will never start (namely the Domain
Router and the SSVM).
According to the agent.log, ACS sends li
