----- Original Message -----
> From: "Cristian Falcas" <cristi.fal...@gmail.com>
> 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`::<?xml version="1.0"
> encoding="utf-8"?>
> <domain type="kvm">
> <name>q</name>
> <uuid>a4a8f349-7fdf-42f4-873e-e70f692c6ca2</uuid>
> <memory>524288</memory>
> <currentMemory>524288</currentMemory>
> <vcpu>2</vcpu>
> <devices>
> <channel type="unix">
> <target name="com.redhat.rhevm.vdsm" type="virtio"/>
> <source mode="bind"
> path="/var/lib/libvirt/qemu/channels/q.com.redhat.rhevm.vdsm"/>
> </channel>
> <channel type="unix">
> <target name="org.qemu.guest_agent.0" type="virtio"/>
> <source mode="bind"
> path="/var/lib/libvirt/qemu/channels/q.org.qemu.guest_agent.0"/>
> </channel>
> <input bus="ps2" type="mouse"/>
> <channel type="spicevmc">
> <target name="com.redhat.spice.0" type="virtio"/>
> </channel>
> <graphics autoport="yes" keymap="en-us" listen="0" passwd="*****"
> passwdValidTo="1970-01-01T00:00:01" port="-1" tlsPort="-1"
> type="spice">
> <channel mode="secure" name="main"/>
> <channel mode="secure" name="inputs"/>
> <channel mode="secure" name="cursor"/>
> <channel mode="secure" name="playback"/>
> <channel mode="secure" name="record"/>
> <channel mode="secure" name="display"/>
> <channel mode="secure" name="usbredir"/>
> <channel mode="secure" name="smartcard"/>
> </graphics>
> <console type="pty">
> <target port="0" type="virtio"/>
> </console>
> <sound model="ac97"/>
> <video>
> <model heads="1" type="qxl" vram="65536"/>
> </video>
> <interface type="bridge">
> <mac address="00:1a:4a:6f:6f:f4"/>
> <model type="virtio"/>
> <source bridge="ovirtmgmt"/>
> <filterref filter="vdsm-no-mac-spoofing"/>
> </interface>
> <memballoon model="virtio"/>
> <disk device="cdrom" snapshot="no" type="file">
> <source
> file="/rhev/data-center/21ddcd50-aba8-461a-9ecf-c5762af89355/4f6a2b90-9c70-45e5-8b17-5274ee97ce73/images/11111111-1111-1111-1111-111111111111/CentOS-6.3-x86_64-bin-DVD1.iso"
> startupPolicy="optional"/>
> <target bus="ide" dev="hdc"/>
> <readonly/>
> <serial></serial>
> <boot order="1"/>
> </disk>
> <disk device="disk" snapshot="no" type="file">
> <source
> 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"/>
> <target bus="virtio" dev="vda"/>
> <serial>ffa8728f-6f0c-4b59-99ac-5bef0bd7634e</serial>
> <driver cache="none" error_policy="stop" io="threads" name="qemu"
> type="raw"/>
> </disk>
> </devices>
> <os>
> <type arch="x86_64" machine="pc-0.14">hvm</type>
> <smbios mode="sysinfo"/>
> </os>
> <sysinfo type="smbios">
> <system>
> <entry name="manufacturer">oVirt</entry>
> <entry name="product">oVirt Node</entry>
> <entry name="version">17-1</entry>
> <entry name="serial">30303146-4430-3946-3139-3938FFFFFFFF</entry>
> <entry name="uuid">a4a8f349-7fdf-42f4-873e-e70f692c6ca2</entry>
> </system>
> </sysinfo>
> <clock adjustment="-43200" offset="variable">
> <timer name="rtc" tickpolicy="catchup"/>
> </clock>
> <features>
> <acpi/>
> </features>
> <cpu match="exact">
> <model>Opteron_G3</model>
> <topology cores="1" sockets="2" threads="1"/>
> </cpu>
> </domain>
>
> 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
