On Jan 19, 2018 12:31 PM, "Gianluca Cecchi" <gianluca.cecchi@gmail.com> wrote:
On Fri, Jan 19, 2018 at 11:15 AM, Yaniv Kaul <ykaul@redhat.com> wrote:


On Jan 19, 2018 10:52 AM, "andreil1" <andreil1@starlett.lv> wrote:


Migration disabled.

Why this enforcing? If the VM is so important I see it as a limitation not to be able to move it in case of need

It's related to CPU pinning and NUMA. 



Pass-through host CPU enabled

I don't know if this is so important.
Tested with Oracle RDBMS and not used in my case.

In the specific case of Oracle, I actually suspect you must use CPU pinning for licensing reasons. I suggest you check. 

As for CPU passthrough, might depend on which features you use. 

 

Any idea of NUMA settings ?

Indeed. + Huge pages, in both host and guest. 

Do you think NUMA so essential? It implies non-migratable VM...
In my tests I didn't set NUMA

Depends on the workload really. It and CPU pinning are many times critical for IO bound workloads. Also depends on how much optimization you are after. 
Y. 




In short, use high performance VM. See ovirt.org feature page. 
Y. 


In my opinion the  main limitation of "High performance VM" is to be not-migratable (probably implied because you set NUMA?)
In that case could it be possible to have NUMA as choice, so that at the same time you can choose if you want a migratable or not-migratable high performance VM?
Also CPU passthrough, I don't remember if it is included/fixed option in high perf VM...

Gianluca