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

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?

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.gibanel(a)btactic.com&gt; > Para: users(a)ovirt.org > CC: "Itamar Heim" <iheim(a)redhat.com&gt;, "Jithin Raju" <rajujith(a)gmail.com&gt;, > "Martin Kletzander" <mkletzan(a)redhat.com&gt; > 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? > --