[libvirt] qemu64 - not valid cpu with 'Intel Westmere Family'

[Sandro Bonazzola]

Il 03/07/2013 18:28, Dan Kenigsberg ha scritto:
> On Wed, Jul 03, 2013 at 04:51:30PM +0200, Sandro Bonazzola wrote:
>> Il 03/07/2013 16:40, Sandro Bonazzola ha scritto:
>>> Hi,
>>> I'm trying to run latest vdsm master on RHEL-6.4.
>>> I've built the rpms against livirt-1.10    
>>>
>>> I'm creating a VM using cpu family = 'Intel Westmere Family'
>>>
>>> <cpu match="exact">
>>>      <model>qemu64</model>
>>>      <feature name="svm" policy="disable"/>
>>> </cpu>
>>>
>>> Thread-40::DEBUG::2013-07-03
>>> 15:47:47,150::libvirtconnection::136::vds::(wrapper) Unknown
>>> libvirterror: ecode: 1 edom: 31 level: 2 message: internal error Cannot
>>> find suitable CPU model for given data
>>> Thread-40::DEBUG::2013-07-03
>>> 15:47:47,150::vm::2003::vm.Vm::(_startUnderlyingVm)
>>> vmId=`9deae1fb-e0c5-4362-8f3c-657f39893b8b`::_ongoingCreations released
>>> Thread-40::ERROR::2013-07-03
>>> 15:47:47,150::vm::2029::vm.Vm::(_startUnderlyingVm)
>>> vmId=`9deae1fb-e0c5-4362-8f3c-657f39893b8b`::The vm start process failed
>>> Traceback (most recent call last):
>>>   File "/usr/share/vdsm/vm.py", line 1989, in _startUnderlyingVm
>>>     self._run()
>>>   File "/usr/share/vdsm/vm.py", line 2862, in _run
>>>     self._connection.createXML(domxml, flags),
>>>   File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py",
>>> line 112, in wrapper
>>>     ret = f(*args, **kwargs)
>>>   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2848, in
>>> createXML
>>>     if ret is None:raise libvirtError('virDomainCreateXML() failed',
>>> conn=self)
>>> libvirtError: internal error Cannot find suitable CPU model for given data
>>>
>>>
>>> Is it required a more updated qemu? Is it a vdsm or a livirt bug?
>>
>> It seems that qemu knows qemu64 as cpu
>>
>> #  /usr/libexec/qemu-kvm  --cpu ?
> And what does `virsh -r capabilities` report?



# virsh -r capabilities
<capabilities>

  <host>
    <uuid>3f8f4b81-f54b-4e49-8fe1-a55618c9c5f6</uuid>
    <cpu>
      <arch>x86_64</arch>
      <model>SandyBridge</model>
      <vendor>Intel</vendor>
      <topology sockets='1' cores='4' threads='2'/>
      <feature name='erms'/>
      <feature name='smep'/>
      <feature name='fsgsbase'/>
      <feature name='rdrand'/>
      <feature name='f16c'/>
      <feature name='osxsave'/>
      <feature name='pcid'/>
      <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'>
          <memory unit='KiB'>16661036</memory>
          <cpus num='8'>
            <cpu id='0' socket_id='0' core_id='0' siblings='0,4'/>
            <cpu id='1' socket_id='0' core_id='1' siblings='1,5'/>
            <cpu id='2' socket_id='0' core_id='2' siblings='2,6'/>
            <cpu id='3' socket_id='0' core_id='3' siblings='3,7'/>
            <cpu id='4' socket_id='0' core_id='0' siblings='0,4'/>
            <cpu id='5' socket_id='0' core_id='1' siblings='1,5'/>
            <cpu id='6' socket_id='0' core_id='2' siblings='2,6'/>
            <cpu id='7' socket_id='0' core_id='3' siblings='3,7'/>
          </cpus>
        </cell>
      </cells>
    </topology>
    <secmodel>
      <model>selinux</model>
      <doi>0</doi>
    </secmodel>
    <secmodel>
      <model>dac</model>
      <doi>0</doi>
    </secmodel>
  </host>

  <guest>
    <os_type>hvm</os_type>
    <arch name='i686'>
      <wordsize>32</wordsize>
      <emulator>/usr/libexec/qemu-kvm</emulator>
      <machine>rhel6.4.0</machine>
      <machine canonical='rhel6.4.0'>pc</machine>
      <machine>rhel6.3.0</machine>
      <machine>rhel6.2.0</machine>
      <machine>rhel6.1.0</machine>
      <machine>rhel6.0.0</machine>
      <machine>rhel5.5.0</machine>
      <machine>rhel5.4.4</machine>
      <machine>rhel5.4.0</machine>
      <domain type='qemu'>
      </domain>
      <domain type='kvm'>
        <emulator>/usr/libexec/qemu-kvm</emulator>
      </domain>
    </arch>
    <features>
      <cpuselection/>
      <deviceboot/>
      <acpi default='on' toggle='yes'/>
      <apic default='on' toggle='no'/>
      <pae/>
      <nonpae/>
    </features>
  </guest>

  <guest>
    <os_type>hvm</os_type>
    <arch name='x86_64'>
      <wordsize>64</wordsize>
      <emulator>/usr/libexec/qemu-kvm</emulator>
      <machine>rhel6.4.0</machine>
      <machine canonical='rhel6.4.0'>pc</machine>
      <machine>rhel6.3.0</machine>
      <machine>rhel6.2.0</machine>
      <machine>rhel6.1.0</machine>
      <machine>rhel6.0.0</machine>
      <machine>rhel5.5.0</machine>
      <machine>rhel5.4.4</machine>
      <machine>rhel5.4.0</machine>
      <domain type='qemu'>
      </domain>
      <domain type='kvm'>
        <emulator>/usr/libexec/qemu-kvm</emulator>
      </domain>
    </arch>
    <features>
      <cpuselection/>
      <deviceboot/>
      <acpi default='on' toggle='yes'/>
      <apic default='on' toggle='no'/>
    </features>
  </guest>

</capabilities>




> Is there something interesting in /var/log/libvirtd.log?
>
Attached today log, same error.





-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: libvirtd.log.gz
Type: application/gzip
Size: 25421 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20130704/fac1c37f/attachment-0001.gz>