Property: default route, host - true, DC - false
I have 4 nics.
bond0 = 2 x 10g
eno1 = ovirtmgmt
eno2 = for vm traffic.
eno2 says it's out of sync, hosts network config differs from DC,
default route: host - true, DC - false.
I have tried "sync all networks" but the message still remains
Where can I look to fix the issue?
I am currently building a new virtualization cluster with oVirt, using
AMD EPYC processors (AMD EPYC 7351P). At the moment I'm running oVirt
Node Version 4.2.3 @ CentOS 7.4.1708.
We have the situation that the processor type is recognized as "AMD
Opteron G3". With this type of instruction set the VMs are not able to
do AES in hardware, this results in poor performance in our case.
I found some information that tells me that this problem should be
solved with CentOS 7.5
My actual questions:
- Are there any further information about the AMD EPYC support?
- Any information about an update of the oVirt node to CentOS 7.5?
we upgraded ovirt from version 4.1 to 4.2.6. Rebooted all vms.
We missed two vms that were at Cluster Compatibility Version 3.6.
There was a gluster/network IO problem and vms got paused. We were able
to recover all the other vms from the paused state but we have two vms
that won't run because:
"Cannot run VM. The Custom Compatibility Version of VM VM_NAME (3.6) is
not supported in Data Center compatibility version 4.1."
Can we force the CCV of the paused vm to 4.1?
Dear oVirt Gurus,
Using the oVirt user VM portal seems to not work through the squid proxy setup (configured as per the guide). The page loads and login works fine through the proxy, but the asynchronous requests just hang. I've attached a screenshot, but you can see the "api" endpoint just hanging in a web inspector:
This works fine when not going through the proxy.
Is there a way to force noVNC HTML as the console mode through the web-ui, or at least have it as an option if not default?
The console seems not to work when logged in with a base 'user role'.
Research Computing Core
Wellcome Trust Centre for Human Genetics
University of Oxford
I recently deployed oVirt in some hosts to evaluate it as one of my main virtualization tool. I like it a lot, but I don't know if this behaviour is normal: I just configured my iSCSI network against a IBM V7000, and from that point on, the host with the role "SPM" continuosly is reading from storage at about 7 or 8 Mbps. I don't know what it i doing, due to no storage domains are still created. How can I know what it is doing ?
I had similar problem in the past with ESXi 6.0 U2 host where I defined a
VM and used it as oVirt node for nested virtualization. If I run on this
"virtual" node an L2 VM all went well until custom emulated machine value
was at "pc-i440fx-rhel7.2.0".
At some point the default became 7.3 and the L2 VM was not able to boot any
more: it remained in blank screen at boot.
The same up to now in 184.108.40.206 where this default seems to be 7.5
I'm having same problem in a mini lab on a nuc6 where I have ESXi 6.7
installed and try to setup an hosted engine environment.
This problem prevents me to configure the hosted engine because the L2 VM
that should be the hosted engine freezes (?) during its first startup and I
see indeed that the qemu-kvm process is started with option "-machine
Being stated that I'm in an unsupported configuration, I would like to
understand if I can correct in some point and proceed.
So some questions:
1) How can I understand what is the difference between running qemu-kvm
with "-machine pc-i440fx-rhel7.2.0" ad "-machine pc-i440fx-rhel7.5.0" so
that I can then dig with ESXi parameters eventually to tune the settings of
its VM that becomes my oVirt hypervisor?
2) Do I have any chance to configure my oVirt node so that when it runs the
hosted-engine deploy it runs the engine VM with 7.2 parameter? Any conf
file on host where I can somehow force 7.2 compatibility or set it as
3) during gluster base hosted-engine deployment at first "local" startup
how can I connect to the console of the hosted engine VM and see where it
Thanks in advance,
following this reference guide:
after having run with success the gdeploy based gluster setup, there is
Setting up Hosted Engine
Use the Ansible based installation flow of Hosted Engine to set up oVirt
within a virtual machine. The storage details should be provided as type:
glusterfs and connection path as: <hostname>:/engine (Replace hostname with
address of host on which installation is carried out)
What does exactly mean "Use the Ansible based instalation" ? Does it mean
using cockpit web ui? In this casae I suppose I have to choose:
Deploy oVirt hosted engine on storage that has already been provisioned