[Bug 213618] When running as a Hyper-V Guest, FreeBSD 11 networking does not work
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Oct 19 16:50:24 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213618
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 at FreeBSD.org
Reporter: caesar at starkreality.com
CC: freebsd-amd64 at FreeBSD.org
CC: freebsd-amd64 at 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 able
to transmit. The NICs are detected, and appear to be able to receive traffic
(IPv6 SLAAC works, tcpdump shows broadcast/multicast traffic), but the NICs are
unable to transmit. dhclient complains send_packet: No buffer space available.
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 following
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=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=71b<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=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
media: Ethernet autoselect (10Gbase-T <full-duplex>)
status: active
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-amd64
mailing list