Hello,
Yes thanks you, MoM work correctly. Indeed 80% used threshold need to be raise
for memory release work :)
Thanks for support !
Bye,
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy
Hi,
Initially, when the VM is started, it consumes only 200 MB, because the
QEMU process
allocates memory from the OS only when accessed by the VM. Once the VM uses
26 GB,
QEMU process will also use at least 26 GB.
The ballooning starts shrinking the VM, only if the free memory on the host
is
Hi,
Does I need to activate for Clusters / Hosts, something more than:
On my Cluster > Optimization > Memory Balloon > Enable Memory Balloon
Optimization
I've already reboot / take in maintenance and Force MOM policy several time
since I try to make work Balloon
How to check if MoM work on
Hi,
did you put the host to maintenance and activated it again when you
enabled ballooning? Or search for a slightly hidden Sync MOM policy
link somewhere in the host area that would force it.
The log seems to indicate ballooning is either disabled or "not necessary".
Martin
On Tue, Jul 31,
Hi,
Log from my hypervisor after launch the test VM:
2018-08-01 17:45:58,209 - mom.RPCServer - INFO - ping()
2018-08-01 17:45:58,211 - mom.RPCServer - INFO - getStatistics()
2018-08-01 17:45:58,346 - mom.RPCServer - INFO - ping()
2018-08-01 17:45:58,347 - mom.RPCServer - INFO - getStatistics()
Hi,
> 2018-07-31 11:49:44,258 - mom.Monitor - DEBUG - Field 'mem_free' not known.
> Ignoring.
No, this is "normal". Should not affect ballooning.
> I can't find a INFO log file with My_VM- is ready
And the line where the GuestMonitor is starting? You need to get back
to the time the VM
Hi Martin,
No problem, thanks for our answer !
In posted log, you can see:
2018-07-31 11:49:44,258 - mom.Monitor - DEBUG - Field 'mem_free' not known.
Ignoring.
I think issue start here :/ ?
I can't find a INFO log file with My_VM- is ready
All Centos guests are fully supported ? (Centos
Hi,
sorry I could not answer yesterday.
What you need to check is whether the VM is reported as ready in the
log (/var/log/vdsm/mom.log). You should see lines like:
2018-08-01 10:52:25,648 - mom.GuestMonitor.Thread - INFO -
GuestMonitor-ms-vhost-1 starting
2018-08-01 10:52:25,648 -
Hello,
Is someone have an idea regarding my Memory balloon misconfig :/ ?
Thanks !
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code
9 matches
Mail list logo
