From owner-freebsd-virtualization@freebsd.org Tue Jan 26 09:58:10 2016 Return-Path: Delivered-To: freebsd-virtualization@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 0A56FA46938 for ; Tue, 26 Jan 2016 09:58:10 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from mail.bugworks.com (mail.bugworks.com [213.129.194.75]) (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 2DE9A8EF for ; Tue, 26 Jan 2016 09:58:09 +0000 (UTC) (envelope-from j.backus@bugworks.com) Received: from localhost (localhost [127.0.0.1]) by mail.bugworks.com (Postfix) with ESMTP id A15262B9BDD; Tue, 26 Jan 2016 10:58:04 +0100 (CET) Received: from mail.bugworks.com ([127.0.0.1]) by localhost (mercurius.bugworks.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 01692-08; Tue, 26 Jan 2016 10:58:04 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (ortelius.internal.bugworks.com [172.27.172.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.bugworks.com (Postfix) with ESMTPS id 600562B9BA4; Tue, 26 Jan 2016 10:58:04 +0100 (CET) Received: from ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) by ORTELIUS.internal.bugworks.com (2001:470:1f15:de3:8cf6:ad3d:4fe2:615c) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Tue, 26 Jan 2016 10:58:03 +0100 Received: from ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c]) by ORTELIUS.internal.bugworks.com ([fe80::8cf6:ad3d:4fe2:615c%12]) with mapi id 15.00.1076.000; Tue, 26 Jan 2016 10:58:03 +0100 From: Jac Backus To: Kylie Liang , "'freebsd-virtualization@freebsd.org'" , BSD Integration Components for Hyper-V Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Thread-Topic: Hyper-V networking: problem after upgrade to 10.2 Thread-Index: AdFXuefm77fqXshWSUq/xyLaKrOi2AAEaGnQABSV3xA= Date: Tue, 26 Jan 2016 09:58:02 +0000 Message-ID: References: <8572369fcc3b408891fc1a5a7d11e892@SG2PR3002MB0107.064d.mgd.msft.net> In-Reply-To: <8572369fcc3b408891fc1a5a7d11e892@SG2PR3002MB0107.064d.mgd.msft.net> Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.27.172.126] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jan 2016 09:58:10 -0000 Hello Kylie, Thanks for the quick response! I disabled tso, but it makes no difference. I can ping the interface address itself, but no host on the subnet with the= 10.2 kernel.=20 1, 2 and 3 are completely correct. With kind regards, Jac -----Oorspronkelijk bericht----- Van: Kylie Liang [mailto:kyliel@microsoft.com]=20 Verzonden: dinsdag 26 januari 2016 1:01 Aan: Jac Backus; 'freebsd-virtualization@freebsd.org'; BSD Integration Comp= onents for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hi Jac,=20 Thank you for asking. To isolate your issue, could you please try disabling= SO on your 10.2 system first? Thank you.=20 And I would like to confirm with you 1) You met issue for 10.2 kernel + 10.2 system 2) No issue for 10.1 kernel + 10.1 system 3) No issue for 10.1 kernel + 10.2 system Right? And add our engineers in the list.=20 Thanks, Kylie Liang=20 -----Original Message----- From: owner-freebsd-virtualization@freebsd.org [mailto:owner-freebsd-virtua= lization@freebsd.org] On Behalf Of Jac Backus Sent: Tuesday, January 26, 2016 5:56 AM To: 'freebsd-virtualization@freebsd.org' Subject: Hyper-V networking: problem after upgrade to 10.2 Dear reader, Today, I did upgrade FreeBSD 10.1 to 10.2 running on Hyper-V on a full pa= tched Windows Server 2012 R2 x64 version. After the update, networking does not work anymore. In /var/log/messages is this: Jan 25 21:02:01 mercurius kernel: hn0: on vmb= us0 Jan 25 21:02:01 mercurius kernel: hn0: unknown status 1073872902 receiv= ed Jan 25 21:02:01 mercurius kernel: hn0: unknown status 1073872902 receive= d Jan 25 21:02:01 mercurius kernel: hn0: hv send offload request succeeded = Jan 25 21:02:01 mercurius kernel: hn0: Using defaults for TSO: 65518/35/204= 8 Jan 25 21:02:01 mercurius kernel: hn0: Ethernet address: 00:15:5d:ac:11:0= 8 Jan 25 21:02:01 mercurius kernel: hn1: on v= mbus0 Jan 25 21:02:01 mercurius kernel: hn1: unknown status 1073872902 rece= ived Jan 25 21:02:01 mercurius kernel: hn1: unknown status 1073872902 recei= ved Jan 25 21:02:01 mercurius kernel: hn1: hv send offload request succeede= d Jan 25 21:02:01 mercurius kernel: hn1: Using defaults for TSO: 65518/35/2= 048 Jan 25 21:02:01 mercurius kernel: hn1: Ethernet address: 00:15:5d:ac:11= :09 Jan 25 21:02:01 mercurius kernel: hn2: on= vmbus0 Jan 25 21:02:01 mercurius kernel: hn2: unknown status 1073872902 re= ceived Jan 25 21:02:01 mercurius kernel: hn2: unknown status 1073872902 rec= eived Jan 25 21:02:01 mercurius kernel: hn2: hv send offload request succee= ded Jan 25 21:02:01 mercurius kernel: hn2: Using defaults for TSO: 65518/35= /2048 Jan 25 21:02:01 mercurius kernel: hn2: Ethernet address: 00:15:5d:ac:= 11:07 It worked fine with the 10.1 kernel, and when I boot this kernel, it works = again: Jan 25 22:20:02 mercurius kernel: hn0: on vmb= us0 Jan 25 22:20:02 mercurius kernel: hn0: Ethernet address: 00:15:5d:ac:11= :07 Jan 25 22:20:02 mercurius kernel: hn1: on= vmbus0 Jan 25 22:20:02 mercurius kernel: hn1: Ethernet address: 00:15:5d:a= c:11:08 Jan 25 22:20:02 mercurius kernel: hn2: on vmbus0 Jan 25 22:20:02 mercurius kernel: hn2: Ethernet address: 00:15:= 5d:ac:11:09 So I am running a 10.2 system on a 10.1 kernel at the moment. I found nothing in /usr/src/UPDATING and not really anything on the net. So, could you tell why does this happen, and how can I solve this? Thanks for the help! With kind regards, Jac Backus _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://na01.safelinks.prot= ection.outlook.com/?url=3Dhttps%3a%2f%2flists.freebsd.org%2fmailman%2flisti= nfo%2ffreebsd-virtualization&data=3D01%7c01%7ckyliel%40064d.mgd.microsoft.c= om%7cc9ca2e0d0fef482b553f08d325d3aefb%7c72f988bf86f141af91ab2d7cd011db47%7c= 1&sdata=3Do%2bMZGuBW0frrQhjAPkhrWlLgNEH8LJ7BiLUyiO4tvR0%3d To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebs= d.org"