[ovirt-users] Cannot find suitable CPU model for given data

[Hoot Thompson]

When trying to launch a Centos6.5 VM (pulled from
ovirt-image-repository) onto a Westmere (Dell 6100)
host through oVirt, the following error occurs from
libvirt:

3312: warning : x86Decode:1517 : Preferred CPU model Westmere not 
allowed by hypervisor; closest supported model will be used
3312: error : x86Decode:1573 : internal error: Cannot find suitable CPU 
model for given data


Googling the issue yeilds:
https://bugzilla.redhat.com/show_bug.cgi?id=804224

System info as Virsh sees it.

$virsh capabilities

  
6622b24b-5019-4644-af20-289533f0a7bc

  x86_64
  Westmere
  Intel

CPUs qemu-kvm supports.

$/usr/libexec/qemu-kvm -cpu "?" -nodefconfig
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
x86kvm64  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

CPU model name from /proc/cpu

Intel(R) Xeon(R) CPU X5660 @ 2.80GHz


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Cannot find suitable CPU model for given data

[Thompson, John H. (GSFC-606.2)[Computer Sciences Corporation]]

When trying to launch a Centos6.5 VM (pulled from
ovirt-image-repository) onto a Westmere (Dell 6100)
host through oVirt, the following error occurs from
libvirt:

3312: warning : x86Decode:1517 : Preferred CPU model Westmere not allowed by
hypervisor; closest supported model will be used
3312: error : x86Decode:1573 : internal error: Cannot find suitable CPU
model for given data

Googling the issue yeilds:
https://bugzilla.redhat.com/show_bug.cgi?id=804224

System info as Virsh sees it.

$virsh capabilities

  
6622b24b-5019-4644-af20-289533f0a7bc

  x86_64
  Westmere
  Intel

CPUs qemu-kvm supports.

$/usr/libexec/qemu-kvm -cpu "?" -nodefconfig
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
x86kvm64  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

CPU model name from /proc/cpu

Intel(R) Xeon(R) CPU X5660 @ 2.80GHz




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Cannot find suitable CPU model for given data

[Cristian Falcas]

On Tue, Dec 11, 2012 at 11:17 PM, Itamar Heim  wrote:

> On 12/11/2012 11:09 PM, Cristian Falcas wrote:
>
>>
>>
>>
>> On Mon, Dec 10, 2012 at 2:22 PM, Roy Golan > > wrote:
>>
>> On 12/10/2012 02:04 PM, Cristian Falcas wrote:
>>
>>>
>>>
>>>
>>> On Mon, Dec 10, 2012 at 9:30 AM, Itamar Heim >> > wrote:
>>>
>>> On 12/09/2012 11:22 PM, Cristian Falcas wrote:
>>>
>>>
>>>
>>>
>>> On Sun, Dec 9, 2012 at 5:37 PM, Roy Golan
>>> mailto:rgo...@redhat.com>
>>> >>
>>> wrote:
>>>
>>> On 12/09/2012 05:17 PM, Cristian Falcas wrote:
>>>
>>> Hi,
>>>
>>> I get this error with the nightly builds when I
>>> start a VM:
>>>
>>>
>>>   please paste the output of the following command to
>>> see if
>>> Opteron_G3 is really supported:
>>>vdsClient 0 -s getVdsCaps
>>>
>>>
>>> libvirtError: internal error Cannot find suitable
>>> CPU model for
>>> given data
>>>
>>>
>>> Log data:
>>> Thread-654::DEBUG::2012-12-09
>>> 17:14:18,120::libvirtvm::1485:**:vm.Vm::(_run)
>>> vmId=`a4a8f349-7fdf-42f4-873e-**e70f692c6ca2`::>> version="1.0"
>>> encoding="utf-8"?>
>>> 
>>> q
>>> a4a8f349-7fdf-42f4-873e-**e70f692c6ca2
>>> 524288
>>> 524288
>>> 2
>>> 
>>> 
>>> >> name="com.redhat.rhevm.vdsm"
>>> type="virtio"/>
>>> >>
>>> path="/var/lib/libvirt/qemu/**
>>> channels/q.com.redhat.rhevm.**vdsm"/>
>>> 
>>> 
>>> >> name="org.qemu.guest_agent.0"
>>> type="virtio"/>
>>> >>
>>> path="/var/lib/libvirt/qemu/**channels/q.org.qemu.guest_
>>> **agent.0"/>
>>> 
>>> 
>>> 
>>> >> name="com.redhat.spice.0"
>>> type="virtio"/>
>>> 
>>> >> keymap="en-us" listen="0"
>>> passwd="*" passwdValidTo="1970-01-01T00:**00:01"
>>> port="-1"
>>> tlsPort="-1" type="spice">
>>> >> name="main"/>
>>> >> name="inputs"/>
>>> >> name="cursor"/>
>>> >> name="playback"/>
>>> >> name="record"/>
>>> >> name="display"/>
>>> >> name="usbredir"/>
>>> >> name="smartcard"/>
>>> 
>>> 
>>> >> type="virtio"/>
>>> 
>>> 
>>> 
>>> >> type="qxl" vram="65536"/>
>>> 
>>> 
>>> >> address="00:1a:4a:6f:6f:f4"/>
>>> 
>>> 
>>> >> filter="vdsm-no-mac-spoofing"/**>
>>> 
>>> 
>>> >> type="file">
>>> >>
>>> file="/rhev/data-center/**21ddcd50-aba8-461a-9ecf-**
>>> c5762af89355/4f6a2b90-9c70-**45e5-8b17-5274ee97ce73/images/**
>>> ----**/CentOS-6.3-x86_**64-bin-DVD1.iso"
>>> startupPolicy="optional"/>
>>> 
>>> 
>

