[Users] ovirt reporting wrong cpu family
Adrian Gibanel
adrian.gibanel at btactic.com
Sat Mar 2 16:07:05 UTC 2013
Sorry for the late answer. I was kind of busy. I reply inline below.
----- Mensaje original -----
> De: "Martin Kletzander" <mkletzan at redhat.com>
> Para: "Itamar Heim" <iheim at redhat.com>
> CC: "Adrian Gibanel" <adrian.gibanel at btactic.com>, users at ovirt.org, "Jithin
> Raju" <rajujith at 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>
<uuid>c090c38a-5202-e211-bbb4-4c72b97c99ed</uuid>
<cpu>
<arch>x86_64</arch>
<model>Nehalem</model>
<vendor>Intel</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_transport>tcp</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>
<model>selinux</model>
<doi>0</doi>
</secmodel>
</host>
<guest>
<os_type>hvm</os_type>
<arch name='i686'>
<wordsize>32</wordsize>
<emulator>/usr/bin/qemu-system-x86_64</emulator>
<machine>pc-0.15</machine>
<machine>pc-1.0</machine>
<machine canonical='pc-1.0'>pc</machine>
<machine>pc-0.14</machine>
<machine>pc-0.13</machine>
<machine>pc-0.12</machine>
<machine>pc-0.11</machine>
<machine>pc-0.10</machine>
<machine>isapc</machine>
<domain type='qemu'>
</domain>
<domain type='kvm'>
<emulator>/usr/bin/qemu-kvm</emulator>
<machine>pc-0.15</machine>
<machine>pc-1.0</machine>
<machine canonical='pc-1.0'>pc</machine>
<machine>pc-0.14</machine>
<machine>pc-0.13</machine>
<machine>pc-0.12</machine>
<machine>pc-0.11</machine>
<machine>pc-0.10</machine>
<machine>isapc</machine>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
<pae/>
<nonpae/>
<acpi default='on' toggle='yes'/>
<apic default='on' toggle='no'/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='x86_64'>
<wordsize>64</wordsize>
<emulator>/usr/bin/qemu-system-x86_64</emulator>
<machine>pc-0.15</machine>
<machine>pc-1.0</machine>
<machine canonical='pc-1.0'>pc</machine>
<machine>pc-0.14</machine>
<machine>pc-0.13</machine>
<machine>pc-0.12</machine>
<machine>pc-0.11</machine>
<machine>pc-0.10</machine>
<machine>isapc</machine>
<domain type='qemu'>
</domain>
<domain type='kvm'>
<emulator>/usr/bin/qemu-kvm</emulator>
<machine>pc-0.15</machine>
<machine>pc-1.0</machine>
<machine canonical='pc-1.0'>pc</machine>
<machine>pc-0.14</machine>
<machine>pc-0.13</machine>
<machine>pc-0.12</machine>
<machine>pc-0.11</machine>
<machine>pc-0.10</machine>
<machine>isapc</machine>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
<acpi default='on' toggle='yes'/>
<apic default='on' toggle='no'/>
</features>
</guest>
</capabilities>
> 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 .
More information about the Users
mailing list