On 10/15/2014 09:42 AM, Fawzy Ibrhim wrote:
Dear All;
I have DELL PowerEdge 6850 with two Intel(R) Xeon(TM) CPU 2.66GHz.
The CPU has the below flags which does not include AES flag:-
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 lm constant_tsc pebs bts pni dtes64
monitor ds_cpl vmx est cid cx16 xtpr lahf_lm tpr_shadow
I have installed Centos 6.5 64bit on it and I need to add it to the cluster Intel Nehalem
Family.
oVirt Engine Version is 3.4.3-1.el6.
Cluster Compatibility Version is: 3.4
CPU type is: Intel Nehalm Family
The installation started normally and stopped with error:-
"Host iScsi moved to Non-Operational state as host CPU type is not supported in this
cluster compatibility version or is not supported at all"
# virsh -r capabilities
<capabilities>
<host>
<uuid>2bbed3bb-c962-4ffc-8fbc-20c73663137c</uuid>
<cpu>
<arch>x86_64</arch>
<model>cpu64-rhel6</model>
<vendor>Intel</vendor>
<topology sockets='2' cores='2' threads='2'/>
<feature name='xtpr'/>
<feature name='cid'/>
<feature name='est'/>
<feature name='vmx'/>
<feature name='ds_cpl'/>
<feature name='monitor'/>
<feature name='dtes64'/>
<feature name='pbe'/>
<feature name='tm'/>
<feature name='ht'/>
<feature name='ss'/>
<feature name='acpi'/>
<feature name='ds'/>
<feature name='vme'/>
</cpu>
<power_management>
<suspend_disk/>
</power_management>
<migration_features>
<live/>
<uri_transports>
<uri_transport>tcp</uri_transport>
</uri_transports>
</migration_features>
<topology>
<cells num='1'>
<cell id='0'>
<cpus num='8'>
<cpu id='0' socket_id='2' core_id='0'
siblings='0,4'/>
<cpu id='1' socket_id='3' core_id='0'
siblings='1,5'/>
<cpu id='2' socket_id='2' core_id='1'
siblings='2,6'/>
<cpu id='3' socket_id='3' core_id='1'
siblings='3,7'/>
<cpu id='4' socket_id='2' core_id='0'
siblings='0,4'/>
<cpu id='5' socket_id='3' core_id='0'
siblings='1,5'/>
<cpu id='6' socket_id='2' core_id='1'
siblings='2,6'/>
<cpu id='7' socket_id='3' core_id='1'
siblings='3,7'/>
</cpus>
</cell>
</cells>
</topology>
<secmodel>
<model>selinux</model>
<doi>0</doi>
</secmodel>
<secmodel>
<model>dac</model>
<doi>0</doi>
</secmodel>
</host>
<guest>
<os_type>hvm</os_type>
<arch name='i686'>
<wordsize>32</wordsize>
<emulator>/usr/libexec/qemu-kvm</emulator>
<machine>rhel6.5.0</machine>
<machine canonical='rhel6.5.0'>pc</machine>
<machine>rhel6.4.0</machine>
<machine>rhel6.3.0</machine>
<machine>rhel6.2.0</machine>
<machine>rhel6.1.0</machine>
<machine>rhel6.0.0</machine>
<machine>rhel5.5.0</machine>
<machine>rhel5.4.4</machine>
<machine>rhel5.4.0</machine>
<domain type='qemu'>
</domain>
<domain type='kvm'>
<emulator>/usr/libexec/qemu-kvm</emulator>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
<acpi default='on' toggle='yes'/>
<apic default='on' toggle='no'/>
<pae/>
<nonpae/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='x86_64'>
<wordsize>64</wordsize>
<emulator>/usr/libexec/qemu-kvm</emulator>
<machine>rhel6.5.0</machine>
<machine canonical='rhel6.5.0'>pc</machine>
<machine>rhel6.4.0</machine>
<machine>rhel6.3.0</machine>
<machine>rhel6.2.0</machine>
<machine>rhel6.1.0</machine>
<machine>rhel6.0.0</machine>
<machine>rhel5.5.0</machine>
<machine>rhel5.4.4</machine>
<machine>rhel5.4.0</machine>
<domain type='qemu'>
</domain>
<domain type='kvm'>
<emulator>/usr/libexec/qemu-kvm</emulator>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
<acpi default='on' toggle='yes'/>
<apic default='on' toggle='no'/>
</features>
</guest>
</capabilities>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
i wasn't aware there is a nehalem without AES.
this causes libvirt to not identify/report any identified cpu, rather a
generic one (cpu64-rhel6).
is this what you also get from 'vdsClient -s 0 getVdsCaps | grep cpu' ?