Jump into your mysql cloud db. Run this:
select op.id, name, total_capacity from op_host_capacity op, host h
where op.capacity_type=0 and op.host_id=h.id;
(my example output from a test cloud)
++-++
| id | name| total_capacity |
++-+--
Currently, if you really want to overcommit RAM, there is a workaround with
KVM, but it involves to modify the value reported by the host directly in
the database.
On Wed, Jul 17, 2013 at 12:14 PM, Tao Lin wrote:
> Hi,Andreas,
> Memory over-committing has not been support yet.Take a look at
9(176) 10308549
ahu...@7five-edv.de
- Ursprüngliche Mail -
Von: "Tao Lin"
An: users@cloudstack.apache.org
Gesendet: Mittwoch, 17. Juli 2013 12:14:10
Betreff: Re: Memory Overcommit + KVM
Hi,Andreas,
Memory over-committing has not been support yet.Take a look at the
followi
Hi,Andreas,
Memory over-committing has not been support yet.Take a look at the
following links:
[1] http://markmail.org/message/u6i5mdwyf42icsff
[2] https://cwiki.apache.org/CLOUDSTACK/cpu-and-ram-overcommit.html
2013/7/17 Andreas Huser
> Hello at all,
>
> i have two KVM Hypervisors with equa
Hello at all,
i have two KVM Hypervisors with equal RAM à 16GB
In the Cloudstack zone resource tab can i read "Allocated: 15.30 GB / 31.13 GB".
When i configure memory overcommit *2 and restart the Cloud Manager. I see the
same "Allocated: 15.30 GB / 31.13 GB"
Must this not now like e.g "Allocat
