From owner-freebsd-amd64@freebsd.org  Wed Oct 19 16:50:24 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@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 C726AC19286
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Wed, 19 Oct 2016 16:50:24 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 9DD29C15
 for <freebsd-amd64@FreeBSD.org>; Wed, 19 Oct 2016 16:50:24 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9JGoOeH084464
 for <freebsd-amd64@FreeBSD.org>; Wed, 19 Oct 2016 16:50:24 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 213618] When running as a Hyper-V Guest, FreeBSD 11 networking
 does not work
Date: Wed, 19 Oct 2016 16:50:24 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-RC1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: caesar@starkreality.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter cc
Message-ID: <bug-213618-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 16:50:24 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213618

            Bug ID: 213618
           Summary: When running as a Hyper-V Guest, FreeBSD 11 networking
                    does not work
           Product: Base System
           Version: 11.0-RC1
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: caesar@starkreality.com
                CC: freebsd-amd64@FreeBSD.org
                CC: freebsd-amd64@FreeBSD.org

Host OS: Windows Server 2012
Guest OS: FreeBSD 11.0-RELEASE-p1

Neither the syntetic hnX NIC or the emulated Tulip deX NICs appear to be ab=
le
to transmit.  The NICs are detected, and appear to be able to receive traff=
ic
(IPv6 SLAAC works, tcpdump shows broadcast/multicast traffic), but the NICs=
 are
unable to transmit.  dhclient complains send_packet: No buffer space availa=
ble.
 After configuring a static address with ifconfig, attempts to send packets=
 via
ping do not show up in a tcpdump.  This has been verified under the followi=
ng
conditions:

10.3-RELEASE upgrade to 11.0-RELEASE
11.0-RELEASE fresh installation from .iso
11.0-RELEASE .vhd image from ftp.freebsd.org

dmesg related to hn:
hn0: <Hyper-V Network Interface> on vmbus0
hn0: LRO: entry count 128
hn0: unknown status 1073872902 received
hn0: unknown status 1073872902 received
hn0: hv send offload request succeeded
hn0: 1 TX ring, 1 RX ring
hn0: Ethernet address: 00:15:5d:xx:xx:xx
hn0: TSO: 65517/31/4096
hn0: link state changed to UP

ifconfig hn0 shows:
hn0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=3D71b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,TSO6,LRO>
ether 00:15:5d:xx:xx:xx
inet6 fe80::... prefixlen 64 scopeid 0x2
inet6 2601:... prefixlen 64 autoconf
inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
nd6 options=3D23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
media: Ethernet autoselect (10Gbase-T <full-duplex>)
status: active

--=20
You are receiving this mail because:
You are on the CC list for the bug.=