Re: [ovirt-users] VM "hot" RAM memory decrease

I can't really help without the mom.log and the virsh dumpxml output of that VM in the final state (all memory ballooned). Min guaranteed should be respected, but the question is how the physical memory was measured (which number from top was used). -- Martin Sivak SLA / oVirt On Tue, Mar 28, 2017 at 4:29 PM, Michal Skrivanek <michal.skrivanek(a)redhat.com&gt; wrote: > >> On 27 Mar 2017, at 23:15, Nicolás <nicolas(a)devels.es&gt; wrote: >> >> Hi, >> >> I don't really know if this question is suitable on this list, as I doubt it's an oVirt bug, neither I know if it shall be considered a bug. >> >> We recently run a VM on a host that was memory over-used (around 80% of usage). The VM booted correctly, then we run "top" and saw how physical RAM started decreasing every two seconds. At first it was 4GB, then less and less until it stabilized at around 600MB. >> >> Based on this (correct me if I'm wrong), we believe this is an effect of having this VM with ballooning enabled, as it does exactly this: It adds/removes RAM depending on host decision. Thing is that this VM had a minimal guaranteed RAM of 1GB, so even if this happened due to ballooning, I'm not sure if it should have honored the minimum guaranteed RAM. >> >> When this happened, we run a 'ps' to see with what options the qemu process was invoked, and parameters seemed correct (that's why I don't know if it should be posted here or even if it's a bug). > > It does belong here, it’s a different component doing it “externally” to the qemu process- mom. > >> >> Is this the expected behavior? > > > Thanks, > michal > >> >> Thanks. >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >> >