Re: [Users] Cannot find suitable CPU model for given data

[Itamar Heim]

On 12/11/2012 11:09 PM, Cristian Falcas wrote:




On Mon, Dec 10, 2012 at 2:22 PM, Roy Golan mailto:rgo...@redhat.com>> wrote:

On 12/10/2012 02:04 PM, Cristian Falcas wrote:




On Mon, Dec 10, 2012 at 9:30 AM, Itamar Heim mailto:ih...@redhat.com>> wrote:

On 12/09/2012 11:22 PM, Cristian Falcas wrote:




On Sun, Dec 9, 2012 at 5:37 PM, Roy Golan
mailto:rgo...@redhat.com>
>> wrote:

On 12/09/2012 05:17 PM, Cristian Falcas wrote:

Hi,

I get this error with the nightly builds when I
start a VM:


  please paste the output of the following command to
see if
Opteron_G3 is really supported:
   vdsClient 0 -s getVdsCaps


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


Log data:
Thread-654::DEBUG::2012-12-09
17:14:18,120::libvirtvm::1485::vm.Vm::(_run)
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::

q
a4a8f349-7fdf-42f4-873e-e70f692c6ca2
524288
524288
2















































ffa8728f-6f0c-4b59-99ac-5bef0bd7634e




hvm




oVirt
oVirt Node
17-1
30303146-4430-3946-3139-3938
a4a8f349-7fdf-42f4-873e-e70f692c6ca2









Opteron_G3




Thread-654::DEBUG::2012-12-09
17:14:18,152::vm::672::vm.Vm::(_startUnderlyingVm)

vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::_ongoingCreations
released
Thread-654::ERROR::2012-12-09
17:14:18,152::vm::696::vm.Vm::(_startUnderlyingVm)
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::The
vm start process
failed
Traceback (most recent call last):
  File "/usr/share/vdsm/vm.py",

Re: [Users] Cannot find suitable CPU model for given data

[Roy Golan]

On 12/10/2012 02:04 PM, Cristian Falcas wrote:




On Mon, Dec 10, 2012 at 9:30 AM, Itamar Heim > wrote:


On 12/09/2012 11:22 PM, Cristian Falcas wrote:




On Sun, Dec 9, 2012 at 5:37 PM, Roy Golan mailto:rgo...@redhat.com>
>> wrote:

On 12/09/2012 05:17 PM, Cristian Falcas wrote:

Hi,

I get this error with the nightly builds when I start
a VM:


  please paste the output of the following command to see if
Opteron_G3 is really supported:
   vdsClient 0 -s getVdsCaps


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


Log data:
Thread-654::DEBUG::2012-12-09
17:14:18,120::libvirtvm::1485::vm.Vm::(_run)
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::

