You might also want to watch out for hostname-3.20-7.el8.x86_64. It's
causing loops in systemd's service start ordering which get broken by
randomly not starting a service. Often this service turns out to be
NetworkManager :(
On 5/25/2021 1:38 PM, [email protected] wrote:
Thanks Jeff Bailey,
The issue was with edk2-ovmf, rolling that package back and it started
recognizing the CPU correctly.
_______________________________________________
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/6J2WGNN3XPPH6ALLNPEE72J5JLUVESSH/
_______________________________________________
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/LZ2Q5HDZQTD6NQWPLGAJEE7BEKY5SPBW/
