Re: [Users] ovirt reporting wrong cpu family

2013-03-06 Thread Martin Kletzander 
On 03/02/2013 05:07 PM, Adrian Gibanel wrote:
> Sorry for the late answer. I was kind of busy. I reply inline below.
> 
> - Mensaje original - 
> 
>> De: "Martin Kletzander" 
>> Para: "Itamar Heim" 
>> CC: "Adrian Gibanel" , users@ovirt.org, "Jithin
>> Raju" 
>> Enviados: Martes, 19 de Febrero 2013 15:11:05
>> Asunto: Re: [Users] ovirt reporting wrong cpu family
> 
>> On 02/16/2013 10:02 PM, Itamar Heim wrote:
>>> Adrian - can you later please wikify this recurring question?
>>>
> 
>> If this is related to libvirt detecting the wrong CPU, we have a short
>> wiki page [1] for that either, you can link to that in yours (or maybe
>> it'll help you write it).
> Thank you. I'll take a look. More below.
> 
>> [...]
>>>> On 16/02/2013 18:56, Adrian Gibanel wrote:
>>>>> I happen to have the same problem in oVirt 3.1 on Fedora.
>>>>> Any workaround?
>>>>>
>>>>> $ sudo vdsClient -s 0 getVdsCaps | grep -i flags ; echo -e -n "\n" ;cat
>>>>> /proc/cpuinfo | grep "model name" | head -n 1
>>>>> cpuFlags =
>>>>> 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,xsave,avx,lahf_lm,arat,epb,xsaveopt,pln,pts,dtherm,tpr_shadow,vnmi,flexpriority,ept,vpid,model_coreduo,model_Conroe
>>>>>
> 
>> At first, let me say that this is very weird CPU detection as according
>> to these flags, the processor described in here should be "Nehalem".
>> Could you try running 'virsh -r capabilities' on the host to check what
>> libvirt reports?
> 
> Here you are:
> 
> 
> 
>   
> c090c38a-5202-e211-bbb4-4c72b97c99ed
> 
>   x86_64
>   Nehalem

And it is really Nehalem, so my manual cpu flags hunt was right.  But
this means there is a problem lower than in libvirt.  I'm afraid that
the sentence about the BIOS/UEFI not being your case which I wrote in
http://lists.ovirt.org/pipermail/users/2013-March/012908.html is no
longer true for this server.  The only solution I can come up with right
now is what already once helped for resolving Nehalem-related detection
and it's the link from the wiki page (that was outdated, so I updated it):

http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=TOOL-ASU

but that's applicable for BladeCenters only.  If this is not suitable
for you, I'm afraid you'll have to contact your HW vendor in order to
resolve the CPU issue.

Hope it helps and please keep me posted, I'd like to summarize all the
related info on one place and resolve related bugs (if there are any) so
similar issues go away, because they seem to be appearing more and more
frequently.

Have a nice day,
Martin

[...]
> 
> 
> 
>> There might be a possible workaround if you want your CPU to be
>> identified as different model, most probably by editing
>> '/usr/share/libvirt/cpu_map.xml', but that should be omitted since it
>> may lead to problems.
> Non applicable workaround then. I should have expected it. Ok, I prefer not 
> having additional problems.
> 
>> [...]
>>>>> model name : Intel(R) Core(TM) i3-2130 CPU @ 3.40GHz
>>>>>
> 
>> And as I see the CPU is SandyBridge, so this should be solved properly
>> (probably a bug somewhere or very low-level misconfiguration). Check
>> [1], maybe some features can get enabled.
> 
> The machine is in a datacentre so I doubt I can change any BIOS or UEFI 
> settings.
> 
>> Martin
> 
>> [1]
>> http://wiki.libvirt.org/page/Libvirt_identifies_host_processor_as_a_different_model_from_the_hardware_documentation
> 

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

Re: [Users] ovirt reporting wrong cpu family (2nd server)

2013-03-06 Thread Martin Kletzander 
On 03/02/2013 08:46 PM, Itamar Heim wrote:
> On 02/03/2013 18:39, Adrian Gibanel wrote:
>> I've read again the wiki page and as you might ask for it here's the
>> cpuinfo flags output:
>>
>> 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
>> pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
>> xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
>> ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2
>> x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat epb
>> xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid
>>
>> If we check the mentioned cpu_max.xml file we find :
>>
>>  
>>
>>
>>
>>
>>
>>
>>
>>  
>>
>> So I suppose that pclmuldq is expected in the flags but it's not
>> there. Isn't it?
> 
> well, it kind of looks like a bug, since you have pclmulqdq (additional
> 'q' in the middle').
> martin?
> 

Hi, this is expected.  While working on these features, the names
sometime change and in this case pclmulqdq is the same as pclmuldq.
Mostly it is referred to it as pclmulqdq, but when this feature was
added in qemu, the name was without the 'q', alias was added later on:

http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg02376.html

>> # virsh -r capabilities
>> 
>> 
>> 
>>   
>> ----002590a41888
>> 
>>   x86_64
>>   SandyBridge

But from this output (which I pasted from the older mail, so the
indentation may not fit), I see libvirt is detecting the CPU perfectly
in this case.

>>
>> So I need to add my specific model at hand and trying to infer which
>> are the specific flags for it?
>> Or maybe that needs something more to be hacked in the libvirt code...
>> and thus I should wait for libvirt people to add it? Well, I mean,
>> going to their ML and asking there?
>>
>> Or isn't there any hope for my particular sandbridge cpu?
>>

There definitely is, as mentioned above.  There almost always is, I
remember only one CPU without a chance and that was because the HW
itself really didn't know the function.  Unfortunately, sometimes
(HW-dependant) it really has to be set in BIOS/UEFI.  For some changes
there are utilities, so you don't have to have physical access to the
machine, but as seen from the capabilities, this is not your case.

>> Thank you.
>>
>> - Mensaje original -
>>
>>> De: "Adrian Gibanel" 
>>> Para: users@ovirt.org
>>> CC: "Itamar Heim" , "Jithin Raju"
>>> ,
>>> "Martin Kletzander" 
>>> Enviados: Sábado, 2 de Marzo 2013 17:21:43
>>> Asunto: Re: [Users] ovirt reporting wrong cpu family (2nd server)
>>
>>> This is another server which I have also problems with. I cannot select
>>> SandyBridge as the cpu type.
>>> Still oVirt 3.1 in Fedora 17.
>>
>>> * Tecnology : Sandy Bridge E
>>> * CPU : Intel Xeon E5-1620
>>> * Cores / Threads : 4 / 8
>>> * Frecuency : 3.6GHz / 3.8GHz Turbo Boost
>>
>>> #cpuinfo:
>>> Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz
>>
>>> # rpm -qa | grep -E 'vdsm|libvirt' | sort
>>> libvirt-0.9.11.9-1.fc17.x86_64
>>> libvirt-client-0.9.11.9-1.fc17.x86_64
>>> libvirt-daemon-0.9.11.9-1.fc17.x86_64
>>> libvirt-daemon-config-network-0.9.11.9-1.fc17.x86_64
>>> libvirt-daemon-config-nwfilter-0.9.11.9-1.fc17.x86_64
>>> libvirt-lock-sanlock-0.9.11.9-1.fc17.x86_64
>>> libvirt-python-0.9.11.9-1.fc17.x86_64
>>> vdsm-4.10.0-10.fc17.x86_64
>>> vdsm-cli-4.10.0-10.fc17.noarch
>>> vdsm-python-4.10.0-10.fc17.x86_64
>>> vdsm-xmlrpc-4.10.0-10.fc17.noarch
>>
>>> # virsh -r capabilities
>>
>>> 
>>> [...]
>>
>>> - Mensaje original -
>>
>>>> At first, let me say that this is very weird CPU detection as according
>>>> to these flags, the processor described in here should be "Nehalem".
>>>> Could you try running 'virsh -r capabilities' on the host to check what
>>>> libvirt reports?
>>
>>> -- 
> 

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

Re: [Users] ovirt reporting wrong cpu family (2nd server)

2013-03-02 Thread Itamar Heim 

On 02/03/2013 18:39, Adrian Gibanel wrote:

I've read again the wiki page and as you might ask for it here's the cpuinfo 
flags output:

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 pdpe1gb rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 
cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes 
xsave avx lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi 
flexpriority ept vpid

If we check the mentioned cpu_max.xml file we find :

 
   
   
   
   
   
   
   
 

So I suppose that pclmuldq is expected in the flags but it's not there. Isn't 
it?


well, it kind of looks like a bug, since you have pclmulqdq (additional 
'q' in the middle').

martin?



So I need to add my specific model at hand and trying to infer which are the 
specific flags for it?
Or maybe that needs something more to be hacked in the libvirt code... and thus 
I should wait for libvirt people to add it? Well, I mean, going to their ML and 
asking there?

Or isn't there any hope for my particular sandbridge cpu?

Thank you.

- Mensaje original -


De: "Adrian Gibanel" 
Para: users@ovirt.org
CC: "Itamar Heim" , "Jithin Raju" ,
"Martin Kletzander" 
Enviados: Sábado, 2 de Marzo 2013 17:21:43
Asunto: Re: [Users] ovirt reporting wrong cpu family (2nd server)



This is another server which I have also problems with. I cannot select
SandyBridge as the cpu type.
Still oVirt 3.1 in Fedora 17.



* Tecnology : Sandy Bridge E
* CPU : Intel Xeon E5-1620
* Cores / Threads : 4 / 8
* Frecuency : 3.6GHz / 3.8GHz Turbo Boost



#cpuinfo:
Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz



# rpm -qa | grep -E 'vdsm|libvirt' | sort
libvirt-0.9.11.9-1.fc17.x86_64
libvirt-client-0.9.11.9-1.fc17.x86_64
libvirt-daemon-0.9.11.9-1.fc17.x86_64
libvirt-daemon-config-network-0.9.11.9-1.fc17.x86_64
libvirt-daemon-config-nwfilter-0.9.11.9-1.fc17.x86_64
libvirt-lock-sanlock-0.9.11.9-1.fc17.x86_64
libvirt-python-0.9.11.9-1.fc17.x86_64
vdsm-4.10.0-10.fc17.x86_64
vdsm-cli-4.10.0-10.fc17.noarch
vdsm-python-4.10.0-10.fc17.x86_64
vdsm-xmlrpc-4.10.0-10.fc17.noarch



# virsh -r capabilities




[...]



- Mensaje original -



At first, let me say that this is very weird CPU detection as according
to these flags, the processor described in here should be "Nehalem".
Could you try running 'virsh -r capabilities' on the host to check what
libvirt reports?



--


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

Re: [Users] ovirt reporting wrong cpu family (2nd server)

2013-03-02 Thread Adrian Gibanel 
I've read again the wiki page and as you might ask for it here's the cpuinfo 
flags output:

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 pdpe1gb rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 
cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes 
xsave avx lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi 
flexpriority ept vpid

If we check the mentioned cpu_max.xml file we find :


  
  
  
  
  
  
  


So I suppose that pclmuldq is expected in the flags but it's not there. Isn't 
it?

So I need to add my specific model at hand and trying to infer which are the 
specific flags for it?
Or maybe that needs something more to be hacked in the libvirt code... and thus 
I should wait for libvirt people to add it? Well, I mean, going to their ML and 
asking there?

Or isn't there any hope for my particular sandbridge cpu?

Thank you.

- Mensaje original - 

> De: "Adrian Gibanel" 
> Para: users@ovirt.org
> CC: "Itamar Heim" , "Jithin Raju" ,
> "Martin Kletzander" 
> Enviados: Sábado, 2 de Marzo 2013 17:21:43
> Asunto: Re: [Users] ovirt reporting wrong cpu family (2nd server)

> This is another server which I have also problems with. I cannot select
> SandyBridge as the cpu type.
> Still oVirt 3.1 in Fedora 17.

> * Tecnology : Sandy Bridge E
> * CPU : Intel Xeon E5-1620
> * Cores / Threads : 4 / 8
> * Frecuency : 3.6GHz / 3.8GHz Turbo Boost

> #cpuinfo:
> Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz

> # rpm -qa | grep -E 'vdsm|libvirt' | sort
> libvirt-0.9.11.9-1.fc17.x86_64
> libvirt-client-0.9.11.9-1.fc17.x86_64
> libvirt-daemon-0.9.11.9-1.fc17.x86_64
> libvirt-daemon-config-network-0.9.11.9-1.fc17.x86_64
> libvirt-daemon-config-nwfilter-0.9.11.9-1.fc17.x86_64
> libvirt-lock-sanlock-0.9.11.9-1.fc17.x86_64
> libvirt-python-0.9.11.9-1.fc17.x86_64
> vdsm-4.10.0-10.fc17.x86_64
> vdsm-cli-4.10.0-10.fc17.noarch
> vdsm-python-4.10.0-10.fc17.x86_64
> vdsm-xmlrpc-4.10.0-10.fc17.noarch

> # virsh -r capabilities

> 
> [...]

> - Mensaje original -

> > At first, let me say that this is very weird CPU detection as according
> > to these flags, the processor described in here should be "Nehalem".
> > Could you try running 'virsh -r capabilities' on the host to check what
> > libvirt reports?

> --
-- 

-- 
Adrián Gibanel 
I.T. Manager 

+34 675 683 301 
www.btactic.com 



Ens podeu seguir a/Nos podeis seguir en: 

i 

Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és 
cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El 
medio ambiente es cosa de todos. 

AVIS: 
El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou 
el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o 
copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge 
per error, us agrairem que ho feu saber immediatament al remitent i que 
procediu a destruir el missatge . 

AVISO: 
El contenido de este mensaje y de sus anexos es confidencial. Si no es el 
destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o 
copiarlo sin tener la autorización correspondiente. Si han recibido este 
mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al 
remitente y que procedan a destruir el mensaje . 

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

Re: [Users] ovirt reporting wrong cpu family (2nd server)

2013-03-02 Thread Adrian Gibanel 
This is another server which I have also problems with. I cannot select 
SandyBridge as the cpu type.
Still oVirt 3.1 in Fedora 17.

* Tecnology : Sandy Bridge E
* CPU : Intel Xeon E5-1620
* Cores / Threads : 4 / 8
* Frecuency : 3.6GHz / 3.8GHz Turbo Boost

#cpuinfo:
  Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz

# rpm -qa | grep -E 'vdsm|libvirt' | sort
libvirt-0.9.11.9-1.fc17.x86_64
libvirt-client-0.9.11.9-1.fc17.x86_64
libvirt-daemon-0.9.11.9-1.fc17.x86_64
libvirt-daemon-config-network-0.9.11.9-1.fc17.x86_64
libvirt-daemon-config-nwfilter-0.9.11.9-1.fc17.x86_64
libvirt-lock-sanlock-0.9.11.9-1.fc17.x86_64
libvirt-python-0.9.11.9-1.fc17.x86_64
vdsm-4.10.0-10.fc17.x86_64
vdsm-cli-4.10.0-10.fc17.noarch
vdsm-python-4.10.0-10.fc17.x86_64
vdsm-xmlrpc-4.10.0-10.fc17.noarch

# virsh -r capabilities



  
----002590a41888

  x86_64
  SandyBridge
  Intel
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  
  
  


  
  
tcp
  


  

  








  

  


  selinux
  0

  

  
hvm

  32
  /usr/bin/qemu-system-x86_64
  pc-0.15
  pc-1.0
  pc
  pc-0.14
  pc-0.13
  pc-0.12
  pc-0.11
  pc-0.10
  isapc
  
  
  
/usr/bin/qemu-kvm
pc-0.15
pc-1.0
pc
pc-0.14
pc-0.13
pc-0.12
pc-0.11
pc-0.10
isapc
  


  
  
  
  
  
  

  

  
hvm

  64
  /usr/bin/qemu-system-x86_64
  pc-0.15
  pc-1.0
  pc
  pc-0.14
  pc-0.13
  pc-0.12
  pc-0.11
  pc-0.10
  isapc
  
  
  
/usr/bin/qemu-kvm
pc-0.15
pc-1.0
pc
pc-0.14
pc-0.13
pc-0.12
pc-0.11
pc-0.10
isapc
  


  
  
  
  

  





- Mensaje original - 

> At first, let me say that this is very weird CPU detection as according
> to these flags, the processor described in here should be "Nehalem".
> Could you try running 'virsh -r capabilities' on the host to check what
> libvirt reports?

-- 
Adrián Gibanel 
I.T. Manager 

+34 675 683 301 
www.btactic.com 



Ens podeu seguir a/Nos podeis seguir en: 

i 

Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és 
cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El 
medio ambiente es cosa de todos. 

AVIS: 
El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou 
el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o 
copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge 
per error, us agrairem que ho feu saber immediatament al remitent i que 
procediu a destruir el missatge . 

AVISO: 
El contenido de este mensaje y de sus anexos es confidencial. Si no es el 
destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o 
copiarlo sin tener la autorización correspondiente. Si han recibido este 
mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al 
remitente y que procedan a destruir el mensaje . 

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

Re: [Users] ovirt reporting wrong cpu family

2013-03-02 Thread Adrian Gibanel 
Sorry for the late answer. I was kind of busy. I reply inline below.

- Mensaje original - 

> De: "Martin Kletzander" 
> Para: "Itamar Heim" 
> CC: "Adrian Gibanel" , users@ovirt.org, "Jithin
> Raju" 
> Enviados: Martes, 19 de Febrero 2013 15:11:05
> Asunto: Re: [Users] ovirt reporting wrong cpu family

> On 02/16/2013 10:02 PM, Itamar Heim wrote:
> > Adrian - can you later please wikify this recurring question?
> >

> If this is related to libvirt detecting the wrong CPU, we have a short
> wiki page [1] for that either, you can link to that in yours (or maybe
> it'll help you write it).
Thank you. I'll take a look. More below.

> [...]
> >> On 16/02/2013 18:56, Adrian Gibanel wrote:
> >>> I happen to have the same problem in oVirt 3.1 on Fedora.
> >>> Any workaround?
> >>>
> >>> $ sudo vdsClient -s 0 getVdsCaps | grep -i flags ; echo -e -n "\n" ;cat
> >>> /proc/cpuinfo | grep "model name" | head -n 1
> >>> cpuFlags =
> >>> 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,xsave,avx,lahf_lm,arat,epb,xsaveopt,pln,pts,dtherm,tpr_shadow,vnmi,flexpriority,ept,vpid,model_coreduo,model_Conroe
> >>>

> At first, let me say that this is very weird CPU detection as according
> to these flags, the processor described in here should be "Nehalem".
> Could you try running 'virsh -r capabilities' on the host to check what
> libvirt reports?

Here you are:



  
c090c38a-5202-e211-bbb4-4c72b97c99ed

  x86_64
  Nehalem
  Intel
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  
  
  


  
  
tcp
  


  

  




  

  


  selinux
  0

  

  
hvm

  32
  /usr/bin/qemu-system-x86_64
  pc-0.15
  pc-1.0
  pc
  pc-0.14
  pc-0.13
  pc-0.12
  pc-0.11
  pc-0.10
  isapc
  
  
  
/usr/bin/qemu-kvm
pc-0.15
pc-1.0
pc
pc-0.14
pc-0.13
pc-0.12
pc-0.11
pc-0.10
isapc
  


  
  
  
  
  
  

  

  
hvm

  64
  /usr/bin/qemu-system-x86_64
  pc-0.15
  pc-1.0
  pc
  pc-0.14
  pc-0.13
  pc-0.12
  pc-0.11
  pc-0.10
  isapc
  
  
  
/usr/bin/qemu-kvm
pc-0.15
pc-1.0
pc
pc-0.14
pc-0.13
pc-0.12
pc-0.11
pc-0.10
isapc
  


  
  
  
  

  




> There might be a possible workaround if you want your CPU to be
> identified as different model, most probably by editing
> '/usr/share/libvirt/cpu_map.xml', but that should be omitted since it
> may lead to problems.
Non applicable workaround then. I should have expected it. Ok, I prefer not 
having additional problems.

> [...]
> >>> model name : Intel(R) Core(TM) i3-2130 CPU @ 3.40GHz
> >>>

> And as I see the CPU is SandyBridge, so this should be solved properly
> (probably a bug somewhere or very low-level misconfiguration). Check
> [1], maybe some features can get enabled.

The machine is in a datacentre so I doubt I can change any BIOS or UEFI 
settings.

> Martin

> [1]
> http://wiki.libvirt.org/page/Libvirt_identifies_host_processor_as_a_different_model_from_the_hardware_documentation

-- 
-- 
Adrián Gibanel 
I.T. Manager 

+34 675 683 301 
www.btactic.com 



Ens podeu seguir a/Nos podeis seguir en: 

i 

Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és 
cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El 
medio ambiente es cosa de todos. 

AVIS: 
El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou 
el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o 
copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge 
per error, us agrairem que ho feu saber immediatament al remitent i que 
procediu a destruir el missatge . 

AVISO: 
El contenido de este mensaje y de sus anexos es confidencial. Si no es el 
destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o 
copiarlo sin tener la autorización correspondiente. Si han recibido este 
mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al 
remitente y que procedan a destruir el mensaje . 

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

Re: [Users] ovirt reporting wrong cpu family

2013-02-19 Thread Martin Kletzander 
On 02/16/2013 10:02 PM, Itamar Heim wrote:
> On 16/02/2013 22:46, Adrian Gibanel wrote:
>> Yes, I know. I meant a workaround where the processor is detected as
>> SandyBridge.
> 
> Adrian - please provide libvirt version.
> Martin - can you please take a look?

I'm not sure what kind of help I can give here, but let me see.

> Adrian - can you later please wikify this recurring question?
> 

If this is related to libvirt detecting the wrong CPU, we have a short
wiki page [1] for that either, you can link to that in yours (or maybe
it'll help you write it).

[...]
>> On 16/02/2013 18:56, Adrian Gibanel wrote:
>>> I happen to have the same problem in oVirt 3.1 on Fedora.
>>> Any workaround?
>>>
>>> $ sudo vdsClient -s 0 getVdsCaps | grep -i flags ; echo -e -n "\n" ;cat 
>>> /proc/cpuinfo | grep "model name" | head -n 1
>>> cpuFlags = 
>>> 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,xsave,avx,lahf_lm,arat,epb,xsaveopt,pln,pts,dtherm,tpr_shadow,vnmi,flexpriority,ept,vpid,model_coreduo,model_Conroe
>>>

At first, let me say that this is very weird CPU detection as according
to these flags, the processor described in here should be "Nehalem".
Could you try running 'virsh -r capabilities' on the host to check what
libvirt reports?

There might be a possible workaround if you want your CPU to be
identified as different model, most probably by editing
'/usr/share/libvirt/cpu_map.xml', but that should be omitted since it
may lead to problems.

[...]
>>> model name : Intel(R) Core(TM) i3-2130 CPU @ 3.40GHz
>>>

And as I see the CPU is SandyBridge, so this should be solved properly
(probably a bug somewhere or very low-level misconfiguration).  Check
[1], maybe some features can get enabled.

Martin

[1]
http://wiki.libvirt.org/page/Libvirt_identifies_host_processor_as_a_different_model_from_the_hardware_documentation
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] ovirt reporting wrong cpu family

2013-02-16 Thread Adrian Gibanel 
Here there's my libvirt version: 

$ rpm -qa | grep libvirt 
libvirt-daemon-config-nwfilter-0.9.11.9-1.fc17.x86_64 
libvirt-python-0.9.11.9-1.fc17.x86_64 
libvirt-client-0.9.11.9-1.fc17.x86_64 
libvirt-daemon-0.9.11.9-1.fc17.x86_64 
libvirt-lock-sanlock-0.9.11.9-1.fc17.x86_64 
libvirt-0.9.11.9-1.fc17.x86_64 
libvirt-daemon-config-network-0.9.11.9-1.fc17.x86_64 

Yes, I suppose I will be able to wikify it. 

- Mensaje original - 

> De: "Itamar Heim" 
> Para: "Adrian Gibanel" 
> CC: users@ovirt.org, "Jithin Raju" , "Martin
> Kletzander" 
> Enviados: Sábado, 16 de Febrero 2013 22:02:01
> Asunto: Re: [Users] ovirt reporting wrong cpu family

> On 16/02/2013 22:46, Adrian Gibanel wrote:
> > Yes, I know. I meant a workaround where the processor is detected
> > as
> > SandyBridge.

> Adrian - please provide libvirt version.
> Martin - can you please take a look?
> Adrian - can you later please wikify this recurring question?

> Thanks,
> Itamar

> >
> > Thank you.
> >
> > 
> >
> > *De: *"Itamar Heim" 
> > *Para: *"Adrian Gibanel" 
> > *CC: *"Jithin Raju" , users@ovirt.org
> > *Enviados: *Sábado, 16 de Febrero 2013 21:36:38
> > *Asunto: *Re: [Users] ovirt reporting wrong cpu family
> >
> > On 16/02/2013 18:56, Adrian Gibanel wrote:
> > > I happen to have the same problem in oVirt 3.1 on Fedora.
> > > Any workaround?
> > >
> > > $ sudo vdsClient -s 0 getVdsCaps | grep -i flags ; echo -e -n
> > "\n" ;cat /proc/cpuinfo | grep "model name" | head -n 1
> > > cpuFlags =
> > 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,xsave,avx,lahf_lm,arat,epb,xsaveopt,pln,pts,dtherm,tpr_shadow,vnmi,flexpriority,ept,vpid,model_coreduo,model_Conroe
> >
> > you cpu is identified as model_Conroe, which should work. just set
> > the
> > cluster level to Conroe (should happen automatically if first host
> > added
> > to the cluster)
> >
> > >
> > > model name : Intel(R) Core(TM) i3-2130 CPU @ 3.40GHz
> > >
> > > $ rpm -qa | grep -i ovirt ; rpm -qa | grep -i vdsm
> > > ovirt-release-fedora-5-2.noarch
> > > vdsm-python-4.10.0-10.fc17.x86_64
> > > vdsm-cli-4.10.0-10.fc17.noarch
> > > vdsm-4.10.0-10.fc17.x86_64
> > > vdsm-xmlrpc-4.10.0-10.fc17.noarch

-- 

-- 
Adrián Gibanel 
I.T. Manager 

+34 675 683 301 
www.btactic.com 



Ens podeu seguir a/Nos podeis seguir en: 

i 


Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és 
cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El 
medio ambiente es cosa de todos. 

AVIS: 
El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou 
el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o 
copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge 
per error, us agrairem que ho feu saber immediatament al remitent i que 
procediu a destruir el missatge . 

AVISO: 
El contenido de este mensaje y de sus anexos es confidencial. Si no es el 
destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o 
copiarlo sin tener la autorización correspondiente. Si han recibido este 
mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al 
remitente y que procedan a destruir el mensaje . 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] ovirt reporting wrong cpu family

2013-02-16 Thread Itamar Heim 

On 16/02/2013 22:46, Adrian Gibanel wrote:

Yes, I know. I meant a workaround where the processor is detected as
SandyBridge.


Adrian - please provide libvirt version.
Martin - can you please take a look?
Adrian - can you later please wikify this recurring question?

Thanks,
   Itamar



Thank you.



*De: *"Itamar Heim" 
*Para: *"Adrian Gibanel" 
*CC: *"Jithin Raju" , users@ovirt.org
*Enviados: *Sábado, 16 de Febrero 2013 21:36:38
    *Asunto: *Re: [Users] ovirt reporting wrong cpu family

On 16/02/2013 18:56, Adrian Gibanel wrote:
 > I happen to have the same problem in oVirt 3.1 on Fedora.
 > Any workaround?
 >
 > $ sudo vdsClient -s 0 getVdsCaps | grep -i flags ; echo -e -n
"\n" ;cat /proc/cpuinfo | grep "model name" | head -n 1
 > cpuFlags =

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,xsave,avx,lahf_lm,arat,epb,xsaveopt,pln,pts,dtherm,tpr_shadow,vnmi,flexpriority,ept,vpid,model_coreduo,model_Conroe

you cpu is identified as model_Conroe, which should work. just set the
cluster level to Conroe (should happen automatically if first host
added
to the cluster)

 >
 > model name : Intel(R) Core(TM) i3-2130 CPU @ 3.40GHz
 >
 > $ rpm -qa | grep -i ovirt ; rpm -qa | grep -i vdsm
 > ovirt-release-fedora-5-2.noarch
 > vdsm-python-4.10.0-10.fc17.x86_64
 > vdsm-cli-4.10.0-10.fc17.noarch
 > vdsm-4.10.0-10.fc17.x86_64
 > vdsm-xmlrpc-4.10.0-10.fc17.noarch

--
<http://www.btactic.com/>*Adrián Gibanel*
I.T. Manager

+34 675 683 301
www.btactic.com <http://btactic.com/>


*
Ens podeu seguir a/Nos podeis seguir en:

<http://www.facebook.com/pages/btactic/118651634826400?v=app_9953271133>
i <http://twitter.com/btactic>*

Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi
ambient és cosa de tothom. / Antes de imprimir el mensaje piensa en el
medio ambiente. El medio ambiente es cosa de todos.

AVIS:
El contingut d'aquest missatge i els seus annexos és confidencial. Si no
en sou el destinatari, us fem saber que està prohibit utilitzar-lo,
divulgar-lo i/o copiar-lo sense tenir l'autorització corresponent. Si
heu rebut aquest missatge per error, us agrairem que ho feu saber
immediatament al remitent i que procediu a destruir el missatge.

AVISO:
El contenido de este mensaje y de sus anexos es confidencial. Si no es
el destinatario, les hacemos saber que está prohibido utilizarlo,
divulgarlo y/o copiarlo sin tener la autorización correspondiente. Si
han recibido este mensaje por error, les agradeceríamos que lo hagan
saber inmediatamente al remitente y que procedan a destruir el mensaje.



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

Re: [Users] ovirt reporting wrong cpu family

2013-02-16 Thread Adrian Gibanel 
Yes, I know. I meant a workaround where the processor is detected as 
SandyBridge. 

Thank you. 

- Mensaje original -

> De: "Itamar Heim" 
> Para: "Adrian Gibanel" 
> CC: "Jithin Raju" , users@ovirt.org
> Enviados: Sábado, 16 de Febrero 2013 21:36:38
> Asunto: Re: [Users] ovirt reporting wrong cpu family

> On 16/02/2013 18:56, Adrian Gibanel wrote:
> > I happen to have the same problem in oVirt 3.1 on Fedora.
> > Any workaround?
> >
> > $ sudo vdsClient -s 0 getVdsCaps | grep -i flags ; echo -e -n "\n"
> > ;cat /proc/cpuinfo | grep "model name" | head -n 1
> > cpuFlags =
> > 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,xsave,avx,lahf_lm,arat,epb,xsaveopt,pln,pts,dtherm,tpr_shadow,vnmi,flexpriority,ept,vpid,model_coreduo,model_Conroe

> you cpu is identified as model_Conroe, which should work. just set
> the
> cluster level to Conroe (should happen automatically if first host
> added
> to the cluster)

> >
> > model name : Intel(R) Core(TM) i3-2130 CPU @ 3.40GHz
> >
> > $ rpm -qa | grep -i ovirt ; rpm -qa | grep -i vdsm
> > ovirt-release-fedora-5-2.noarch
> > vdsm-python-4.10.0-10.fc17.x86_64
> > vdsm-cli-4.10.0-10.fc17.noarch
> > vdsm-4.10.0-10.fc17.x86_64
> > vdsm-xmlrpc-4.10.0-10.fc17.noarch

-- 

Adrián Gibanel 
I.T. Manager 

+34 675 683 301 
www.btactic.com 

Ens podeu seguir a/Nos podeis seguir en: 

i 

Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és 
cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El 
medio ambiente es cosa de todos. 

AVIS: 
El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou 
el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o 
copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge 
per error, us agrairem que ho feu saber immediatament al remitent i que 
procediu a destruir el missatge . 

AVISO: 
El contenido de este mensaje y de sus anexos es confidencial. Si no es el 
destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o 
copiarlo sin tener la autorización correspondiente. Si han recibido este 
mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al 
remitente y que procedan a destruir el mensaje . 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] ovirt reporting wrong cpu family

2013-02-16 Thread Itamar Heim 

On 16/02/2013 18:56, Adrian Gibanel wrote:

I happen to have the same problem in oVirt 3.1 on Fedora.
Any workaround?

$ sudo vdsClient -s 0 getVdsCaps | grep -i flags ; echo -e -n "\n" ;cat /proc/cpuinfo | 
grep "model name" | head -n 1
cpuFlags = 
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,xsave,avx,lahf_lm,arat,epb,xsaveopt,pln,pts,dtherm,tpr_shadow,vnmi,flexpriority,ept,vpid,model_coreduo,model_Conroe


you cpu is identified as model_Conroe, which should work. just set the 
cluster level to Conroe (should happen automatically if first host added 
to the cluster)




model name : Intel(R) Core(TM) i3-2130 CPU @ 3.40GHz

$ rpm -qa | grep -i ovirt ; rpm -qa | grep -i vdsm
ovirt-release-fedora-5-2.noarch
vdsm-python-4.10.0-10.fc17.x86_64
vdsm-cli-4.10.0-10.fc17.noarch
vdsm-4.10.0-10.fc17.x86_64
vdsm-xmlrpc-4.10.0-10.fc17.noarch

- Mensaje original -


De: "Jithin Raju" 
Para: "Itamar Heim" 
CC: users@ovirt.org
Enviados: Jueves, 3 de Enero 2013 4:49:34
Asunto: Re: [Users] ovirt reporting wrong cpu family



Hi ,



Please find the requested flags below:



[root@fig /]# vdsClient -s 0 getVdsCaps | grep -i flags
cpuFlags =
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,pdpe1gb,rdtscp,lm,constant_tsc,arch_perfmon,pebs,bts,rep_good,nopl,xtopology,nonstop_tsc,aperfmperf,pni,pclmulqdq,dtes64,monitor,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,pcid,dca,sse4_1,sse4_2,x2apic,popcnt,tsc_deadline_timer,aes,xsave,avx,lahf_lm,ida,arat,epb,xsaveopt,pln,pts,dtherm,tpr_shadow,vnmi,flexpriority,ept,vpid,model_coreduo,model_Conroe



Thanks,
Jithin



On Thu, Jan 3, 2013 at 2:03 AM, Itamar Heim < ih...@redhat.com >
wrote:



On 01/02/2013 03:37 PM, Jithin Raju wrote:





Hi,







I have installed ovirt 3.1 on fedora 17.





I added my node wtih intel E5-2620 (sandy bridge) to cluster.





Even though model is detected properly,CPU name is shown as Intel
Conroe





family instead of sandy bridge.





Since my cluster is configured as sandy bridge i got this error:







Host fig moved to Non-Operational state as host does not meet the





cluster's minimum CPU level. Missing CPU features :
model_SandyBridge.







as per cpuinfo :model name : Intel(R) Xeon(R) CPU E5-2620 0 @
2.00GHz.







i moved the cluster to conroe ,got the host up.







reference:





http://en.wikipedia.org/wiki/ Sandy_Bridge_( microarchitecture)





http://ark.intel.com/products/ 64594







PFA for screenshot.







Thanks,





Jithin








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

Re: [Users] ovirt reporting wrong cpu family

2013-02-16 Thread Adrian Gibanel 
I happen to have the same problem in oVirt 3.1 on Fedora.
Any workaround?

$ sudo vdsClient -s 0 getVdsCaps | grep -i flags ; echo -e -n "\n" ;cat 
/proc/cpuinfo | grep "model name" | head -n 1 
cpuFlags = 
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,xsave,avx,lahf_lm,arat,epb,xsaveopt,pln,pts,dtherm,tpr_shadow,vnmi,flexpriority,ept,vpid,model_coreduo,model_Conroe
 

model name : Intel(R) Core(TM) i3-2130 CPU @ 3.40GHz 

$ rpm -qa | grep -i ovirt ; rpm -qa | grep -i vdsm 
ovirt-release-fedora-5-2.noarch 
vdsm-python-4.10.0-10.fc17.x86_64 
vdsm-cli-4.10.0-10.fc17.noarch 
vdsm-4.10.0-10.fc17.x86_64 
vdsm-xmlrpc-4.10.0-10.fc17.noarch 

- Mensaje original - 

> De: "Jithin Raju" 
> Para: "Itamar Heim" 
> CC: users@ovirt.org
> Enviados: Jueves, 3 de Enero 2013 4:49:34
> Asunto: Re: [Users] ovirt reporting wrong cpu family

> Hi ,

> Please find the requested flags below:

> [root@fig /]# vdsClient -s 0 getVdsCaps | grep -i flags
> cpuFlags =
> 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,pdpe1gb,rdtscp,lm,constant_tsc,arch_perfmon,pebs,bts,rep_good,nopl,xtopology,nonstop_tsc,aperfmperf,pni,pclmulqdq,dtes64,monitor,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,pcid,dca,sse4_1,sse4_2,x2apic,popcnt,tsc_deadline_timer,aes,xsave,avx,lahf_lm,ida,arat,epb,xsaveopt,pln,pts,dtherm,tpr_shadow,vnmi,flexpriority,ept,vpid,model_coreduo,model_Conroe

> Thanks,
> Jithin

> On Thu, Jan 3, 2013 at 2:03 AM, Itamar Heim < ih...@redhat.com >
> wrote:

> > On 01/02/2013 03:37 PM, Jithin Raju wrote:
> 

> > > Hi,
> > 
> 

> > > I have installed ovirt 3.1 on fedora 17.
> > 
> 
> > > I added my node wtih intel E5-2620 (sandy bridge) to cluster.
> > 
> 
> > > Even though model is detected properly,CPU name is shown as Intel
> > > Conroe
> > 
> 
> > > family instead of sandy bridge.
> > 
> 
> > > Since my cluster is configured as sandy bridge i got this error:
> > 
> 

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

> > > as per cpuinfo :model name : Intel(R) Xeon(R) CPU E5-2620 0 @
> > > 2.00GHz.
> > 
> 

> > > i moved the cluster to conroe ,got the host up.
> > 
> 

> > > reference:
> > 
> 
> > > http://en.wikipedia.org/wiki/ Sandy_Bridge_( microarchitecture)
> > 
> 
> > > http://ark.intel.com/products/ 64594
> > 
> 

> > > PFA for screenshot.
> > 
> 

> > > Thanks,
> > 
> 
> > > Jithin
> > 
> 

-- 

-- 
Adrián Gibanel 
I.T. Manager 

+34 675 683 301 
www.btactic.com 



Ens podeu seguir a/Nos podeis seguir en: 

i 


Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és 
cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El 
medio ambiente es cosa de todos. 

AVIS: 
El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou 
el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o 
copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge 
per error, us agrairem que ho feu saber immediatament al remitent i que 
procediu a destruir el missatge . 

AVISO: 
El contenido de este mensaje y de sus anexos es confidencial. Si no es el 
destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o 
copiarlo sin tener la autorización correspondiente. Si han recibido este 
mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al 
remitente y que procedan a destruir el mensaje . 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] ovirt reporting wrong cpu family

2013-01-02 Thread Itamar Heim 

On 01/03/2013 05:49 AM, Jithin Raju wrote:

Hi ,

Please find the requested flags below:

[root@fig /]# vdsClient -s 0 getVdsCaps | grep -i flags
 cpuFlags =
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,pdpe1gb,rdtscp,lm,constant_tsc,arch_perfmon,pebs,bts,rep_good,nopl,xtopology,nonstop_tsc,aperfmperf,pni,pclmulqdq,dtes64,monitor,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,pcid,dca,sse4_1,sse4_2,x2apic,popcnt,tsc_deadline_timer,aes,xsave,avx,lahf_lm,ida,arat,epb,xsaveopt,pln,pts,dtherm,tpr_shadow,vnmi,flexpriority,ept,vpid,model_coreduo,model_Conroe


i think a libvirt bug not detecting the model correctly (vdsm collects 
the list of models detect by libvirt and appends them to the cpu flags 
string - here model_Conroe).

martin?




Thanks,
Jithin


On Thu, Jan 3, 2013 at 2:03 AM, Itamar Heim mailto:ih...@redhat.com>> wrote:

On 01/02/2013 03:37 PM, Jithin Raju wrote:

Hi,

I have installed ovirt 3.1 on fedora 17.
I added my node wtih intel E5-2620 (sandy bridge) to cluster.
Even though model is detected properly,CPU name is shown as
Intel Conroe
family instead of sandy bridge.
Since my cluster is configured as sandy bridge i got this error:

Host fig moved to Non-Operational state as host does not meet the
cluster's minimum CPU level. Missing CPU features :
model_SandyBridge.

as per cpuinfo :model name  : Intel(R) Xeon(R) CPU E5-2620 0
@ 2.00GHz.

i moved the cluster to conroe ,got the host up.

reference:
http://en.wikipedia.org/wiki/__Sandy_Bridge_(__microarchitecture) 

http://ark.intel.com/products/__64594


PFA for screenshot.

Thanks,
Jithin


_
Users mailing list
Users@ovirt.org 
http://lists.ovirt.org/__mailman/listinfo/users



please share "vdsClient -s 0 getVdsCaps | grep -i flags" from the host





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

Re: [Users] ovirt reporting wrong cpu family

2013-01-02 Thread Jithin Raju 
Hi ,

Please find the requested flags below:

[root@fig /]# vdsClient -s 0 getVdsCaps | grep -i flags
cpuFlags =
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,pdpe1gb,rdtscp,lm,constant_tsc,arch_perfmon,pebs,bts,rep_good,nopl,xtopology,nonstop_tsc,aperfmperf,pni,pclmulqdq,dtes64,monitor,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,pcid,dca,sse4_1,sse4_2,x2apic,popcnt,tsc_deadline_timer,aes,xsave,avx,lahf_lm,ida,arat,epb,xsaveopt,pln,pts,dtherm,tpr_shadow,vnmi,flexpriority,ept,vpid,model_coreduo,model_Conroe

Thanks,
Jithin


On Thu, Jan 3, 2013 at 2:03 AM, Itamar Heim  wrote:

> On 01/02/2013 03:37 PM, Jithin Raju wrote:
>
>> Hi,
>>
>> I have installed ovirt 3.1 on fedora 17.
>> I added my node wtih intel E5-2620 (sandy bridge) to cluster.
>> Even though model is detected properly,CPU name is shown as Intel Conroe
>> family instead of sandy bridge.
>> Since my cluster is configured as sandy bridge i got this error:
>>
>> Host fig moved to Non-Operational state as host does not meet the
>> cluster's minimum CPU level. Missing CPU features : model_SandyBridge.
>>
>> as per cpuinfo :model name  : Intel(R) Xeon(R) CPU E5-2620 0 @
>> 2.00GHz.
>>
>> i moved the cluster to conroe ,got the host up.
>>
>> reference:
>> http://en.wikipedia.org/wiki/**Sandy_Bridge_(**microarchitecture)
>> http://ark.intel.com/products/**64594
>>
>> PFA for screenshot.
>>
>> Thanks,
>> Jithin
>>
>>
>> __**_
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/**mailman/listinfo/users
>>
>>
> please share "vdsClient -s 0 getVdsCaps | grep -i flags" from the host
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] ovirt reporting wrong cpu family

2013-01-02 Thread Jeff Bailey 

On 1/2/2013 3:33 PM, Itamar Heim wrote:

On 01/02/2013 03:37 PM, Jithin Raju wrote:

Hi,

I have installed ovirt 3.1 on fedora 17.
I added my node wtih intel E5-2620 (sandy bridge) to cluster.
Even though model is detected properly,CPU name is shown as Intel Conroe
family instead of sandy bridge.
Since my cluster is configured as sandy bridge i got this error:

Host fig moved to Non-Operational state as host does not meet the
cluster's minimum CPU level. Missing CPU features : model_SandyBridge.



I had a similar problem with 3.1 and E5-2670's.  The 3.2 alpha works 
fine though.


as per cpuinfo :model name  : Intel(R) Xeon(R) CPU E5-2620 0 @ 
2.00GHz.


i moved the cluster to conroe ,got the host up.

reference:
http://en.wikipedia.org/wiki/Sandy_Bridge_(microarchitecture)
http://ark.intel.com/products/64594

PFA for screenshot.

Thanks,
Jithin


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



please share "vdsClient -s 0 getVdsCaps | grep -i flags" from the host

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


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

Re: [Users] ovirt reporting wrong cpu family

2013-01-02 Thread Itamar Heim 

On 01/02/2013 03:37 PM, Jithin Raju wrote:

Hi,

I have installed ovirt 3.1 on fedora 17.
I added my node wtih intel E5-2620 (sandy bridge) to cluster.
Even though model is detected properly,CPU name is shown as Intel Conroe
family instead of sandy bridge.
Since my cluster is configured as sandy bridge i got this error:

Host fig moved to Non-Operational state as host does not meet the
cluster's minimum CPU level. Missing CPU features : model_SandyBridge.

as per cpuinfo :model name  : Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz.

i moved the cluster to conroe ,got the host up.

reference:
http://en.wikipedia.org/wiki/Sandy_Bridge_(microarchitecture)
http://ark.intel.com/products/64594

PFA for screenshot.

Thanks,
Jithin


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



please share "vdsClient -s 0 getVdsCaps | grep -i flags" from the host

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