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 :

  model name='SandyBridge'
model name='Westmere'/
feature name='pclmuldq'/
feature name='x2apic'/
feature name='tsc-deadline'/
feature name='xsave'/
feature name='avx'/
feature name='rdtscp'/
  /model

 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
 
 capabilities
 
   host
 uuid----002590a41888/uuid
 cpu
   archx86_64/arch
   modelSandyBridge/model

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 adrian.giba...@btactic.com
 Para: users@ovirt.org
 CC: Itamar Heim ih...@redhat.com, Jithin Raju
 rajuj...@gmail.com,
 Martin Kletzander mklet...@redhat.com
 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

 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

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 mklet...@redhat.com
 Para: Itamar Heim ih...@redhat.com
 CC: Adrian Gibanel adrian.giba...@btactic.com, users@ovirt.org, Jithin
 Raju rajuj...@gmail.com
 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:

capabilities

  host
uuidc090c38a-5202-e211-bbb4-4c72b97c99ed/uuid
cpu
  archx86_64/arch
  modelNehalem/model
  vendorIntel/vendor
  topology sockets='1' cores='2' threads='2'/
  feature name='rdtscp'/
  feature name='avx'/
  feature name='osxsave'/
  feature name='xsave'/
  feature name='tsc-deadline'/
  feature name='pdcm'/
  feature name='xtpr'/
  feature name='tm2'/
  feature name='est'/
  feature name='vmx'/
  feature name='ds_cpl'/
  feature name='monitor'/
  feature name='dtes64'/
  feature name='pclmuldq'/
  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_mem/
  suspend_disk/
  suspend_hybrid/
/power_management
migration_features
  live/
  uri_transports
uri_transporttcp/uri_transport
  /uri_transports
/migration_features
topology
  cells num='1'
cell id='0'
  cpus num='4'
cpu id='0'/
cpu id='1'/
cpu id='2'/
cpu id='3'/
  /cpus
/cell
  /cells
/topology
secmodel
  modelselinux/model
  doi0/doi
/secmodel
  /host

  guest
os_typehvm/os_type
arch name='i686'
  wordsize32/wordsize
  emulator/usr/bin/qemu-system-x86_64/emulator
  machinepc-0.15/machine
  machinepc-1.0/machine
  machine canonical='pc-1.0'pc/machine
  machinepc-0.14/machine
  machinepc-0.13/machine
  machinepc-0.12/machine
  machinepc-0.11/machine
  machinepc-0.10/machine
  machineisapc/machine
  domain type='qemu'
  /domain
  domain type='kvm'
emulator/usr/bin/qemu-kvm/emulator
machinepc-0.15/machine
machinepc-1.0/machine
machine canonical='pc-1.0'pc/machine
machinepc-0.14/machine
machinepc-0.13/machine
machinepc-0.12/machine
machinepc-0.11/machine
machinepc-0.10/machine
machineisapc/machine
  /domain
/arch
features
  cpuselection/
  deviceboot/
  pae/
  nonpae/
  acpi default='on' toggle='yes'/
  apic default='on' toggle='no'/
/features
  /guest

  guest
os_typehvm/os_type
arch name='x86_64'
  wordsize64/wordsize
  emulator/usr/bin/qemu-system-x86_64/emulator
  machinepc-0.15/machine
  machinepc-1.0/machine
  machine canonical='pc-1.0'pc/machine
  machinepc-0.14/machine
  machinepc-0.13/machine
  machinepc-0.12/machine
  machinepc-0.11/machine
  machinepc-0.10/machine
  machineisapc/machine
  domain type='qemu'
  /domain
  domain type='kvm'
emulator/usr/bin/qemu-kvm/emulator
machinepc-0.15/machine
machinepc-1.0/machine
machine canonical='pc-1.0'pc/machine
machinepc-0.14/machine
machinepc-0.13/machine
machinepc-0.12/machine
machinepc-0.11/machine
machinepc-0.10/machine
machineisapc/machine
  /domain
/arch
features
  cpuselection/
  deviceboot/
  acpi default='on' toggle='yes'/
  apic default='on' toggle='no'/
/features
  /guest

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

capabilities

  host
uuid----002590a41888/uuid
cpu
  archx86_64/arch
  modelSandyBridge/model
  vendorIntel/vendor
  topology sockets='1' cores='4' threads='2'/
  feature name='pdpe1gb'/
  feature name='osxsave'/
  feature name='dca'/
  feature name='pdcm'/
  feature name='xtpr'/
  feature name='tm2'/
  feature name='est'/
  feature name='smx'/
  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_mem/
  suspend_disk/
  suspend_hybrid/
/power_management
migration_features
  live/
  uri_transports
