Hi Gianluca,

You are right, in oVirt 4.2 we removed the 'Num Of IO Threads' text field
from the UI because it was decided that one IO thread is the best
configuration from performance aspects for most cases (according to
performance testings). We wanted to keep the UI simpler to use.

So in case IO threads is enabled via Webadmin UI, only one IO thread is
always created.

For REST API the configuration remains unchanged in 4.2, so you can still
set the number of IO threads to be >= 1 if you want for some reason.

Regards,
Sharon


On Mon, Jun 18, 2018 at 6:21 PM, Gianluca Cecchi <gianluca.cec...@gmail.com>
wrote:

> Hello,
> in oVirt 4.1 I could enable I/O threads for a VM and then there was a
> field where I could define how many I/O threads (aka virtual scsi
> controllers from vm point of view).
> In 4.2 now I see only the option to enable them but not to specify the
> number.
> Next to the setting there is a symbol and a mouseover says "the field is
> not attached to any instance type"
>
> See this screenshot for the Edit VM -> Resource Allocation content:
>
> https://drive.google.com/file/d/1JzCiUBnWxS9fiY64_
> p5TJMY0uO5ZZUID/view?usp=sharing
>
> Any hints for setting the number?
>
> Thanks in advance,
> Gianluca
>
>
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-
> guidelines/
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/
> message/NJIRXBTKMBZO7HWQVUT33F6VFVKOLH5K/
>
>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WF7W3M4CDMZXCAI6VWHKFDUI7O74P4YI/

Reply via email to