I always do this, maybe a oVirt bug ?

2015-05-12 0:28 GMT-05:00 Yedidyah Bar David <didi@redhat.com>:
----- Original Message -----
> From: "Julián Tete" <danteconrad14@gmail.com>
> To: "Yedidyah Bar David" <didi@redhat.com>
> Cc: users@ovirt.org
> Sent: Monday, May 11, 2015 7:46:40 PM
> Subject: Re: [SOLVED] [ovirt-users] Problem with a second host: Exit message: internal error: Cannot find suitable
> CPU model for given data.
>
> Hi Friends of oVirt
>
> I talked with the network administrator and remove the proxy rules to a
> range of IP's, installed oVirt with hosted engine on CentOS 7.1 and
> everything run just fine. Previously I set the enviroment settings to
> include the include proxy and proxy exceptions for the all the users of the
> system with a file in /etc/profile.d/ directory. I used to do this and
> always works.
>
> It's a bug in oVirt ?
>
> My ovirt-image-repository it's working now and with IP's behind the proxy
> doesn't.
>
> oVirt doesn't play nice behind a web proxy ?

Not sure what's the exact issue, but engine-setup and hosted-engine --deploy
do not directly download packages - they use yum for that. So if yum works
for you, they should, too. Generally speaking, you can configure yum to use
a proxy by setting 'proxy=$URL' in /etc/yum.conf.

Best,

