<div dir="ltr">I had the same issue, and I also have a support case open. They referenced <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1288237">https://bugzilla.redhat.com/show_bug.cgi?id=1288237</a> which is private. I didn't have any success getting that bugzilla changed to public. We couldn't keep waiting for the issue to be fixed so we replaced the NICs with Broadcom/Qlogic that we knew had no issues in other hosts.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 17, 2016 at 11:27 AM, Sigbjorn Lie <span dir="ltr"><<a href="mailto:sigbjorn@nixtra.com" target="_blank">sigbjorn@nixtra.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Is this on CentOS/RHEL 7.2?<br>
<br>
Log in as root as see if you can see any messages from ixgbe about "tx queue hung" in dmesg. I<br>
currently have an open support case for RHEL7.2 and the ixgbe driver, where there is a driver<br>
issue causing the network adapter to reset continuously when there are network traffic.<br>
<br>
<br>
Regards,<br>
Siggi<br>
<br>
<br>
<br>
On Thu, March 17, 2016 12:52, Nir Soffer wrote:<br>
> On Thu, Mar 17, 2016 at 10:49 AM, Johan Kooijman <<a href="mailto:mail@johankooijman.com">mail@johankooijman.com</a>> wrote:<br>
><br>
>> Hi all,<br>
>><br>
>><br>
>> Since we upgraded to the latest ovirt node running 7.2, we're seeing that<br>
>> nodes become unavailable after a while. It's running fine, with a couple of VM's on it, untill it<br>
>> becomes non responsive. At that moment it doesn't even respond to ICMP. It'll come back by<br>
>> itself after a while, but oVirt fences the machine before that time and restarts VM's elsewhere.<br>
>><br>
>><br>
>> Engine tells me this message:<br>
>><br>
>><br>
>> VDSM host09 command failed: Message timeout which can be caused by<br>
>> communication issues<br>
>><br>
>> Is anyone else experiencing these issues with ixgbe drivers? I'm running on<br>
>> Intel X540-AT2 cards.<br>
>><br>
><br>
> We will need engine and vdsm logs to understand this issue.<br>
><br>
><br>
> Can you file a bug and attach ful logs?<br>
><br>
><br>
> Nir<br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
><br>
><br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</blockquote></div><br></div>