[ovirt-users] Missing CPU features

Bloemen, Jurriën Jurrien.Bloemen at dmc.amcnetworks.com
Tue May 19 17:08:47 UTC 2015


Hi all,

I try to add a new host to a new cluster but I get this message:

Host <hostname> moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : model_Haswell

The engine.log shows:


2015-05-19 13:54:09,843 INFO  [org.ovirt.engine.core.bll.ActivateVdsCommand] (ajp--127.0.0.1-8702-2) [a4e6c90] Lock Acquired to object EngineLock [exclusiveLocks= key: 1ac98a04-41ed-40b7-8f02-e1b9cbbc5480 value: VDS

, sharedLocks= ]

2015-05-19 13:54:09,868 INFO  [org.ovirt.engine.core.bll.ActivateVdsCommand] (org.ovirt.thread.pool-8-thread-14) [a4e6c90] Running command: ActivateVdsCommand internal: false. Entities affected :  ID: 1ac98a04-41ed-40b7-8f02-e1b9cbbc5480 Type: VDSAction group MANIPULATE_HOST with role type ADMIN

2015-05-19 13:54:09,869 INFO  [org.ovirt.engine.core.bll.ActivateVdsCommand] (org.ovirt.thread.pool-8-thread-14) [a4e6c90] Before acquiring lock in order to prevent monitoring for host <hostname> from data-center DMC

2015-05-19 13:54:09,870 INFO  [org.ovirt.engine.core.bll.ActivateVdsCommand] (org.ovirt.thread.pool-8-thread-14) [a4e6c90] Lock acquired, from now a monitoring of host will be skipped for host <hostname> from data-center DMC

2015-05-19 13:54:09,885 INFO  [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (org.ovirt.thread.pool-8-thread-14) [a4e6c90] START, SetVdsStatusVDSCommand(HostName = <hostname>, HostId = 1ac98a04-41ed-40b7-8f02-e1b9cbbc5480, status=Unassigned, nonOperationalReason=NONE, stopSpmFailureLogged=false), log id: 3ec2e03a

2015-05-19 13:54:09,890 INFO  [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (org.ovirt.thread.pool-8-thread-14) [a4e6c90] FINISH, SetVdsStatusVDSCommand, log id: 3ec2e03a

2015-05-19 13:54:09,920 INFO  [org.ovirt.engine.core.bll.ActivateVdsCommand] (org.ovirt.thread.pool-8-thread-14) [a4e6c90] Activate finished. Lock released. Monitoring can run now for host <hostname> from data-center DMC

2015-05-19 13:54:09,923 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-14) [a4e6c90] Correlation ID: a4e6c90, Job ID: 2bb9b203-0d51-4532-9b83-d261d805a19d, Call Stack: null, Custom Event ID: -1, Message: Host <hostname> was activated by admin at internal.

2015-05-19 13:54:09,926 INFO  [org.ovirt.engine.core.bll.ActivateVdsCommand] (org.ovirt.thread.pool-8-thread-14) [a4e6c90] Lock freed to object EngineLock [exclusiveLocks= key: 1ac98a04-41ed-40b7-8f02-e1b9cbbc5480 value: VDS

, sharedLocks= ]

2015-05-19 13:54:11,706 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler_Worker-94) [3f613a08] START, GetHardwareInfoVDSCommand(HostName = <hostname>, HostId = 1ac98a04-41ed-40b7-8f02-e1b9cbbc5480, vds=Host[<hostname>,1ac98a04-41ed-40b7-8f02-e1b9cbbc5480]), log id: 32ca13a8

2015-05-19 13:54:11,712 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler_Worker-94) [3f613a08] FINISH, GetHardwareInfoVDSCommand, log id: 32ca13a8

2015-05-19 13:54:11,726 WARN  [org.ovirt.engine.core.vdsbroker.VdsManager] (DefaultQuartzScheduler_Worker-94) [3f613a08] Host <hostname> is running with disabled SELinux.

2015-05-19 13:54:11,748 INFO  [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] (DefaultQuartzScheduler_Worker-94) [1f024fdb] Running command: HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected :  ID: 1ac98a04-41ed-40b7-8f02-e1b9cbbc5480 Type: VDS

2015-05-19 13:54:11,772 INFO  [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (DefaultQuartzScheduler_Worker-94) [3ccdb219] Running command: SetNonOperationalVdsCommand internal: true. Entities affected :  ID: 1ac98a04-41ed-40b7-8f02-e1b9cbbc5480 Type: VDS

2015-05-19 13:54:11,786 INFO  [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler_Worker-94) [3ccdb219] START, SetVdsStatusVDSCommand(HostName = <hostname>  HostId = 1ac98a04-41ed-40b7-8f02-e1b9cbbc5480, status=NonOperational, nonOperationalReason=CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER, stopSpmFailureLogged=false), log id: 24054dd4

2015-05-19 13:54:11,789 INFO  [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler_Worker-94) [3ccdb219] FINISH, SetVdsStatusVDSCommand, log id: 24054dd4

2015-05-19 13:54:11,796 WARN  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-94) [3ccdb219] Correlation ID: 1f024fdb, Call Stack: null, Custom Event ID: -1, Message: Host <hostname> moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : model_Haswell

2015-05-19 13:54:11,813 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-94) [3ccdb219] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Status of host <hostname> was set to NonOperational.

2015-05-19 13:54:11,839 INFO  [org.ovirt.engine.core.bll.HandleVdsVersionCommand] (DefaultQuartzScheduler_Worker-94) [4bb0a00] Running command: HandleVdsVersionCommand internal: true. Entities affected :  ID: 1ac98a04-41ed-40b7-8f02-e1b9cbbc5480 Type: VDS

2015-05-19 13:54:11,841 INFO  [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-94) [4bb0a00] Host 1ac98a04-41ed-40b7-8f02-e1b9cbbc5480 : <hostname> is already in NonOperational status for reason CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER. SetNonOperationalVds command is skipped.

It says that the host has not meet the minimum CPU level. “lscpu" has the following output:


# lscpu

Architecture:          x86_64

CPU op-mode(s):        32-bit, 64-bit

Byte Order:            Little Endian

CPU(s):                56

On-line CPU(s) list:   0-55

Thread(s) per core:    2

Core(s) per socket:    14

Socket(s):             2

NUMA node(s):          2

Vendor ID:             GenuineIntel

CPU family:            6

Model:                 63

Model name:            Intel(R) Xeon(R) CPU E5-2697 v3 @ 2.60GHz

Stepping:              2

CPU MHz:               1957.007

BogoMIPS:              5206.30

Virtualization:        VT-x

L1d cache:             32K

L1i cache:             32K

L2 cache:              256K

L3 cache:              35840K

NUMA node0 CPU(s):     0-13,28-41

NUMA node1 CPU(s):     14-27,42-55

This model is a haswell: http://ark.intel.com/products/81059/Intel-Xeon-Processor-E5-2697-v3-35M-Cache-2_60-Ghz<http://ark.intel.com/products/81059/Intel-Xeon-Processor-E5-2697-v3-35M-Cache-2_60-GHz> and http://ark.intel.com/products/codename/42174/Haswell#@All

Is this a bug? Should I make a bug report at bugzilla for this? Or am I missing something?

Kind regards,

Jurriën Bloemen
This message (including any attachments) may contain information that is privileged or confidential. If you are not the intended recipient, please notify the sender and delete this email immediately from your systems and destroy all copies of it. You may not, directly or indirectly, use, disclose, distribute, print or copy this email or any part of it if you are not the intended recipient
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20150519/b44a490e/attachment-0001.html>


More information about the Users mailing list