The host xxx did not satisfy internal filter Memory because its available memory is too low
Hi, When I create vm after I have installed ovirt Node 4.1.1 successfully, I got this error message "The host xxxx did not satisfy internal filter Memory because its available memory is too low". I use ovirt node:ovirt-node-ng-installer-ovirt-4.1-2017032304.iso and ovirt-engine-appliance-4.1-20170322.1.el7.centos.noarch.rpm. And I followed the steps in http://www.ovirt.org/node/. I found the informations in "hosts"->"general"->"info" page: "Max free Memory for scheduling new VMs: 356 MB" "Physical Memory: 15747 MB total, 5039 MB used, 10708 MB free" Why the free memory for scheduling new vms is so little? Is there anything wrong with my configuration? Thanks in advance, Yiimao Yang.
Looks like a bug, the "Max free Memory for scheduling new VMs" in the case when we do not have memory optimization must be equal to the free memory on the host(minus some small amount of the reserved memory). Can you please provide the screenshot of the host in the engine and also output of the command # free -h on the problematic host. Best Regards On Sun, Mar 26, 2017 at 6:13 PM, yimao <yiimao.y@gmail.com> wrote:
Hi,
When I create vm after I have installed ovirt Node 4.1.1 successfully, I got this error message "The host xxxx did not satisfy internal filter Memory because its available memory is too low".
I use ovirt node:ovirt-node-ng-installer-ovirt-4.1-2017032304.iso and ovirt-engine-appliance-4.1-20170322.1.el7.centos.noarch.rpm. And I followed the steps in http://www.ovirt.org/node/.
I found the informations in "hosts"->"general"->"info" page: "Max free Memory for scheduling new VMs: 356 MB" "Physical Memory: 15747 MB total, 5039 MB used, 10708 MB free"
Why the free memory for scheduling new vms is so little? Is there anything wrong with my configuration?
Thanks in advance, Yiimao Yang. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I am sorry, how can I get the screenshot of the host in the engine? 2017-03-27 16:57 GMT+08:00 Artyom Lukianov <alukiano@redhat.com>:
Looks like a bug, the "Max free Memory for scheduling new VMs" in the case when we do not have memory optimization must be equal to the free memory on the host(minus some small amount of the reserved memory). Can you please provide the screenshot of the host in the engine and also output of the command # free -h on the problematic host.
Best Regards
On Sun, Mar 26, 2017 at 6:13 PM, yimao <yiimao.y@gmail.com> wrote:
Hi,
When I create vm after I have installed ovirt Node 4.1.1 successfully, I got this error message "The host xxxx did not satisfy internal filter Memory because its available memory is too low".
I use ovirt node:ovirt-node-ng-installer-ovirt-4.1-2017032304.iso and ovirt-engine-appliance-4.1-20170322.1.el7.centos.noarch.rpm. And I followed the steps in http://www.ovirt.org/node/.
I found the informations in "hosts"->"general"->"info" page: "Max free Memory for scheduling new VMs: 356 MB" "Physical Memory: 15747 MB total, 5039 MB used, 10708 MB free"
Why the free memory for scheduling new vms is so little? Is there anything wrong with my configuration?
Thanks in advance, Yiimao Yang. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Try to use "Print Screen" button :) Also, I wanted to correct my answer. it looks like a bug only in the case when the host does not have other VM's that run on it. In the case when you have other VM's that run on the host, possible the situation when the host free memory will be greater than "Max free Memory for scheduling new VMs". The variable "Max free Memory for scheduling new VMs" has straight relation to the guaranteed memory on the VM's that run on the host, but it does not the real amount of the allocated memory on the host. Best Regards On Mon, Mar 27, 2017 at 8:32 PM, yimao <yiimao.y@gmail.com> wrote:
I am sorry, how can I get the screenshot of the host in the engine?
2017-03-27 16:57 GMT+08:00 Artyom Lukianov <alukiano@redhat.com>:
Looks like a bug, the "Max free Memory for scheduling new VMs" in the case when we do not have memory optimization must be equal to the free memory on the host(minus some small amount of the reserved memory). Can you please provide the screenshot of the host in the engine and also output of the command # free -h on the problematic host.
Best Regards
On Sun, Mar 26, 2017 at 6:13 PM, yimao <yiimao.y@gmail.com> wrote:
Hi,
When I create vm after I have installed ovirt Node 4.1.1 successfully, I got this error message "The host xxxx did not satisfy internal filter Memory because its available memory is too low".
I use ovirt node:ovirt-node-ng-installer-ovirt-4.1-2017032304.iso and ovirt-engine-appliance-4.1-20170322.1.el7.centos.noarch.rpm. And I followed the steps in http://www.ovirt.org/node/.
I found the informations in "hosts"->"general"->"info" page: "Max free Memory for scheduling new VMs: 356 MB" "Physical Memory: 15747 MB total, 5039 MB used, 10708 MB free"
Why the free memory for scheduling new vms is so little? Is there anything wrong with my configuration?
Thanks in advance, Yiimao Yang. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
DId you mean this information? # free -h total used free shared buff/cache available Mem: 23G 7.6G 14G 17M 784M 15G Swap: 7.8G 0B 7.8G There was no additional vm when I got these information. I have added a 8GB memory to solve the problem, but Max free Memory for scheduling new VMs is 8484 MB. If you need ,I can unplug the memory and get the information again. Best Regards 2017-03-28 15:16 GMT+08:00 Artyom Lukianov <alukiano@redhat.com>:
Try to use "Print Screen" button :) Also, I wanted to correct my answer. it looks like a bug only in the case when the host does not have other VM's that run on it. In the case when you have other VM's that run on the host, possible the situation when the host free memory will be greater than "Max free Memory for scheduling new VMs". The variable "Max free Memory for scheduling new VMs" has straight relation to the guaranteed memory on the VM's that run on the host, but it does not the real amount of the allocated memory on the host.
Best Regards
On Mon, Mar 27, 2017 at 8:32 PM, yimao <yiimao.y@gmail.com> wrote:
I am sorry, how can I get the screenshot of the host in the engine?
2017-03-27 16:57 GMT+08:00 Artyom Lukianov <alukiano@redhat.com>:
Looks like a bug, the "Max free Memory for scheduling new VMs" in the case when we do not have memory optimization must be equal to the free memory on the host(minus some small amount of the reserved memory). Can you please provide the screenshot of the host in the engine and also output of the command # free -h on the problematic host.
Best Regards
On Sun, Mar 26, 2017 at 6:13 PM, yimao <yiimao.y@gmail.com> wrote:
Hi,
When I create vm after I have installed ovirt Node 4.1.1 successfully, I got this error message "The host xxxx did not satisfy internal filter Memory because its available memory is too low".
I use ovirt node:ovirt-node-ng-installer-ovirt-4.1-2017032304.iso and ovirt-engine-appliance-4.1-20170322.1.el7.centos.noarch.rpm. And I followed the steps in http://www.ovirt.org/node/.
I found the informations in "hosts"->"general"->"info" page: "Max free Memory for scheduling new VMs: 356 MB" "Physical Memory: 15747 MB total, 5039 MB used, 10708 MB free"
Why the free memory for scheduling new vms is so little? Is there anything wrong with my configuration?
Thanks in advance, Yiimao Yang. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Looks like a bug, the "Max free Memory for scheduling new VMs" in the case when we do not have memory optimization must be equal to the free memory on the host(minus some small amount of the reserved memory).
This is unfortunately not accurate at all. Max free Memory for scheduling new VMs takes into account the theoretically possible maximal memory consumption of all running VMs. But the Linux kernel and Qemu won't eat all the physical memory immediately. That is why you can see pretty big difference between those two numbers (free memory and memory available for new VMs). For example: Host 10 GiB of RAM 2 running VMs configured to eat 4GiB of RAM each but the VMs are not doing anything and really use only 1GiB of RAM each The result? Max memory for new VMs: 2 GiB, Free memory on the host: 8 GiB How many VMs are you running on the host? What are their memory allocations? Best regards -- Martin Sivak SLA / oVirt On Mon, Mar 27, 2017 at 10:57 AM, Artyom Lukianov <alukiano@redhat.com> wrote:
Looks like a bug, the "Max free Memory for scheduling new VMs" in the case when we do not have memory optimization must be equal to the free memory on the host(minus some small amount of the reserved memory). Can you please provide the screenshot of the host in the engine and also output of the command # free -h on the problematic host.
Best Regards
On Sun, Mar 26, 2017 at 6:13 PM, yimao <yiimao.y@gmail.com> wrote:
Hi,
When I create vm after I have installed ovirt Node 4.1.1 successfully, I got this error message "The host xxxx did not satisfy internal filter Memory because its available memory is too low".
I use ovirt node:ovirt-node-ng-installer-ovirt-4.1-2017032304.iso and ovirt-engine-appliance-4.1-20170322.1.el7.centos.noarch.rpm. And I followed the steps in http://www.ovirt.org/node/.
I found the informations in "hosts"->"general"->"info" page: "Max free Memory for scheduling new VMs: 356 MB" "Physical Memory: 15747 MB total, 5039 MB used, 10708 MB free"
Why the free memory for scheduling new vms is so little? Is there anything wrong with my configuration?
Thanks in advance, Yiimao Yang. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Yes, you are right. The HostedEngine vm's default Memory Size is 14940 MB. When I turn down the memory size, the Max free Memory for scheduling new VMs has increased. Thank you very much. 2017-03-28 16:57 GMT+08:00 Martin Sivak <msivak@redhat.com>:
Looks like a bug, the "Max free Memory for scheduling new VMs" in the case when we do not have memory optimization must be equal to the free memory on the host(minus some small amount of the reserved memory).
This is unfortunately not accurate at all.
Max free Memory for scheduling new VMs takes into account the theoretically possible maximal memory consumption of all running VMs. But the Linux kernel and Qemu won't eat all the physical memory immediately. That is why you can see pretty big difference between those two numbers (free memory and memory available for new VMs).
For example:
Host 10 GiB of RAM 2 running VMs configured to eat 4GiB of RAM each but the VMs are not doing anything and really use only 1GiB of RAM each
The result? Max memory for new VMs: 2 GiB, Free memory on the host: 8 GiB
How many VMs are you running on the host? What are their memory allocations?
Best regards
-- Martin Sivak SLA / oVirt
On Mon, Mar 27, 2017 at 10:57 AM, Artyom Lukianov <alukiano@redhat.com> wrote:
Looks like a bug, the "Max free Memory for scheduling new VMs" in the case when we do not have memory optimization must be equal to the free memory on the host(minus some small amount of the reserved memory). Can you please provide the screenshot of the host in the engine and also output of the command # free -h on the problematic host.
Best Regards
On Sun, Mar 26, 2017 at 6:13 PM, yimao <yiimao.y@gmail.com> wrote:
Hi,
When I create vm after I have installed ovirt Node 4.1.1 successfully, I got this error message "The host xxxx did not satisfy internal filter Memory because its available memory is too low".
I use ovirt node:ovirt-node-ng-installer-ovirt-4.1-2017032304.iso and ovirt-engine-appliance-4.1-20170322.1.el7.centos.noarch.rpm. And I followed the steps in http://www.ovirt.org/node/.
I found the informations in "hosts"->"general"->"info" page: "Max free Memory for scheduling new VMs: 356 MB" "Physical Memory: 15747 MB total, 5039 MB used, 10708 MB free"
Why the free memory for scheduling new vms is so little? Is there anything wrong with my configuration?
Thanks in advance, Yiimao Yang. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (3)
-
Artyom Lukianov -
Martin Sivak -
yimao