Hello,
I ran into a nasty problem today when creating a new, cloned VM from a
template (one virtual 20 GBdisk) on our two-node oVirt cluster: on the
node where I started a VM creation job, load skyrocketed and some VMs
stopped responding until and after the job failed. Everything recovered
without intervention, but this obviously shouldn't happen. I have
attached the relevant vdsm log file. The button to create the VM was
pressed around 11:17, the first error in the vdsm log is at 11:23:58.
The ISO domain is a gluster volume exposed via NFS, the storage domain
for the VM's is also a gluster volume. The underlying filesystem is ZFS.
The hypervisor nodes are full CentOS 6 installs.
I'm guessing the 'no free file handlers in pool' in the vdsm log file is
key here. What can I do to prevent this from happening again? Apart from
not creating new VMs of course :)
Tiemen