> ovirt-image-repository
> ------------------------------
>
> This article originally appeared on community.redhat.com. Follow the
> community on Twitter at @redhatopen <https://twitter.com/redhatopen>, and
> find us on Facebook <https://www.facebook.com/redhatopen> and Goo
> <https://plus.google.com/u/0/b/113258037797946990391/113258037797946990391/posts>
>
>
> 2015-04-29 2:58 GMT-05:00 Yedidyah Bar David <didi@redhat.com>:
>
> > ----- Original Message -----
> > > From: "Yedidyah Bar David" <didi@redhat.com>
> > > To: "Julián Tete" <danteconrad14@gmail.com>
> > > Cc: users@ovirt.org
> > > Sent: Wednesday, April 29, 2015 10:51:48 AM
> > > Subject: Re: [ovirt-users] Problem with a second host: Exit message:
> > internal error: Cannot find suitable CPU model
> > > for given data.
> > >
> > > ----- Original Message -----
> > > > From: "Julián Tete" <danteconrad14@gmail.com>
> > > > To: "Yedidyah Bar David" <didi@redhat.com>
> > > > Cc: users@ovirt.org
> > > > Sent: Wednesday, April 29, 2015 7:20:34 AM
> > > > Subject: Re: [ovirt-users] Problem with a second host: Exit message:
> > > > internal error: Cannot find suitable CPU model
> > > > for given data.
> > > >
> > > > Hi
> > > >
> > > > Thanks for advices. :)
> > > >
> > > > I reinstalled the Second Host, Installed QEMU/KVM with virt-manager,
> > > > created virtual machines, no hassle.
> > > >
> > > > I don't think in BIOS problem, beacuse are new machines and I didn't
> > touch
> > > > anything.
> > >
> > > Please double check that, also compare with the working host.
> >
> > See also:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1103672
> >
> > Best,
> >
> > >
> > > >
> > > > Yesterday I did format the Second Host and try the Server-World
> > aproach on
> > > > CentOS 7:
> > > >
> > > > http://www.server-world.info/en/note?os=CentOS_6&p=ovirt&f=2
> > > >
> > > > Didn't work
> > > >
> > > > Today i'm going to format the machine and try to install a hosted
> > engine on
> > > > the Second Host.
> > > >
> > > > I'm listening suggestions.
> > >
> > > I don't have many more, sorry.
> > >
> > > If BIOS Setup is exactly the same, I suggest to ask this in a libvirt
> > mailing
> > > list.
> > >
> > > Best,
> > >
> > > >
> > > >
> > > >
> > > > 2015-04-28 1:03 GMT-05:00 Yedidyah Bar David <didi@redhat.com>:
> > > >
> > > > > ----- Original Message -----
> > > > > > From: "Julián Tete" <danteconrad14@gmail.com>
> > > > > > To: "Yedidyah Bar David" <didi@redhat.com>
> > > > > > Cc: users@ovirt.org
> > > > > > Sent: Tuesday, April 28, 2015 12:32:37 AM
> > > > > > Subject: Re: [ovirt-users] Problem with a second host: Exit
> > message:
> > > > > internal error: Cannot find suitable CPU model
> > > > > > for given data.
> > > > > >
> > > > > > Check this out:
> > > > > >
> > > > > > First Host;
> > > > > >
> > > > > > Input:
> > > > > >
> > > > > > systemctl status libvirtd.service -l
> > > > > >
> > > > > > Output:
> > > > > >
> > > > > > libvirtd.service - Virtualization daemon
> > > > > >    Loaded: loaded (/usr/lib/systemd/system/libvirtd.service;
> > enabled)
> > > > > >    Active: active (running) since vie 2015-04-24 20:28:11 COT; 2
> > days
> > > > > >    ago
> > > > > >      Docs: man:libvirtd(8)
> > > > > >            http://libvirt.org
> > > > > >  Main PID: 26351 (libvirtd)
> > > > > >    CGroup: /system.slice/libvirtd.service
> > > > > >            └─26351 /usr/sbin/libvirtd --listen
> > > > > >
> > > > > > abr 27 16:29:08 patascoy.udistritaloas.edu.co libvirtd[26351]:
> > metadata
> > > > > not
> > > > > > found: Requested metadata element is not present
> > > > > > abr 27 16:29:23 patascoy.udistritaloas.edu.co libvirtd[26351]:
> > metadata
> > > > > not
> > > > > > found: Requested metadata element is not present
> > > > > > abr 27 16:29:38 patascoy.udistritaloas.edu.co libvirtd[26351]:
> > metadata
> > > > > not
> > > > > > found: Requested metadata element is not present
> > > > > > abr 27 16:29:53 patascoy.udistritaloas.edu.co libvirtd[26351]:
> > metadata
> > > > > not
> > > > > > found: Requested metadata element is not present
> > > > > > abr 27 16:30:08 patascoy.udistritaloas.edu.co libvirtd[26351]:
> > metadata
> > > > > not
> > > > > > found: Requested metadata element is not present
> > > > > > abr 27 16:30:23 patascoy.udistritaloas.edu.co libvirtd[26351]:
> > metadata
> > > > > not
> > > > > > found: Requested metadata element is not present
> > > > > > abr 27 16:30:38 patascoy.udistritaloas.edu.co libvirtd[26351]:
> > metadata
> > > > > not
> > > > > > found: Requested metadata element is not present
> > > > > > abr 27 16:30:53 patascoy.udistritaloas.edu.co libvirtd[26351]:
> > metadata
> > > > > not
> > > > > > found: Requested metadata element is not present
> > > > > > abr 27 16:31:08 patascoy.udistritaloas.edu.co libvirtd[26351]:
> > metadata
> > > > > not
> > > > > > found: Requested metadata element is not present
> > > > > > abr 27 16:31:23 patascoy.udistritaloas.edu.co libvirtd[26351]:
> > metadata
> > > > > not
> > > > > > found: Requested metadata element is not present
> > > > > >
> > > > > > Second Host:
> > > > > >
> > > > > > Input:
> > > > > >
> > > > > > systemctl status libvirtd.service -l
> > > > > >
> > > > > > Output:
> > > > > >
> > > > > > libvirtd.service - Virtualization daemon
> > > > > >    Loaded: loaded (/usr/lib/systemd/system/libvirtd.service;
> > enabled)
> > > > > >    Active: active (running) since lun 2015-04-27 12:37:37 COT; 3h
> > 54min
> > > > > ago
> > > > > >      Docs: man:libvirtd(8)
> > > > > >            http://libvirt.org
> > > > > >  Main PID: 1875 (libvirtd)
> > > > > >    CGroup: /system.slice/libvirtd.service
> > > > > >            └─1875 /usr/sbin/libvirtd --listen
> > > > > >
> > > > > > abr 27 15:28:12 sotara.udistritaloas.edu.co libvirtd[1875]:
> > Preferred
> > > > > CPU
> > > > > > model SandyBridge not allowed by hypervisor; closest supported
> > model
> > > > > > will
> > > > > > be used
> > > > > > abr 27 15:28:12 sotara.udistritaloas.edu.co libvirtd[1875]:
> > internal
> > > > > error:
> > > > > > Cannot find suitable CPU model for given data
> > > > >
> > > > > Well, you can search for these messages on the net...
> > > > >
> > > > > Are BIOS Setup settings identical between them?
> > > > >
> > > > > > abr 27 15:46:57 sotara.udistritaloas.edu.co libvirtd[1875]:
> > Preferred
> > > > > CPU
> > > > > > model Westmere not allowed by hypervisor; closest supported model
> > will
> > > > > > be
> > > > > > used
> > > > > > abr 27 15:46:57 sotara.udistritaloas.edu.co libvirtd[1875]:
> > internal
> > > > > error:
> > > > > > Cannot find suitable CPU model for given data
> > > > > > abr 27 15:48:17 sotara.udistritaloas.edu.co libvirtd[1875]:
> > Preferred
> > > > > CPU
> > > > > > model Westmere not allowed by hypervisor; closest supported model
> > will
> > > > > > be
> > > > > > used
> > > > > > abr 27 15:48:17 sotara.udistritaloas.edu.co libvirtd[1875]:
> > internal
> > > > > error:
> > > > > > Cannot find suitable CPU model for given data
> > > > > > abr 27 16:00:12 sotara.udistritaloas.edu.co libvirtd[1875]:
> > Preferred
> > > > > CPU
> > > > > > model Westmere not allowed by hypervisor; closest supported model
> > will
> > > > > > be
> > > > > > used
> > > > > > abr 27 16:00:12 sotara.udistritaloas.edu.co libvirtd[1875]:
> > internal
> > > > > error:
> > > > > > Cannot find suitable CPU model for given data
> > > > > > abr 27 16:07:52 sotara.udistritaloas.edu.co libvirtd[1875]:
> > Preferred
> > > > > CPU
> > > > > > model Westmere not allowed by hypervisor; closest supported model
> > will
> > > > > > be
> > > > > > used
> > > > > > abr 27 16:07:52 sotara.udistritaloas.edu.co libvirtd[1875]:
> > internal
> > > > > error:
> > > > > > Cannot find suitable CPU model for given data
> > > > > >
> > > > > >
> > > > > >
> > > > > > El lun., 27 abr. 2015 a las 16:19, Julián Tete
> > > > > > (<danteconrad14@gmail.com
> > > > > >)
> > > > > > escribió:
> > > > > >
> > > > > > > Hi Didi
> > > > > > >
> > > > > > > Thanks for your help
> > > > > > >
> > > > > > > It's the same hardware (IBM HS23) on all the machines
> > (SandyBridge
> > > > > CPU's)
> > > > > > >
> > > > > > > The first Host contains the Engine (It's Hosted-Engine)
> > > > > > >
> > > > > > > The Virtual machine works on the first host but doesn't on the
> > > > > > > second.
> > > > > > > (The State are Up in Both Hosts)
> > > > > > >
> > > > > > > I changed the number of CPUs on the virtual machine and nothing
> > > > > happens.
> > > > > > >
> > > > > > > Basic First Host Information:
> > > > > > >
> > > > > > > http://pastebin.com/TG7LVLVs
> > > > > > >
> > > > > > > First Host Relevant oVirt Information:
> > > > > > >
> > > > > > > http://pastebin.com/XAdf7Mt5
> > > > > > >
> > > > > > > I don't undestand: "try to copy/paste the generated domain xml
> > from
> > > > > > > vdsm.log and use that with virsh cpu-compare?"
> > > > > > >
> > > > > > > Thanks in Advance
> > > > > > >
> > > > > > > El lun., 27 abr. 2015 a las 1:47, Yedidyah Bar David
> > > > > > > (<didi@redhat.com
> > > > > >)
> > > > > > > escribió:
> > > > > > >
> > > > > > >> ----- Original Message -----
> > > > > > >> > From: "Julián Tete" <danteconrad14@gmail.com>
> > > > > > >> > To: users@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@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
> > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Didi
> > > > >
> > > > >
> > > >
> > >
> > > --
> > > Didi
> > >
> > >
> >
> > --
> > Didi
> >
> >
>

--
Didi