<div dir="ltr">I'll try and let you know, but is a little bit difficult due to the fact that my setup is a production one!<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 2, 2014 at 12:59 AM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Mon, Mar 31, 2014 at 04:57:44PM +0300, Gabi C wrote:<br>
> Hello!<br>
><br>
> Has that fix pushed into the repository yet?<br>
><br>
><br>
> Seems that removing Qos profiles from the NIC profiles did the trick..VM is<br>
> up!<br>
><br>
> Thanks guys!<br>
<br>
</div>No, thank you for reporting this.<br>
<br>
The patch still awaits verification <a href="http://gerrit.ovirt.org/#/c/26254/" target="_blank">http://gerrit.ovirt.org/#/c/26254/</a><br>
<br>
I would very much appreciate if you can apply it on your host's vdsm,<br>
re-add the QoS profiles, and report if life is good again.<br>
<span class="HOEnZb"><font color="#888888"><br>
Dan.<br>
</font></span></blockquote></div><br></div>