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 - mom.GuestManager - DEBUG - added monitor for guest c4f1ea89-457a-4049-97d7-11cf751d00f0 2018-08-01 10:52:25,648 - mom.Monitor - DEBUG - Using optional fields: set(['swap_out', 'swap_usage', 'balloon_cur', 'swap_total', 'balloon_min', 'major_fault', 'swap_in', 'io_tune_current', 'mem_unused', 'balloon_max', 'minor_fault', 'io_tune', 'mem_available']) 2018-08-01 10:52:25,649 - mom.Monitor - DEBUG - Using fields: set(['vcpu_count', 'vcpu_period', 'vcpu_user_limit', 'vcpu_quota']) ... 2018-08-01 10:52:25,808 - mom.Monitor - INFO - ms-vhost-1 is ready There might be a message reporting that some required data fields are not available and the ballooning won't work for that VM in such case. Best regards Martin Sivak On Wed, Aug 1, 2018 at 10:45 AM, <[email protected]> wrote: > Hello, > > Is someone have an idea regarding my Memory balloon misconfig :/ ? > > Thanks ! > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/FTNY4FQ4W52Z62GGFCXC567KOBJ2DJOI/ _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/VJSSYKXAVSLSIOYETGT6HTSVWPQOJV3B/