q
a4a8f349-7fdf-42f4-873e-e70f692c6ca2
524288
524288
2



   
path="/var/lib/libvirt/qemu/channels/q.com.redhat.rhevm.vdsm"/>




   
path="/var/lib/libvirt/qemu/channels/q.org.qemu.guest_agent.0"/>































   
file="/rhev/data-center/21ddcd50-aba8-461a-9ecf-c5762af89355/4f6a2b90-9c70-45e5-8b17-5274ee97ce73/images/----/CentOS-6.3-x86_64-bin-DVD1.iso"

startupPolicy="optional"/>






   
file="/rhev/data-center/21ddcd50-aba8-461a-9ecf-c5762af89355/81361e6d-2b58-4781-80c2-d908a0fe91cd/images/ffa8728f-6f0c-4b59-99ac-5bef0bd7634e/80a8701a-bf07-4d8a-8d02-8f98e6bb46a1"/>


ffa8728f-6f0c-4b59-99ac-5bef0bd7634e




hvm




oVirt
oVirt
Node
17-1
30303146-4430-3946-3139-3938
a4a8f349-7fdf-42f4-873e-e70f692c6ca2









Opteron_G3




Thread-654::DEBUG::2012-12-09
17:14:18,152::vm::672::vm.Vm::(_startUnderlyingVm)
   
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::_ongoingCreations

released
Thread-654::ERROR::2012-12-09
17:14:18,152::vm::696::vm.Vm::(_startUnderlyingVm)
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::The vm
start process
failed
Traceback

Re: [Users] Cannot find suitable CPU model for given data

[Cristian Falcas]

On Mon, Dec 10, 2012 at 9:30 AM, Itamar Heim  wrote:

