Ask Your Question
2

libvirtError: internal error Cannot find suitable CPU model for given data

asked 2013-08-09 09:26:46 -0500

liriarte gravatar image

updated 2013-08-13 11:42:13 -0500

I am trying to run a simple instance after a fresh installation of OpenStack. The instance cannot start and in the log I found "libvirtError: internal error Cannot find suitable CPU model for given data". Please help.

Some info:

libvirt.x86_64 0.10.2.6-5.el6.centos.alt

qemu-kvm.x86_64 2:0.12.1.2-2.355.0.1.el6.centos.6

CentOS release 6.4 (Final). (Linux 3.4.54-8.el6.centos.alt.x86_64 #1 SMP Tue Jul 23 17:29:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux)

/usr/libexec/qemu-kvm  --cpu ?
x86       Opteron_G5  AMD Opteron 63xx class CPU                      
x86       Opteron_G4  AMD Opteron 62xx class CPU                      
x86       Opteron_G3  AMD Opteron 23xx (Gen 3 Class Opteron)          
x86       Opteron_G2  AMD Opteron 22xx (Gen 2 Class Opteron)          
x86       Opteron_G1  AMD Opteron 240 (Gen 1 Class Opteron)           
x86          Haswell  Intel Core Processor (Haswell)                  
x86      SandyBridge  Intel Xeon E312xx (Sandy Bridge)                
x86         Westmere  Westmere E56xx/L56xx/X56xx (Nehalem-C)          
x86          Nehalem  Intel Core i7 9xx (Nehalem Class Core i7)       
x86           Penryn  Intel Core 2 Duo P9xxx (Penryn Class Core 2)    
x86           Conroe  Intel Celeron_4x0 (Conroe/Merom Class Core 2)   
x86      cpu64-rhel5  QEMU Virtual CPU version (cpu64-rhel5)          
x86      cpu64-rhel6  QEMU Virtual CPU version (cpu64-rhel6)          
x86             n270  Intel(R) Atom(TM) CPU N270   @ 1.60GHz          
x86           athlon  QEMU Virtual CPU version 0.12.1                 
x86         pentium3                                                  
x86         pentium2                                                  
x86          pentium                                                  
x86              486                                                  
x86          coreduo  Genuine Intel(R) CPU           T2600  @ 2.16GHz 
x86           qemu32  QEMU Virtual CPU version 0.12.1                 
x86            kvm64  Common KVM processor                            
x86         core2duo  Intel(R) Core(TM)2 Duo CPU     T7700  @ 2.40GHz 
x86           phenom  AMD Phenom(tm) 9550 Quad-Core Processor         
x86           qemu64  QEMU Virtual CPU version 0.12.1 
Recognized CPUID flags:
  f_edx: pbe ia64 tm ht ss sse2 sse fxsr mmx acpi ds clflush pn pse36 pat cmov mca pge mtrr sep apic cx8 mce pae msr tsc pse de vme fpu
  f_ecx: hypervisor rdrand f16c avx osxsave xsave aes tsc-deadline popcnt movbe x2apic sse4.2|sse4_2 sse4.1|sse4_1 dca pcid pdcm xtpr cx16 fma cid ssse3 tm2 est smx vmx ds_cpl monitor dtes64 pclmulqdq|pclmuldq pni|sse3
  extf_edx: 3dnow 3dnowext lm|i64 rdtscp pdpe1gb fxsr_opt|ffxsr fxsr mmx mmxext nx|xd pse36 pat cmov mca pge mtrr syscall apic cx8 mce pae msr tsc pse de vme fpu
  extf_ecx: perfctr_nb perfctr_core topoext tbm nodeid_msr tce fma4 lwp wdt skinit xop ibs osvw 3dnowprefetch misalignsse sse4a abm cr8legacy extapic svm cmp_legacy lahf_lm

And:

virsh -r capabilities
<capabilities>

  <host>
    <uuid>44454c4c-4400-104d-8030-cac04f584731</uuid>
    <cpu>
      <arch>x86_64</arch>
      <model>Penryn</model>
      <vendor>Intel</vendor>
      <topology sockets='1' cores='2' threads='1'/>
      <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/>
    </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='2'>
            <cpu ...
(more)
edit retag flag offensive close merge delete

Comments

Have you enabled virtualization in the BIOS for the chip? What is the actual error message in nova compute when you try to launch an instance? If it has hvm in the TRACE then it may be due to intel VT not being enabled.

mpetason gravatar imagempetason ( 2014-07-15 12:51:05 -0500 )edit

3 answers

Sort by ยป oldest newest most voted
1

answered 2014-07-10 08:23:24 -0500

dwyaneini gravatar image

you can set

libvirt_cpu_mode=host-passthrough

in nova.conf. It helps me to solve this problem. Hope this will help you, too.

edit flag offensive delete link more
0

answered 2013-08-19 16:09:45 -0500

koolhead17 gravatar image

It simply means you are using wrong package and it is not supported for your architecture. Kindly see the official Centos site and try to understand if they have package available for your architecture..

edit flag offensive delete link more

Comments

So I need to get another libvirt package for CentOS that support my architecture. Is that what you mean? Many thanks for you help.

liriarte gravatar imageliriarte ( 2013-08-20 07:25:29 -0500 )edit

Can you help me please?

liriarte gravatar imageliriarte ( 2013-08-29 03:32:12 -0500 )edit
-1

answered 2014-05-01 04:38:50 -0500

Any one got resolution for this case ? I meet with the exact error... and struggling to go forward !!

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2013-08-09 09:26:46 -0500

Seen: 3,887 times

Last updated: Jul 10 '14