[Users] Host Agent-35 moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : model_Penryn
René Koch
r.koch at ovido.at
Fri Aug 16 13:33:00 UTC 2013
Hi,
Is it working when you set CPU name of your cluster to "Intel Conroe Family"?
Your CPU (the 5110) is quite old (older then Intel Penryn series)...
Regards,
René
-----Original message-----
From: higkoohk<higkoohk at gmail.com>
Sent: Friday 16th August 2013 14:32
To: users at ovirt.org
Subject: [Users] Host Agent-35 moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : model_Penryn
Hello,
Im using oVirt 3.3 beta for gluster, but when I add host into cluster.
Many machine change into non-operational .
Error tips:Host Agent-35 moved to Non-Operational state as host does not meet the clusters minimum CPU level. Missing CPU features : model_Penryn.
This one is OK:
Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm dts tpr_shadow vnmi flexpriority
This one is FAIL:
Intel(R) Xeon(R) CPU 5110 @ 1.60GHz
fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca lahf_lm dts tpr_shadow
Is this mean that failed machine couldnt make vm?
_______________________________________________
Users mailing list
Users at ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
More information about the Users
mailing list