[ovirt-users] Re: CPU Compatibility Problem after Upgrading Centos 8 Stream Host

Hi Christoph, The 20200602gitca407c7246bf-5.el8 is the "broken" one [1], try downgrading to the older version (I have 20200602gitca407c7246bf-4.el8_4.1). 1: https://bugzilla.redhat.com/show_bug.cgi?id=1961558#c6 <https://bugzilla.redhat.com/show_bug.cgi?id=1961558#c6> Regards, Lucia On Wed, Jul 28, 2021 at 9:40 AM Michal Skrivanek <michal.skrivanek(a)redhat.com <mailto:michal.skrivanek@redhat.com>> wrote: > On 26. 7. 2021, at 15:06, Christoph Timm <ovirt(a)timmi.org > <mailto:ovirt@timmi.org>> wrote: > > Hi all, > > please note that I also tried to migrate one of my hosts from > CentOS 8 to CentOS Stream 8. > After the reboot I received the following message: > The host CPU does not match the Cluster CPU Type and is running > in a degraded mode. It is missing the following CPU flags: > model_IvyBridge, spec_ctrl. Please update the host CPU microcode > or change the Cluster CPU Type. > > I downgraded the edk2-ovmf package to the following version: > 20200602gitca407c7246bf-5.el8 upgraded. that’s a newer version than the one below > The following version was installed before: > 20210527gite1999b264f1f-1.el8 > > But still the issue is present for me. I’m not aware of any issue with the virt stack packages in Stream, that edk2-ovmf issue has been fixed few weeks back, the new version is the right one, but maybe you have other outdated packages? Also please refresh host capabilities after each such package change. There also could be a microcode change for IvyBridge that you’ve missed (or intel didn’t fix for your particular cpu)…perhaps it’s good enough to just change the Cluster CPU to SandyBridge instead. > > I'm running latest 4.4.7 and my cluster version is 4.6. > > Best regards > Christoph > > > Am 27.05.21 um 16:26 schrieb Gunasekhar Kothapalli via Users: >> The issue was with edk2-ovmf package update, rolling that >> package back and it started recognizing the CPU and host coming >> up... tested on one host and worked fine. >> Thanks & Regards, >> *Gunasekhar Kothapalli* >> >> *From:*Nur Imam Febrianto&lt;nur_imam(a)outlook.com&gt; >> <mailto:nur_imam@outlook.com> >> *Sent:*Wednesday, May 26, 2021 9:54 PM >> *To:*k.gunasekhar@non.keysight.com >> <mailto:k.gunasekhar@non.keysight.com>;users@ovirt.org >> <mailto:users@ovirt.org> >> *Subject:*RE: [ovirt-users] Re: CPU Compatibility Problem after >> Upgrading Centos 8 Stream Host >> >> *CAUTION:*This message originates from an external sender. >> >> Already trying several things, seem kernel update doesn’t make >> this problem happen. Already tried to yum update exclude kernel, >> the issue still happened. >> Thanks. >> Regards, >> Nur Imam Febrianto >> *From:*k.gunasekhar--- via Users <mailto:users@ovirt.org> >> *Sent:*26 May 2021 12:27 >> *To:*users@ovirt.org <mailto:users@ovirt.org> >> *Subject:*[ovirt-users] Re: CPU Compatibility Problem after >> Upgrading Centos 8 Stream Host >> I also end up with the same problem today. How did rollback yum >> i see many yum updates in the yum history. >> >> Here is what the error says. >> >> The host CPU does not match the Cluster CPU Type and is running >> in a degraded mode. It is missing the following CPU flags: >> model_IvyBridge, spec_ctrl. Please update the host CPU microcode >> or change the Cluster CPU Type. >> _______________________________________________ >> Users mailing list --users(a)ovirt.org <mailto:users@ovirt.org> >> To unsubscribe send an email tousers-leave(a)ovirt.org >> <mailto:users-leave@ovirt.org> >> Privacy >> Statement:https://apac01.safelinks.protection.outlook.com/?url=https%3A%2... >> <https://urldefense.com/v3/__https:/apac01.safelinks.protection.outlook.co... >> oVirt Code of >> Conduct:https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%... >> <https://urldefense.com/v3/__https:/apac01.safelinks.protection.outlook.co... >> List >> Archives:https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F... >> <https://urldefense.com/v3/__https:/apac01.safelinks.protection.outlook.co... >> >> _______________________________________________ >> Users mailing list --users(a)ovirt.org <mailto:users@ovirt.org> >> To unsubscribe send an email tousers-leave(a)ovirt.org <mailto:users-leave@ovirt.org> >> Privacy Statement:https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html> >> oVirt Code of Conduct:https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> >> List Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZT... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZTOZO4DO6F6... > > _______________________________________________ > Users mailing list --users(a)ovirt.org <mailto:users@ovirt.org> > To unsubscribe send an email tousers-leave(a)ovirt.org > <mailto:users-leave@ovirt.org> > Privacy Statement:https://www.ovirt.org/privacy-policy.html > <https://www.ovirt.org/privacy-policy.html> > oVirt Code of > Conduct:https://www.ovirt.org/community/about/community-guidelines/ > <https://www.ovirt.org/community/about/community-guidelines/> > List > Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/SH... > <https://lists.ovirt.org/archives/list/users@ovirt.org/message/SHXZBWXQMMF... _______________________________________________ Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/CGDVQ54Q534... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/CGDVQ54Q534...