Hi all and Happy New Year!
I have a ovirt 188.8.131.52 cluster (running with 3 nodes and shared gluster
I have randomly observed that some Windows 10 64bit VMs are reported from
engine dashboard with 100%CPU while when connecting within the VM the CPU
utilization is normal.
Sometimes, when reported with 100% CPU I cannot get a console at VM
(console gives black screen) then I have to force shutdown the VM and start
it up again. The only warning I see is in the qemu logs of the guest
reporting that CPUs not present in any NUMA nodes.
Any ideas how to tackle this?
I'm installing 2-node failover cluster (2 x Xeon servers with local RAID
5 / ext4 for oVirt storage domains).
Now I have a dilemma - use either GlusterFS replica 2 or stick with NFS?
4.2 Engine is running on separate hardware.
Each node have its own storage domain (on internal RAID).
All VMs must be highly available.
One of the VMs is an accounting/stock control system with FireBird SQL
server on CentOS is speed-critical.
No load balancing between nodes necessary. 2nd is just for backup if 1st
for whatever reason goes up in smoke. All VM disks must be replicated to
backup node in near real-time or in worst case each 1 - 2 hour.
GlusterFS solves this issue yet at high performance penalty.
>From what I read here
GlusterFS performance with oVirt is not very good right now because QEMU
uses FUSE instead of libgfapi.
What is optimal way to go on ?
Thanks in advance.
A new oVirt blog post has been published, on how you can customize, in
oVirt 4.2, the host deploy process, by using Ansible. This is a very
powerful feature which allows extending the regular host deploy process
with additional post-deployment tasks, such as package installation,
service configuration, etc.
See https://ovirt.org/blog/2017/12/host-deploy-customization/ for the full