Il 22/Gen/2017 08:26, "久保田" <kubota(a)ops.dti.ne.jp&gt; ha scritto: Hello, I am a user of oVirt Engine 3.6.2.6-1.el7.centos . Ovirt 3.6 still has a bug that classifies IvyBridge CPU(i7-3770K) as Westmere and clusters it. Is this bug fixed in ovirt 4.x? Letting virtualization team to answer this and Is there a prospect of correcting this bug in ovirt 3.6? No, 3.6 reached end of life when 4.0 has been released. Please note that 4.1 will arrive soon so the upcoming 4.0.7 will be the last 4.0 release. I would suggest to upgrade. When IvyBridge is added to cluster of SandyBridge, an error of CPU_TYPE_INCONPATIBLE_WITH_CLUSTER appears. engine.log 2017-01-22 15:25:00,004 INFO [org.ovirt.engine.core.bll.AutoRecoveryManager] (DefaultQuartzScheduler_Worker-11) [] Autorecovering 1 hosts 2017-01-22 15:25:00,004 INFO [org.ovirt.engine.core.bll.AutoRecoveryManager] (DefaultQuartzScheduler_Worker-11) [] Autorecovering hosts id: 726249f0-fa7d-496b-b86b-432e8909a2f3 , name :XXX 2017-01-22 15:25:00,005 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (DefaultQuartzScheduler_Worker-11) [33e5f398] Lock Acquired to object 'EngineLock:{exclusiveLocks='[726249f0-fa7d-496b-b86b-432e8909a2f3=<VDS, ACTION_TYPE_FAILE D_OBJECT_LOCKED>]', sharedLocks='null'}' 2017-01-22 15:25:00,006 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (DefaultQuartzScheduler_Worker-11) [33e5f398] Running command: ActivateVdsCommand internal: true. Entities affected : ID: 726249f0-fa7d-496b-b86b-432e8909a2f3 Type: VDSAction group MANIPULATE_HOST with role type ADMIN 2017-01-22 15:25:00,006 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (DefaultQuartzScheduler_Worker-11) [33e5f398] Before acquiring lock in order to prevent monitoring for host 'XXX' from data-center 'Default' 2017-01-22 15:25:00,006 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (DefaultQuartzScheduler_Worker-11) [33e5f398] Lock acquired, from now a monitoring of host will be skipped for host 'XXX' from data-center 'Default' 2017-01-22 15:25:00,014 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler_Worker-11) [33e5f398] START, SetVdsStatusVDSCommand(HostName = green.team-boss.com, SetVdsStatusVDSCommandParameters:{runAsync ='true', hostId='726249f0-fa7d-496b-b86b-432e8909a2f3', status='Unassigned', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 2284a60f 2017-01-22 15:25:00,016 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler_Worker-11) [33e5f398] FINISH, SetVdsStatusVDSCommand, log id: 2284a60f 2017-01-22 15:25:00,024 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (DefaultQuartzScheduler_Worker-11) [] Activate finished. Lock released. Monitoring can run now for host 'XXX' from data-center 'Default' 2017-01-22 15:25:00,024 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (DefaultQuartzScheduler_Worker-11) [] Lock freed to object 'EngineLock:{exclusiveLocks='[726249f0-fa7d-496b-b86b-432e8909a2f3=<VDS, ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}' 2017-01-22 15:25:02,888 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler_Worker-60) [] START, GetHardwareInfoVDSCommand(HostName = XXX, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',hostId= '726249f0-fa7d-496b-b86b-432e8909a2f3',vds='Host[XXX, 726249f0-fa7d-496b-b86b-432e8909a2f3]'}),log id: 1927e79c 2017-01-22 15:25:02,892 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler_Worker-60) [] FINISH, GetHardwareInfoVDSCommand, log id: 1927e79c 2017-01-22 15:25:02,894 WARN [org.ovirt.engine.core.vdsbroker.VdsManager] (DefaultQuartzScheduler_Worker-60) [] Host 'XXX'is running with SELinux in 'DISABLED' mode 2017-01-22 15:25:02,911 INFO [org.ovirt.engine.core.bll. HandleVdsCpuFlagsOrClusterChangedCommand] (DefaultQuartzScheduler_Worker-60) [1afd70be] Running command: HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected : ID: 726249f0-fa7d-496b-b86b-432e8909a2f3 Type: VDS 2017-01-22 15:25:02,925 INFO [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (DefaultQuartzScheduler_Worker-60) [65c681a5] Running command: SetNonOperationalVdsCommand internal: true. Entities affected : ID: 726249f0-fa7d-496b-b86b-432e8909a2f3 Type: VDS 2017-01-22 15:25:02,926 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler_Worker-60) [65c681a5] START, SetVdsStatusVDSCommand(HostName = XXX, SetVdsStatusVDSCommandParameters:{runAsync='true',hostId=' 726249f0-fa7d-496b-b86b-432e8909a2f3', status='NonOperational', nonOperationalReason='CPU_TYPE_INCOMPATIBLE_WITH_ CLUSTER',stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 4c07f536 2017-01-22 15:25:02,930 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler_Worker-60) [65c681a5] FINISH, SetVdsStatusVDSCommand, log id: 4c07f536 2017-01-22 15:25:02,936 INFO [org.ovirt.engine.core.dal. dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-60) [65c681a5] Correlation ID: 65c681a5, Job ID: ec912b06-7fd0-4497-9f1a-247d0d1d1fea, Call Stack: null, Custom Event ID: -1, Message: Host XXX moved to Non-Operational state. 2017-01-22 15:25:02,943 WARN [org.ovirt.engine.core.dal. dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-60) [65c681a5] Correlation ID: 1afd70be, Call Stack: null, Custom Event ID: -1, Message: Host green.team-boss.com moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : model_SandyBridge 2017-01-22 15:25:02,947 INFO [org.ovirt.engine.core.dal. dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-60) [65c681a5] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Status of host XXX was set to NonOperational. 2017-01-22 15:25:02,955 INFO [org.ovirt.engine.core.bll.HandleVdsVersionCommand] (DefaultQuartzScheduler_Worker-60) [1bd90240] Running command: HandleVdsVersionCommand internal: true. Entities affected : ID: 726249f0-fa7d-496b-b86b-432e8909a2f3 Type: VDS 2017-01-22 15:25:02,957 INFO [org.ovirt.engine.core.vdsbroker.HostMonitoring] (DefaultQuartzScheduler_Worker-60) [1bd90240] Host 'XXX'(726249f0-fa7d-496b-b86b-432e8909a2f3) is already in NonOperational status for reason 'CPU_TYPE_INCOMPATIBLE_WITH_CLUSTER'. SetNonOperationalVds command is skipped. my server # cat /proc/cpuinfo|head processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz stepping : 9 microcode : 0x1c cpu MHz : 1600.566 cache size : 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : 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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt bogomips : 7000.00 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: : : #uname -a Linux XXX 3.10.0-514.6.1.el7.x86_64 #1 SMP Wed Jan 18 13:06:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # rpm -q ovirt-engine ovirt-engine-3.6.2.6-1.el7.centos.noarch # rpm -q vdsm vdsm-4.17.32-1.el7.noarch # libvirtd --version libvirtd (libvirt) 2.0.0 thx -kubota _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users