Sorry, yes i meant a bug in ovirt with SLES, not in SLES :).
Now, I understand all the details. Thanks a lot !
I will then open a bug as suggested, never did it before but hope it will be
Users mailing list --
>Ok, May I know why you think it's only a bug in SLES?.
I never claimed it is a bug in SLES, but a bug in Ovirt detecting proper memory
usage in SLES.
The behaviour you observe was normal for RHEL6/CentOS6/SLES11/openSUSE and
bellow , so it is normal for some OSes.In my oVirt 4.3.10 , I see that
Ok, May I know why you think it's only a bug in SLES?.
As I said before, ovirt is behaving the same way even for CentOS7 VMs. I am
attaching the details again here below.
One of running CentOS VM memory details are as below.
[centos@centos-vm1 ~]$ free -m
For some OS versions , the oVirt's behavior is accurate , but for other
versions it's not accurate.
I think that it is more accurate to say that oVirt improperly calculates memory
for SLES 15/openSUSE 15.
I would open a bug at bugzilla.redhat.com .
I think I already checked that.
What I meant (since beginning) was that ovirt is reporting memory usage in GUI
same way regardless of CentOS or SLES in our case.
My main question is why ovirt is reporting memory usage percentage based on
"free" memory but not actually based on "available
In Some OS versions it should not be considered a bug.
For RH , you can address https://access.redhat.com/solutions/406773 for more
details. (For access , you can use a free subscription from
В четвъртък, 17 септември 2020 г.,
Most of our VMs are SLES SP15 and also few are CentOS 7. But the problem looks
to be same for any type of VM.
Today, I tried to clear the "buff/cache" memory manually for one of the VM
using "sync; echo 3 > /proc/sys/vm/drop_caches" linux command and then I
noticed in ovirt GUI that VM's
What is your VM's OS type ?
There is some differences per OS version ->
В сряда, 16 септември 2020 г., 11:13:51 Гринуич+3, KISHOR K
Memory field/column for few of VMs in our ovirt
Mail list logo