Hi,

I think the edk2-ovmf is still not working in CentOS 8 Stream.
Try to downgrade.

dnf downgrade edk2-ovmf-20200602gitca407c7246bf-4.el8

This solved the problem on my oVirt hosts.

Best regards
Christoph

Am 25.10.21 um 11:59 schrieb [email protected]:
Hi all,

On CentOS 8 Stream I get the following error during "hosted-engine --deploy":

[ INFO ] The host has been set in non_operational status, deployment errors: 
code 156: Host HOST moved to Non-Operational state as host CPU type is not 
supported in this cluster compatibility version or is not supported at all, 
code 519



CPU:

[root@ovirt-test ~]# lscpu
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
CPU(s):              24
On-line CPU(s) list: 0-23
Thread(s) per core:  2
Core(s) per socket:  6
Socket(s):           2
NUMA node(s):        2
Vendor ID:           GenuineIntel
BIOS Vendor ID:      Intel
CPU family:          6
Model:               63
Model name:          Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz


I set up cluster compatibility but it did not solve the problem.
On a normal CentOS 8.4 system, the error is not present.

Does anyone have an idea?
Or have older drivers been removed from the Streram version?

Thanks
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]/message/TT3MNE4VJS2ZMGL5WFQ7UVFSMEMNB22W/
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]/message/2E24TT42BRXYTSYQLSYDS6QSF7N2JB66/

Reply via email to