From owner-freebsd-stable@freebsd.org  Wed Sep  6 09:33:25 2017
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id D87D1E1D2B1
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed,  6 Sep 2017 09:33:25 +0000 (UTC)
 (envelope-from paul.koch@akips.com)
Received: from mail.akips.com (mail.akips.com [45.32.79.107])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id A583C688AA
 for <freebsd-stable@freebsd.org>; Wed,  6 Sep 2017 09:33:25 +0000 (UTC)
 (envelope-from paul.koch@akips.com)
Date: Wed, 6 Sep 2017 19:33:09 +1000
From: Paul Koch <paul.koch@akips.com>
To: freebsd-stable@freebsd.org
Subject: 11.1 running on HyperV hn interface hangs
Message-ID: <20170906193309.796c79ed@akips.com>
Organization: AKIPS
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 09:33:26 -0000


No sure if -stable is the right mailing list for this one.

We recently moved our software from 11.0-p9 to 11.1-p1, but looks like there
is a regression in 11.1-p1 running on HyperV (Windows/HyperV 2012 R2) where
the virtual hn0 interface hangs with the following kernel messages:

 hn0: <Hyper-V Network Interface> on vmbus0
 hn0: Ethernet address: 00:15:5d:31:21:0f
 hn0: link state changed to UP
 ...
 hn0: RXBUF ack retry
 hn0: RXBUF ack failed
 last message repeated 571 times

It requires a restart of the HyperV VM.

This is a customer production server (remote customer ~4000km away) running
fairly critical monitoring software, so we needed to roll it back to 11.0-p9.
We only have two customers running our software in HyperV, vs lots in VMware
and a handful on physical hardware.

11.0-p9 has been very stable.  Has anyone seen this problem before with 11.1 ?

11.1 is listed here
 https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-freebsd-virtual-machines-on-hyper-v

	Paul.
-- 
Paul Koch | Founder | CEO
AKIPS Network Monitor | akips.com
Brisbane, Australia