On Tue, Feb 1, 2022 at 8:27 PM Richard W.M. Jones <rjones(a)redhat.com> wrote:
2022-02-01 19:05:01,952Z ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19)
[330886aa] EVENT_ID: CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION(156),
Host ovirt4410-host moved to Non-Operational state as host CPU type is not
supported in this cluster compatibility version or is not supported at all
The host is a nested VM running on old hardware. I don't care that
it's not supported - this is just for testing copying and it'll
literally never even need to run a VM.
Is there a way to ignore this and continue?
Hi,
You need to create a custom DC and a cluster with lower compatibility level
to be able to use older CPUs.
You can take a look at supported CPUs for each cluster level using
ServerCPUList config option:
https://github.com/oVirt/ovirt-engine/blob/master/packaging/dbscripts/upg...
What is your hypervisor CPU?
Regards,
Martin
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages.
http://libguestfs.org
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NOLWZUDPZME...
--
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.