> On 12/09/2012 11:22 PM, Cristian Falcas wrote:
>
>>
>>
>>
>> On Sun, Dec 9, 2012 at 5:37 PM, Roy Golan > > wrote:
>>
>> On 12/09/2012 05:17 PM, Cristian Falcas wrote:
>>
>>> Hi,
>>>
>>> I get this error with the nightly builds when I start a VM:
>>>
>>
>>   please paste the output of the following command to see if
>> Opteron_G3 is really supported:
>>vdsClient 0 -s getVdsCaps
>>
>>>
>>> libvirtError: internal error Cannot find suitable CPU model for
>>> given data
>>>
>>>
>>> Log data:
>>> Thread-654::DEBUG::2012-12-09
>>> 17:14:18,120::libvirtvm::1485:**:vm.Vm::(_run)
>>> vmId=`a4a8f349-7fdf-42f4-873e-**e70f692c6ca2`::>> encoding="utf-8"?>
>>> 
>>> q
>>> a4a8f349-7fdf-42f4-873e-**e70f692c6ca2
>>> 524288
>>> 524288
>>> 2
>>> 
>>> 
>>> >> type="virtio"/>
>>> >> path="/var/lib/libvirt/qemu/**channels/q.com.redhat.rhevm.**vdsm"/>
>>> 
>>> 
>>> >> type="virtio"/>
>>> >> path="/var/lib/libvirt/qemu/**channels/q.org.qemu.guest_**agent.0"/>
>>> 
>>> 
>>> 
>>> >> type="virtio"/>
>>> 
>>> >> passwd="*" passwdValidTo="1970-01-01T00:**00:01" port="-1"
>>> tlsPort="-1" type="spice">
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> >> file="/rhev/data-center/**21ddcd50-aba8-461a-9ecf-**
>>> c5762af89355/4f6a2b90-9c70-**45e5-8b17-5274ee97ce73/images/**
>>> ----**/CentOS-6.3-x86_**64-bin-DVD1.iso"
>>> startupPolicy="optional"/>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> >> file="/rhev/data-center/**21ddcd50-aba8-461a-9ecf-**
>>> c5762af89355/81361e6d-2b58-**4781-80c2-d908a0fe91cd/images/**
>>> ffa8728f-6f0c-4b59-99ac-**5bef0bd7634e/80a8701a-bf07-**
>>> 4d8a-8d02-8f98e6bb46a1"/>
>>> 
>>> ffa8728f-6f0c-4b59-**99ac-5bef0bd7634e
>>> >> io="threads" name="qemu" type="raw"/>
>>> 
>>> 
>>> 
>>> hvm
>>> 
>>> 
>>> 
>>> 
>>> oVirt
>>> oVirt Node
>>> 17-1
>>> >> name="serial">30303146-4430-**3946-3139-3938
>>> >> name="uuid">a4a8f349-7fdf-**42f4-873e-e70f692c6ca2
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> Opteron_G3
>>> 
>>> 
>>> 
>>>
>>> Thread-654::DEBUG::2012-12-09
>>> 17:14:18,152::vm::672::vm.Vm::**(_startUnderlyingVm)
>>> vmId=`a4a8f349-7fdf-42f4-873e-**e70f692c6ca2`::_**ongoingCreations
>>> released
>>> Thread-654::ERROR::2012-12-09
>>> 17:14:18,152::vm::696::vm.Vm::**(_startUnderlyingVm)
>>> vmId=`a4a8f349-7fdf-42f4-873e-**e70f692c6ca2`::The vm start process
>>> failed
>>> Traceback (most recent call last):
>>>   File "/usr/share/vdsm/vm.py", line 658, in _startUnderlyingVm
>>> self._run()
>>>   File "/usr/share/vdsm/libvirtvm.py"**, line 1511, in _run
>>> self._connection.createXML(**domxml, flags),
>>>   File
>>> "/usr/lib64/python2.7/site-**packages/vdsm/**libvirtconnection.py",
>>> line 111, in wrapper
>>> ret = f(*args, **kwargs)
>>>   File "/usr/lib64/python2.7/site-**packages/libvirt.py", line 2633,
>>> in createXML
>>> if ret is None:raise libvirtError('**virDomainCreateXML()
>>> failed', conn=self)
>>> libvirtError: internal error Cannot find suitable CPU model

Re: [Users] Cannot find suitable CPU model for given data

[Itamar Heim]

On 12/09/2012 11:22 PM, Cristian Falcas wrote:




On Sun, Dec 9, 2012 at 5:37 PM, Roy Golan mailto:rgo...@redhat.com>> wrote:

On 12/09/2012 05:17 PM, Cristian Falcas wrote:

Hi,

I get this error with the nightly builds when I start a VM:


  please paste the output of the following command to see if
Opteron_G3 is really supported:
   vdsClient 0 -s getVdsCaps


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


Log data:
Thread-654::DEBUG::2012-12-09
17:14:18,120::libvirtvm::1485::vm.Vm::(_run)
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::

q
a4a8f349-7fdf-42f4-873e-e70f692c6ca2
524288
524288
2















































ffa8728f-6f0c-4b59-99ac-5bef0bd7634e




hvm




oVirt
oVirt Node
17-1
30303146-4430-3946-3139-3938
a4a8f349-7fdf-42f4-873e-e70f692c6ca2









Opteron_G3




Thread-654::DEBUG::2012-12-09
17:14:18,152::vm::672::vm.Vm::(_startUnderlyingVm)
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::_ongoingCreations
released
Thread-654::ERROR::2012-12-09
17:14:18,152::vm::696::vm.Vm::(_startUnderlyingVm)
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::The vm start process
failed
Traceback (most recent call last):
  File "/usr/share/vdsm/vm.py", line 658, in _startUnderlyingVm
self._run()
  File "/usr/share/vdsm/libvirtvm.py", line 1511, in _run
self._connection.createXML(domxml, flags),
  File
"/usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py",
line 111, in wrapper
ret = f(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2633,
in createXML
if ret is None:raise libvirtError('virDomainCreateXML()
failed', conn=self)
libvirtError: internal error Cannot find suitable CPU model for
given data
Thread-654::DEBUG::2012-12-09
17:14:18,156::vm::1045::vm.Vm::(setDownStatus)
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::Changed state to
Down: internal error Cannot find suitable CPU model for given data



___
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




The command
vdsClient 0 -s getVdsCaps
didn't work

Is this the same thing?

[root@localhost cristi]# vdsClient -s localhost getVdsCaps
 HBAInventory = {'iSCSI': [{'InitiatorName':
'iqn.1994-05.com.redhat:74bc7d9e76f3'}], 'FC': []}
 ISCSIInitiatorName = iqn.1994-05.com.redhat:74bc7d9e76f3
 bondings = {'bond4': {'addr': '', 'cfg': {}, 'mtu': '1500',
'netmask': '', 'slaves': [], 'hwaddr': '00:00:00:00:00:00'}, 'bond0':
{'addr': '', 'cfg': {}, 'mtu': '1500', 'netmask': '', 'slaves': [],
'hwaddr': '00:00:00:00:00:00'}}
 bridges = {'ovirtmgmt': {'addr': '10.20.20.20', 'cfg': {'VLAN':
'yes', 'IPV6INIT': 'no', 'IPADDR0': '10.20.20.20', 'DNS1': '8.8.8.8',
'PREFIX0': '24', 'DEFROUTE': 'yes', 'IPV4_FAILURE_FATAL': 'no', 'DELAY':
'0', 'NM_CONTROLLED': 'no', 'BOOTPROTO': 'none', 'GATEWAY0':
'10.20.20.1', 'DEVICE': 'ovirtmgmt', 'TYPE': 'Brid

Re: [Users] Cannot find suitable CPU model for given data

[Cristian Falcas]

On Sun, Dec 9, 2012 at 5:37 PM, Roy Golan  wrote:

>  On 12/09/2012 05:17 PM, Cristian Falcas wrote:
>
> Hi,
>
> I get this error with the nightly builds when I start a VM:
>
>
>  please paste the output of the following command to see if Opteron_G3 is
> really supported:
>   vdsClient 0 -s getVdsCaps
>
>
> libvirtError: internal error Cannot find suitable CPU model for given data
>
>
> Log data:
> Thread-654::DEBUG::2012-12-09 17:14:18,120::libvirtvm::1485::vm.Vm::(_run)
> vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`:: encoding="utf-8"?>
> 
> q
> a4a8f349-7fdf-42f4-873e-e70f692c6ca2
> 524288
> 524288
> 2
> 
> 
>  type="virtio"/>
>  path="/var/lib/libvirt/qemu/channels/q.com.redhat.rhevm.vdsm"/>
> 
> 
>  type="virtio"/>
>  path="/var/lib/libvirt/qemu/channels/q.org.qemu.guest_agent.0"/>
> 
> 
> 
> 
> 
>  passwd="*" passwdValidTo="1970-01-01T00:00:01" port="-1" tlsPort="-1"
> type="spice">
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  file="/rhev/data-center/21ddcd50-aba8-461a-9ecf-c5762af89355/4f6a2b90-9c70-45e5-8b17-5274ee97ce73/images/----/CentOS-6.3-x86_64-bin-DVD1.iso"
> startupPolicy="optional"/>
> 
> 
> 
> 
> 
> 
>  file="/rhev/data-center/21ddcd50-aba8-461a-9ecf-c5762af89355/81361e6d-2b58-4781-80c2-d908a0fe91cd/images/ffa8728f-6f0c-4b59-99ac-5bef0bd7634e/80a8701a-bf07-4d8a-8d02-8f98e6bb46a1"/>
> 
>
> ffa8728f-6f0c-4b59-99ac-5bef0bd7634e
>  io="threads" name="qemu" type="raw"/>
> 
> 
> 
> hvm
> 
> 
> 
> 
> oVirt
> oVirt Node
> 17-1
>  name="serial">30303146-4430-3946-3139-3938
>  name="uuid">a4a8f349-7fdf-42f4-873e-e70f692c6ca2
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Opteron_G3
> 
> 
> 
>
> Thread-654::DEBUG::2012-12-09
> 17:14:18,152::vm::672::vm.Vm::(_startUnderlyingVm)
> vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::_ongoingCreations released
> Thread-654::ERROR::2012-12-09
> 17:14:18,152::vm::696::vm.Vm::(_startUnderlyingVm)
> vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::The vm start process failed
> Traceback (most recent call last):
>   File "/usr/share/vdsm/vm.py", line 658, in _startUnderlyingVm
> self._run()
>   File "/usr/share/vdsm/libvirtvm.py", line 1511, in _run
> self._connection.createXML(domxml, flags),
>   File "/usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py",
> line 111, in wrapper
> ret = f(*args, **kwargs)
>   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2633, in
> createXML
> if ret is None:raise libvirtError('virDomainCreateXML() failed',
> conn=self)
> libvirtError: internal error Cannot find suitable CPU model for given data
> Thread-654::DEBUG::2012-12-09
> 17:14:18,156::vm::1045::vm.Vm::(setDownStatus)
> vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::Changed state to Down:
> internal error Cannot find suitable CPU model for given data
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>

I don't think I have aes on my CPU:
grep aes /proc/cpuinfo

Bu I have nx enabled and I didn't found any way to disable it from bios.

The thing is, it worked until recently. I will downgrade libvirt to see if
it will fix this.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Cannot find suitable CPU model for given data

[Cristian Falcas]

On Sun, Dec 9, 2012 at 5:37 PM, Roy Golan  wrote:

>  On 12/09/2012 05:17 PM, Cristian Falcas wrote:
>
> Hi,
>
> I get this error with the nightly builds when I start a VM:
>
>
>  please paste the output of the following command to see if Opteron_G3 is
> really supported:
>   vdsClient 0 -s getVdsCaps
>
>
> libvirtError: internal error Cannot find suitable CPU model for given data
>
>
> Log data:
> Thread-654::DEBUG::2012-12-09 17:14:18,120::libvirtvm::1485::vm.Vm::(_run)
> vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`:: encoding="utf-8"?>
> 
> q
> a4a8f349-7fdf-42f4-873e-e70f692c6ca2
> 524288
> 524288
> 2
> 
> 
>  type="virtio"/>
>  path="/var/lib/libvirt/qemu/channels/q.com.redhat.rhevm.vdsm"/>
> 
> 
>  type="virtio"/>
>  path="/var/lib/libvirt/qemu/channels/q.org.qemu.guest_agent.0"/>
> 
> 
> 
> 
> 
>  passwd="*" passwdValidTo="1970-01-01T00:00:01" port="-1" tlsPort="-1"
> type="spice">
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  file="/rhev/data-center/21ddcd50-aba8-461a-9ecf-c5762af89355/4f6a2b90-9c70-45e5-8b17-5274ee97ce73/images/----/CentOS-6.3-x86_64-bin-DVD1.iso"
> startupPolicy="optional"/>
> 
> 
> 
> 
> 
> 
>  file="/rhev/data-center/21ddcd50-aba8-461a-9ecf-c5762af89355/81361e6d-2b58-4781-80c2-d908a0fe91cd/images/ffa8728f-6f0c-4b59-99ac-5bef0bd7634e/80a8701a-bf07-4d8a-8d02-8f98e6bb46a1"/>
> 
>
> ffa8728f-6f0c-4b59-99ac-5bef0bd7634e
>  io="threads" name="qemu" type="raw"/>
> 
> 
> 
> hvm
> 
> 
> 
> 
> oVirt
> oVirt Node
> 17-1
>  name="serial">30303146-4430-3946-3139-3938
>  name="uuid">a4a8f349-7fdf-42f4-873e-e70f692c6ca2
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Opteron_G3
> 
> 
> 
>
> Thread-654::DEBUG::2012-12-09
> 17:14:18,152::vm::672::vm.Vm::(_startUnderlyingVm)
> vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::_ongoingCreations released
> Thread-654::ERROR::2012-12-09
> 17:14:18,152::vm::696::vm.Vm::(_startUnderlyingVm)
> vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::The vm start process failed
> Traceback (most recent call last):
>   File "/usr/share/vdsm/vm.py", line 658, in _startUnderlyingVm
> self._run()
>   File "/usr/share/vdsm/libvirtvm.py", line 1511, in _run
> self._connection.createXML(domxml, flags),
>   File "/usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py",
> line 111, in wrapper
> ret = f(*args, **kwargs)
>   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2633, in
> createXML
> if ret is None:raise libvirtError('virDomainCreateXML() failed',
> conn=self)
> libvirtError: internal error Cannot find suitable CPU model for given data
> Thread-654::DEBUG::2012-12-09
> 17:14:18,156::vm::1045::vm.Vm::(setDownStatus)
> vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::Changed state to Down:
> internal error Cannot find suitable CPU model for given data
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


The command
vdsClient 0 -s getVdsCaps
didn't work

Is this the same thing?

[root@localhost cristi]# vdsClient -s localhost getVdsCaps
HBAInventory = {'iSCSI': [{'InitiatorName':
'iqn.1994-05.com.redhat:74bc7d9e76f3'}], 'FC': []}
ISCSIInitiatorName = iqn.1994-05.com.redhat:74bc7d9e76f3
bondings = {'bond4': {'addr': '', 'cfg': {}, 'mtu': '1500',
'netmask': '', 'slaves': [], 'hwaddr': '00:00:00:00:00:00'}, 'bond0':
{'addr': '', 'cfg': {}, 'mtu': '1500', 'netmask': '', 'slaves': [],
'hwaddr': '00:00:0

Re: [Users] Cannot find suitable CPU model for given data

[Roy Golan]

On 12/09/2012 05:17 PM, Cristian Falcas wrote:

Hi,

I get this error with the nightly builds when I start a VM:


 please paste the output of the following command to see if Opteron_G3 
is really supported:

  vdsClient 0 -s getVdsCaps


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


Log data:
Thread-654::DEBUG::2012-12-09 
17:14:18,120::libvirtvm::1485::vm.Vm::(_run) 
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::encoding="utf-8"?>


q
a4a8f349-7fdf-42f4-873e-e70f692c6ca2
524288
524288
2


type="virtio"/>
path="/var/lib/libvirt/qemu/channels/q.com.redhat.rhevm.vdsm"/>



type="virtio"/>
path="/var/lib/libvirt/qemu/channels/q.org.qemu.guest_agent.0"/>






passwd="*" passwdValidTo="1970-01-01T00:00:01" port="-1" 
tlsPort="-1" type="spice">

























file="/rhev/data-center/21ddcd50-aba8-461a-9ecf-c5762af89355/4f6a2b90-9c70-45e5-8b17-5274ee97ce73/images/----/CentOS-6.3-x86_64-bin-DVD1.iso" 
startupPolicy="optional"/>







file="/rhev/data-center/21ddcd50-aba8-461a-9ecf-c5762af89355/81361e6d-2b58-4781-80c2-d908a0fe91cd/images/ffa8728f-6f0c-4b59-99ac-5bef0bd7634e/80a8701a-bf07-4d8a-8d02-8f98e6bb46a1"/>


ffa8728f-6f0c-4b59-99ac-5bef0bd7634e
io="threads" name="qemu" type="raw"/>




hvm




oVirt
oVirt Node
17-1
name="serial">30303146-4430-3946-3139-3938
name="uuid">a4a8f349-7fdf-42f4-873e-e70f692c6ca2










Opteron_G3




Thread-654::DEBUG::2012-12-09 
17:14:18,152::vm::672::vm.Vm::(_startUnderlyingVm) 
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::_ongoingCreations released
Thread-654::ERROR::2012-12-09 
17:14:18,152::vm::696::vm.Vm::(_startUnderlyingVm) 
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::The vm start process failed

Traceback (most recent call last):
  File "/usr/share/vdsm/vm.py", line 658, in _startUnderlyingVm
self._run()
  File "/usr/share/vdsm/libvirtvm.py", line 1511, in _run
self._connection.createXML(domxml, flags),
  File "/usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py", 
line 111, in wrapper

ret = f(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2633, in 
createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed', 
conn=self)

libvirtError: internal error Cannot find suitable CPU model for given data
Thread-654::DEBUG::2012-12-09 
17:14:18,156::vm::1045::vm.Vm::(setDownStatus) 
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::Changed state to Down: 
internal error Cannot find suitable CPU model for given data




___
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] Cannot find suitable CPU model for given data

[Oved Ourfalli]

- Original Message -
> From: "Cristian Falcas" 
> To: users@ovirt.org
> Sent: Sunday, December 9, 2012 5:17:01 PM
> Subject: [Users] Cannot find suitable CPU model for given data
> 
> 
> Hi,
> 
> I get this error with the nightly builds when I start a VM:
> 
> libvirtError: internal error Cannot find suitable CPU model for given
> data
> 
> 
> Log data:
> Thread-654::DEBUG::2012-12-09
> 17:14:18,120::libvirtvm::1485::vm.Vm::(_run)
> vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`:: encoding="utf-8"?>
> 
> q
> a4a8f349-7fdf-42f4-873e-e70f692c6ca2
> 524288
> 524288
> 2
> 
> 
> 
>  path="/var/lib/libvirt/qemu/channels/q.com.redhat.rhevm.vdsm"/>
> 
> 
> 
>  path="/var/lib/libvirt/qemu/channels/q.org.qemu.guest_agent.0"/>
> 
> 
> 
> 
> 
>  passwdValidTo="1970-01-01T00:00:01" port="-1" tlsPort="-1"
> type="spice">
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  file="/rhev/data-center/21ddcd50-aba8-461a-9ecf-c5762af89355/4f6a2b90-9c70-45e5-8b17-5274ee97ce73/images/----/CentOS-6.3-x86_64-bin-DVD1.iso"
> startupPolicy="optional"/>
> 
> 
> 
> 
> 
> 
>  file="/rhev/data-center/21ddcd50-aba8-461a-9ecf-c5762af89355/81361e6d-2b58-4781-80c2-d908a0fe91cd/images/ffa8728f-6f0c-4b59-99ac-5bef0bd7634e/80a8701a-bf07-4d8a-8d02-8f98e6bb46a1"/>
> 
> ffa8728f-6f0c-4b59-99ac-5bef0bd7634e
>  type="raw"/>
> 
> 
> 
> hvm
> 
> 
> 
> 
> oVirt
> oVirt Node
> 17-1
> 30303146-4430-3946-3139-3938
> a4a8f349-7fdf-42f4-873e-e70f692c6ca2
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Opteron_G3
> 
> 
> 
> 
> Thread-654::DEBUG::2012-12-09
> 17:14:18,152::vm::672::vm.Vm::(_startUnderlyingVm)
> vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::_ongoingCreations
> released
> Thread-654::ERROR::2012-12-09
> 17:14:18,152::vm::696::vm.Vm::(_startUnderlyingVm)
> vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::The vm start process
> failed
> Traceback (most recent call last):
> File "/usr/share/vdsm/vm.py", line 658, in _startUnderlyingVm
> self._run()
> File "/usr/share/vdsm/libvirtvm.py", line 1511, in _run
> self._connection.createXML(domxml, flags),
> File "/usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py",
> line 111, in wrapper
> ret = f(*args, **kwargs)
> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2633, in
> createXML
> if ret is None:raise libvirtError('virDomainCreateXML() failed',
> conn=self)
> libvirtError: internal error Cannot find suitable CPU model for given
> data
> Thread-654::DEBUG::2012-12-09
> 17:14:18,156::vm::1045::vm.Vm::(setDownStatus)
> vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::Changed state to Down:
> internal error Cannot find suitable CPU model for given data
> 
> 
Not sure I'm pointing you at the right direction, but perhaps reading the 
following link will help:
http://wiki.libvirt.org/page/Libvirt_identifies_host_processor_as_a_different_model_from_the_hardware_documentation
(especially the last section).

Oved
> ___
> 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

[Users] Cannot find suitable CPU model for given data

[Cristian Falcas]

Hi,

I get this error with the nightly builds when I start a VM:

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


Log data:
Thread-654::DEBUG::2012-12-09 17:14:18,120::libvirtvm::1485::vm.Vm::(_run)
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::

q
a4a8f349-7fdf-42f4-873e-e70f692c6ca2
524288
524288
2
















































ffa8728f-6f0c-4b59-99ac-5bef0bd7634e




hvm




oVirt
oVirt Node
17-1
30303146-4430-3946-3139-3938
a4a8f349-7fdf-42f4-873e-e70f692c6ca2









Opteron_G3




Thread-654::DEBUG::2012-12-09
17:14:18,152::vm::672::vm.Vm::(_startUnderlyingVm)
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::_ongoingCreations released
Thread-654::ERROR::2012-12-09
17:14:18,152::vm::696::vm.Vm::(_startUnderlyingVm)
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::The vm start process failed
Traceback (most recent call last):
  File "/usr/share/vdsm/vm.py", line 658, in _startUnderlyingVm
self._run()
  File "/usr/share/vdsm/libvirtvm.py", line 1511, in _run
self._connection.createXML(domxml, flags),
  File "/usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py", line
111, in wrapper
ret = f(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2633, in
createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed',
conn=self)
libvirtError: internal error Cannot find suitable CPU model for given data
Thread-654::DEBUG::2012-12-09
17:14:18,156::vm::1045::vm.Vm::(setDownStatus)
vmId=`a4a8f349-7fdf-42f4-873e-e70f692c6ca2`::Changed state to Down:
internal error Cannot find suitable CPU model for given data
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users