uri_transporttcp/uri_transport
  /uri_transports
/migration_features
topology
  cells num='1'
cell id='0'
  cpus num='8'
cpu id='0'/
cpu id='1'/
cpu id='2'/
cpu id='3'/
cpu id='4'/
cpu id='5'/
cpu id='6'/
cpu id='7'/
  /cpus
/cell
  /cells
/topology
secmodel
  modelselinux/model
  doi0/doi
/secmodel
  /host

  guest
os_typehvm/os_type
arch name='i686'
  wordsize32/wordsize
  emulator/usr/bin/qemu-system-x86_64/emulator
  machinepc-0.15/machine
  machinepc-1.0/machine
  machine canonical='pc-1.0'pc/machine
  machinepc-0.14/machine
  machinepc-0.13/machine
  machinepc-0.12/machine
  machinepc-0.11/machine
  machinepc-0.10/machine
  machineisapc/machine
  domain type='qemu'
  /domain
  domain type='kvm'
emulator/usr/bin/qemu-kvm/emulator
machinepc-0.15/machine
machinepc-1.0/machine
machine canonical='pc-1.0'pc/machine
machinepc-0.14/machine
machinepc-0.13/machine
machinepc-0.12/machine
machinepc-0.11/machine
machinepc-0.10/machine
machineisapc/machine
  /domain
/arch
features
  cpuselection/
  deviceboot/
  pae/
  nonpae/
  acpi default='on' toggle='yes'/
  apic default='on' toggle='no'/
/features
  /guest

  guest
os_typehvm/os_type
arch name='x86_64'
  wordsize64/wordsize
  emulator/usr/bin/qemu-system-x86_64/emulator
  machinepc-0.15/machine
  machinepc-1.0/machine
  machine canonical='pc-1.0'pc/machine
  machinepc-0.14/machine
  machinepc-0.13/machine
  machinepc-0.12/machine
  machinepc-0.11/machine
  machinepc-0.10/machine
  machineisapc/machine
  domain type='qemu'
  /domain
  domain type='kvm'
emulator/usr/bin/qemu-kvm/emulator
machinepc-0.15/machine
machinepc-1.0/machine
machine canonical='pc-1.0'pc/machine
machinepc-0.14/machine
machinepc-0.13/machine
machinepc-0.12/machine
machinepc-0.11/machine
machinepc-0.10/machine
machineisapc/machine
  /domain
/arch
features
  cpuselection/
  deviceboot/
  acpi default='on' toggle='yes'/
  apic default='on' toggle='no'/
/features
  /guest

/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 

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 :

 model name='SandyBridge'
   model name='Westmere'/
   feature name='pclmuldq'/
   feature name='x2apic'/
   feature name='tsc-deadline'/
   feature name='xsave'/
   feature name='avx'/
   feature name='rdtscp'/
 /model

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 adrian.giba...@btactic.com
Para: users@ovirt.org
CC: Itamar Heim ih...@redhat.com, Jithin Raju rajuj...@gmail.com,
Martin Kletzander mklet...@redhat.com
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



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

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
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 rajuj...@gmail.com
 Para: Itamar Heim ih...@redhat.com
 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-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 rajuj...@gmail.com
Para: Itamar Heim ih...@redhat.com
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
Yes, I know. I meant a workaround where the processor is detected as 
SandyBridge. 

Thank you. 

- Mensaje original -

 De: Itamar Heim ih...@redhat.com
 Para: Adrian Gibanel adrian.giba...@btactic.com
 CC: Jithin Raju rajuj...@gmail.com, 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 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 ih...@redhat.com
 Para: Adrian Gibanel adrian.giba...@btactic.com
 CC: users@ovirt.org, Jithin Raju rajuj...@gmail.com, Martin
 Kletzander mklet...@redhat.com
 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 ih...@redhat.com
  *Para: *Adrian Gibanel adrian.giba...@btactic.com
  *CC: *Jithin Raju rajuj...@gmail.com, 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


[Users] ovirt reporting wrong cpu family

2013-01-02 Thread Jithin Raju
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
attachment: cpu wrong info.JPG___
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


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 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 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://en.wikipedia.org/wiki/Sandy_Bridge_(microarchitecture)
 http://ark.intel.com/products/**64594http://ark.intel.com/products/64594

 PFA for screenshot.

 Thanks,
 Jithin


 __**_
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/**mailman/listinfo/usershttp://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 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 ih...@redhat.com
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://en.wikipedia.org/wiki/Sandy_Bridge_(microarchitecture)
http://ark.intel.com/products/__64594
http://ark.intel.com/products/64594

PFA for screenshot.

Thanks,
Jithin


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