<div dir="ltr">If that is the case, and the required need can be set in the automation dir the I agree.<div>Is that possible to set via scripts in the automation dir?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 25, 2016 at 10:59 AM, Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 25 May 2016 at 10:33, Eyal Edri <<a href="mailto:eedri@redhat.com">eedri@redhat.com</a>> wrote:<br>
> Fabian,<br>
> Please open a ticket to enable all VMs to support nested, I don't see a<br>
> reason why not to.<br>
> Evgheni - we'll need to make sure all hosts supports nested, it will require<br>
> reboot of a server if its not enabled now.<br>
><br>
<br>
</span>The point is not to make VMs support nesting (they all already do probably)<br>
Its to configure std-ci to pre-configure KVM access for mock (without<br>
having the devs specify that in the automation dir) I'm not sure I'm<br>
in favour of that.<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHEV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div>
</div>