[ovirt-users] Problem with a second host: Exit message: internal error: Cannot find suitable CPU model for given data.

[Yedidyah Bar David]

----- Original Message -----
> From: "Julián Tete" <danteconrad14 at gmail.com>
> To: users at ovirt.org
> Sent: Sunday, April 26, 2015 5:41:30 PM
> Subject: [ovirt-users] Problem with a second host: Exit message: internal error: Cannot find suitable CPU model for
> given data.
> 
> Hello Friends of oVirt
> 
> I'd setup a oVirt enviroment (hosted-engine) on BladeCenter HS23 Blades
> 
> All the machines are CentOS 7.1
> 
> Engine FQDN: ovirt.udistritaloas.edu.co
> Second Host FQDN: sotara.udistritaloas.edu.co
> FQDN Host with the Host-Engine and with the Data Master Storage:
> patascoy.udistritaloas.edu.co
> 
> When I try to start a Virtual Machine on a second Host I get:
> 
> VM PrimeraMaquinaCentOS7 is down with error. Exit message: internal error:
> Cannot find suitable CPU model for given data.
> 
> Failed to run VM PrimeraMaquinaCentOS7 on Host sotara.udistritaloas.edu.co .
> 
> Failed to run VM PrimeraMaquinaCentOS7 (User: admin at internal).
> 
> Packages in the second Host:
> 
> vdsm-jsonrpc-4.16.10-8.gitc937927.el7.noarch
> vdsm-gluster-4.16.10-8.gitc937927.el7.noarch
> vdsm-python-4.16.10-8.gitc937927.el7.noarch
> vdsm-4.16.10-8.gitc937927.el7.x86_64
> vdsm-xmlrpc-4.16.10-8.gitc937927.el7.noarch
> vdsm-cli-4.16.10-8.gitc937927.el7.noarch
> vdsm-yajsonrpc-4.16.10-8.gitc937927.el7.noarch
> vdsm-python-zombiereaper-4.16.10-8.gitc937927.el7.noarch
> libvirt-daemon-driver-storage-1.2.8-16.el7_1.2.x86_64
> libvirt-daemon-kvm-1.2.8-16.el7_1.2.x86_64
> libvirt-daemon-1.2.8-16.el7_1.2.x86_64
> libvirt-daemon-driver-secret-1.2.8-16.el7_1.2.x86_64
> libvirt-python-1.2.8-7.el7_1.1.x86_64
> libvirt-gobject-0.1.7-3.el7.x86_64
> libvirt-glib-0.1.7-3.el7.x86_64
> libvirt-daemon-driver-network-1.2.8-16.el7_1.2.x86_64
> libvirt-client-1.2.8-16.el7_1.2.x86_64
> libvirt-lock-sanlock-1.2.8-16.el7_1.2.x86_64
> libvirt-gconfig-0.1.7-3.el7.x86_64
> libvirt-daemon-driver-nodedev-1.2.8-16.el7_1.2.x86_64
> libvirt-daemon-driver-interface-1.2.8-16.el7_1.2.x86_64
> libvirt-daemon-driver-qemu-1.2.8-16.el7_1.2.x86_64
> libvirt-daemon-driver-nwfilter-1.2.8-16.el7_1.2.x86_64
> libvirt-daemon-config-nwfilter-1.2.8-16.el7_1.2.x86_64
> qemu-kvm-common-rhev-1.5.3-60.el7_0.2.x86_64
> libvirt-daemon-kvm-1.2.8-16.el7_1.2.x86_64
> qemu-kvm-rhev-1.5.3-60.el7_0.2.x86_64
> qemu-kvm-tools-rhev-1.5.3-60.el7_0.2.x86_64
> ovirt-engine-sdk-python-3.5.1.0-1.el7.centos.noarch
> ovirt-hosted-engine-setup-1.2.2-1.el7.centos.noarch
> ovirt-hosted-engine-ha-1.2.5-1.el7.centos.noarch
> ovirt-release35-002-1.noarch
> ovirt-host-deploy-1.3.1-1.el7.noarch
> 
> Basic Second Host Information:
> 
> http://pastebin.com/KFWWtD9v
> 
> Second Host Relevant oVirt Information:
> 
> http://pastebin.com/Rvm9kNph
> 
> Engine Log:
> 
> http://pastebin.com/p7UK787e

Some random things to check/post:

Does this same VM work on the first host? Can you then
post relevant data on this first host?

Did you try changing the number of cpus allocated to it?

Can you try to copy/paste the generated domain xml from
vdsm.log and use that with virsh cpu-compare?

Thanks,
-- 
Didi