Re: [ovirt-users] Missing CPU features

2015-05-20 Thread Bloemen , Jurriën 
Hi,

On 19-05-15 23:18, Rik Theys wrote:
Hi,

On Tue, 19 May 2015, Bloemen, Jurriën wrote:
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 Haswell cpu had a processor feature (hle, TSX-NI) that turned out to
be flaky and Intel disabled this feature with a microcode update.

The cpu's with the updated microcode no longer have the 'hle' feature in
/proc/cpuinfo. oVirt/libvirt does not see the cpu as Haswell as the
required feature is missing.

Upstream libvirt has introduced Haswell-noTSX variants and oVirt will
probably get a new CPU type to match in a future release.

For now I've configured the CPU model as SandyBridge on my Haswell
cpu's.

I filed a bug about this in the oVirt bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1218673

Thanks for clarifying that!

I had to go down to Intel Nehalem Family to get it working.

Regards,

Jurriën


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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Missing CPU features

2015-05-19 Thread Bloemen , Jurriën 
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@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

Re: [ovirt-users] Missing CPU features

2015-05-19 Thread Rik Theys 

Hi,

On Tue, 19 May 2015, Bloemen, Jurriën wrote:

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 Haswell cpu had a processor feature (hle, TSX-NI) that turned out to
be flaky and Intel disabled this feature with a microcode update.

The cpu's with the updated microcode no longer have the 'hle' feature in
/proc/cpuinfo. oVirt/libvirt does not see the cpu as Haswell as the
required feature is missing.

Upstream libvirt has introduced Haswell-noTSX variants and oVirt will
probably get a new CPU type to match in a future release.

For now I've configured the CPU model as SandyBridge on my Haswell
cpu's.

I filed a bug about this in the oVirt bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1218673

Regards,

Rik
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users