Re: [ovirt-devel] OST Regression in add cluster (IBRS related)

2018-01-15 Thread Gal Ben Haim
As a workaround, we can map *-IBRS: Intel * Family On Mon, Jan 15, 2018 at 5:52 PM, Eyal Edri wrote: > > > On Mon, Jan 15, 2018 at 5:46 PM, Nadav Goldin > wrote: > >> Maybe related to [1]? >> >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1533125

Re: [ovirt-devel] OST Regression in add cluster (IBRS related)

2018-01-15 Thread Eyal Edri
On Mon, Jan 15, 2018 at 5:46 PM, Nadav Goldin wrote: > Maybe related to [1]? > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1533125 This is for RHEL 7.5, if its related then we should look at the 7.4.z clone: *Bug 1533418*

Re: [ovirt-devel] OST Regression in add cluster (IBRS related)

2018-01-15 Thread Nadav Goldin
Maybe related to [1]? [1] https://bugzilla.redhat.com/show_bug.cgi?id=1533125 On Mon, Jan 15, 2018 at 5:40 PM, Gal Ben Haim wrote: > I've tried to run 'basic-suite-master' with [1], but I'm getting the > following error: > > _ID: VDS_CPU_LOWER_THAN_CLUSTER(515), Host

Re: [ovirt-devel] OST Regression in add cluster (IBRS related)

2018-01-15 Thread Gal Ben Haim
I've tried to run 'basic-suite-master' with [1], but I'm getting the following error: _ID: VDS_CPU_LOWER_THAN_CLUSTER(515), Host lago-basic-suite-master-host-1 moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : model_Haswell-noTSX-IBRS

Re: [ovirt-devel] OST Regression in add cluster (IBRS related)

2018-01-14 Thread Nadav Goldin
Trying to put together what I remember: 1. We had a QEMU bug where it was stated clearly that nested-virtualization is only supported when using 'host-passthrough' (don't know if that had changed since). 2. As consequence of (1) - Lago uses by default host-passthrough. 3. When running O-S-T, we

Re: [ovirt-devel] OST Regression in add cluster (IBRS related)

2018-01-14 Thread Gal Ben Haim
On Fri, Jan 12, 2018 at 7:07 PM, Yaniv Kaul wrote: > > > On Fri, Jan 12, 2018 at 6:49 PM, Michal Skrivanek < > michal.skriva...@redhat.com> wrote: > >> >> >> On 12 Jan 2018, at 17:32, Yaniv Kaul wrote: >> >> >> >> On Fri, Jan 12, 2018 at 1:05 PM, Michal

Re: [ovirt-devel] OST Regression in add cluster (IBRS related)

2018-01-12 Thread Yaniv Kaul
On Fri, Jan 12, 2018 at 6:49 PM, Michal Skrivanek < michal.skriva...@redhat.com> wrote: > > > On 12 Jan 2018, at 17:32, Yaniv Kaul wrote: > > > > On Fri, Jan 12, 2018 at 1:05 PM, Michal Skrivanek redhat.com> wrote: > >> >> >> On 12 Jan 2018, at 08:32, Tomas

Re: [ovirt-devel] OST Regression in add cluster (IBRS related)

2018-01-12 Thread Michal Skrivanek
> On 12 Jan 2018, at 17:32, Yaniv Kaul wrote: > > > > On Fri, Jan 12, 2018 at 1:05 PM, Michal Skrivanek > > wrote: > > >> On 12 Jan 2018, at 08:32, Tomas Jelinek >

Re: [ovirt-devel] OST Regression in add cluster (IBRS related)

2018-01-12 Thread Yaniv Kaul
On Fri, Jan 12, 2018 at 1:05 PM, Michal Skrivanek < michal.skriva...@redhat.com> wrote: > > > On 12 Jan 2018, at 08:32, Tomas Jelinek wrote: > > > > On Fri, Jan 12, 2018 at 8:18 AM, Yaniv Kaul wrote: > >> >> >> On Fri, Jan 12, 2018 at 9:06 AM, Yaniv Kaul

Re: [ovirt-devel] OST Regression in add cluster (IBRS related)

2018-01-12 Thread Michal Skrivanek
> On 12 Jan 2018, at 08:32, Tomas Jelinek wrote: > > > > On Fri, Jan 12, 2018 at 8:18 AM, Yaniv Kaul > wrote: > > > On Fri, Jan 12, 2018 at 9:06 AM, Yaniv Kaul > wrote: > See[1]

Re: [ovirt-devel] OST Regression in add cluster (IBRS related)

2018-01-11 Thread Tomas Jelinek
On Fri, Jan 12, 2018 at 8:18 AM, Yaniv Kaul wrote: > > > On Fri, Jan 12, 2018 at 9:06 AM, Yaniv Kaul wrote: > >> See[1] - do we need to update Lago / Lago OST plugin? >> > > Something like https://github.com/lago-project/lago-ost-plugin/pull/31 > perhaps (not

Re: [ovirt-devel] OST Regression in add cluster (IBRS related)

2018-01-11 Thread Yaniv Kaul
On Fri, Jan 12, 2018 at 9:06 AM, Yaniv Kaul wrote: > See[1] - do we need to update Lago / Lago OST plugin? > Something like https://github.com/lago-project/lago-ost-plugin/pull/31 perhaps (not tested, don't have the HW). Y. > Error Message > > Unsupported CPU model: