2024-07-30T03:27:28.970Z | <Innocent T.> Thanks @John Mulligan for explanation. So what should I do in my case? |
2024-07-30T04:16:52.573Z | <Innocent T.> Btw, it was successful one week ago:: https://files.slack.com/files-pri/T1HG3J90S-F07F03KKJQH/download/screenshot_from_2024-07-30_06-15-49.png |
2024-07-30T13:00:26.412Z | <John Mulligan> That may be due to the release schedule, only the newest releases may have picked up the base image change. Are you running directly on hardware on virtualized? |
2024-07-30T13:09:46.948Z | <Innocent Twagirimana> I am deploying on KVM VMs |
2024-07-30T13:12:10.973Z | <John Mulligan> ok, good. if you were running on bare metal fixing this might be more of an issue. You'll have to switch the CPU type of your vms. I don't know how to do it off the top of my head but you ought to be able to search for it |
2024-07-30T13:12:31.362Z | <John Mulligan> I think its something like "X86-64-v2-AES" |
2024-07-30T13:12:37.798Z | <John Mulligan> but don't take my word for it |
2024-07-30T13:12:57.025Z | <John Mulligan> your vm just needs to support newer instructions than the one you have now |
2024-07-30T13:15:04.014Z | <Innocent Twagirimana> Thanks a lot @John Mulligan. I will check it out. |