For my cluster, I changed the bios settings to enable the AES instruction on each node,
one at a time, after migrating VMs to other nodes and back when done,
then I was able to upgrade the cluster CPU type to the appropriate westmere when they were all updated.

I'm not sure if something else might need enabled for libvirt and newer CPUs.

As a side note, I did have problems installing Server2016 on a real nehalem CPU VM,
where it would become unresponsive, so the test for newer Nehalem is there for good reason.
The lack of AES instruction test is what's used to give nehalem for the cpu type.

On Fri, Aug 31, 2018 at 10:52 AM carl langlois <crl.langlois@gmail.com> wrote:
most of my cpu are
Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz

so yes it is newer..Not sure how to resolve this.

On Tue, Aug 28, 2018 at 2:29 PM Edward Berger <edwberger@gmail.com> wrote:
Is your CPU really nehalem or is it something newer?
cat /proc/cpuinfo and google the model if you're not sure.

For my E5650 servers I found I had to go into the BIOS and enable some AES instruction
before the oVirt node (actually libvirt) detected the CPU type as newer than Nehalem.


On Tue, Aug 28, 2018 at 10:04 AM carl langlois <crl.langlois@gmail.com> wrote:
Hi all,

I am trying to create a windows VM on my cluster that is set with cpu type to Nehalem. The probleme is that ovirt tell me that the guest os does not support this cpu..

What is the best ways to fix it without impacting my 41 running vms?.

Thanks

Regards


_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IUWS6CERIOTXMVLGA4WIEGHDDPF6YMSI/