Created attachment 970055 [details] vdsm log file Description of problem: ERROR 'no free file handlers in pool' in vdsm.log Version-Release number of selected component (if applicable): Name : vdsm Arch : x86_64 Version : 4.14.17 Release : 0.el6 How reproducible: Create a new cloned VM from a template. Actual results: Load skyrockets on the hypervisor node, other VMs stop responding. VM creation job fails. Expected results: New VM is created and other VMs are not affected. Additional info: Two node oVirt cluster running on Xeon(R) CPU E5-2650 0 @ 2.00GHz and 64 GB of RAM. Load at the moment of creating the new VM was less than 1 on both nodes. There are currently 26 VMs running on the two nodes, evenly distributed. The ISO domain is a gluster volume exposed through NFS. The storage domain for the VMs is also a gluster volume. The underlying filesystem for the gluster volumes is ZFS.
maybe this helps: I did not observe this behaviour with vdsm-4.13.3-3.el6.x86_64 on a node with much more ram/cpu and vms. HTH Sven
Tal, can you take a look please?
Tiemen, can you please also include the engine's log?
Created attachment 971760 [details] engine log The button to create the VM was pressed around 2016-12-16 11:17.
*** This bug has been marked as a duplicate of bug 1145241 ***
The cluster didn't have a default disk policy. Once a policy was created, the problem did not occur when adding a VM or creating a disk.