Date: Tue, 26 Jan 2016 15:31:30 +0000 From: Jac Backus <j.backus@bugworks.com> To: Dexuan Cui <decui@microsoft.com>, Kylie Liang <kyliel@microsoft.com>, "'freebsd-virtualization@freebsd.org'" <freebsd-virtualization@freebsd.org>, BSD Integration Components for Hyper-V <bsdic@microsoft.com> Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Message-ID: <e160d0687e7749f49269b0edc57c1c92@ORTELIUS.internal.bugworks.com> In-Reply-To: <bcca15b9c5cd4e0db3d80b40bde7405a@HKXPR3004MB0088.064d.mgd.msft.net> References: <cdb46889a0164856987da43537a104de@ORTELIUS.internal.bugworks.com> <8572369fcc3b408891fc1a5a7d11e892@SG2PR3002MB0107.064d.mgd.msft.net> <bcca15b9c5cd4e0db3d80b40bde7405a@HKXPR3004MB0088.064d.mgd.msft.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Dexuan,
I did fresh installation with the current FreeBSD-10.2-RELEASE-amd64-dvd1.i=
so and this works.
Even with the message, as you already mentioned.
With kind regards,
Jac
-----Oorspronkelijk bericht-----
Van: Dexuan Cui [mailto:decui@microsoft.com]=20
Verzonden: dinsdag 26 januari 2016 7:49
Aan: Kylie Liang; Jac Backus; 'freebsd-virtualization@freebsd.org'; BSD Int=
egration Components for Hyper-V
Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2
Hi Jac,
Kylie meant disabling TSO. Please try this ("ifconfig hn0 -tso").
The message " hn0: unknown status 1073872902 received" should be an unneces=
sary warning only.
My 10.2 VM can work fine even if I see the message too.
Can you please install a 10.2 VM from the 10.2 .ISO file directly as I did =
and see if it works for you?
I guess we never tried upgrading 10.1 from 10.2.
Can you please list the steps how you did the upgrading? We'll try the same=
steps.
Thanks,
-- Dexuan
> -----Original Message-----
> From: Kylie Liang
> Sent: Tuesday, January 26, 2016 8:01
> To: Jac Backus <j.backus@bugworks.com>; 'freebsd-virtualization@freebsd.o=
rg'
> <freebsd-virtualization@freebsd.org>; BSD Integration Components for=20
> Hyper-V <bsdic@microsoft.com>
> Subject: RE: Hyper-V networking: problem after upgrade to 10.2
>=20
> Hi Jac,
>=20
> Thank you for asking. To isolate your issue, could you please try=20
> 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
>=20
> Right? And add our engineers in the list.
>=20
> Thanks,
> Kylie Liang
>=20
> -----Original Message-----
> From: owner-freebsd-virtualization@freebsd.org [mailto:owner-freebsd-=20
> virtualization@freebsd.org] On Behalf Of Jac Backus
> Sent: Tuesday, January 26, 2016 5:56 AM
> To: 'freebsd-virtualization@freebsd.org'=20
> <freebsd-virtualization@freebsd.org>
> Subject: Hyper-V networking: problem after upgrade to 10.2
>=20
> Dear reader,
>=20
> Today, I did upgrade FreeBSD 10.1 to 10.2 running on Hyper-V on a=20
> full patched Windows Server 2012 R2 x64 version.
>=20
> After the update, networking does not work anymore.
>=20
> In /var/log/messages is this:
>=20
> Jan 25 21:02:01 mercurius kernel: hn0: <Synthetic Network Interface>=20
> on
> vmbus0 Jan 25 21:02:01 mercurius kernel: hn0: unknown status=20
> 1073872902 received Jan 25 21:02:01 mercurius kernel: hn0: unknown=20
> status 1073872902 received Jan 25 21:02:01 mercurius kernel: hn0: hv=20
> send offload request succeeded Jan 25 21:02:01 mercurius kernel: hn0: Usi=
ng defaults for TSO:
> 65518/35/2048 Jan 25 21:02:01 mercurius kernel: hn0: Ethernet address:
> 00:15:5d:ac:11:08 Jan 25 21:02:01 mercurius kernel: hn1: <Synthetic=20
> Network
> Interface> on vmbus0 Jan 25 21:02:01 mercurius kernel: hn1: unknown=20
> Interface> status
> 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: unknown=20
> status
> 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: hv send=20
> offload request succeeded Jan 25 21:02:01 mercurius kernel: hn1: Using de=
faults for TSO:
> 65518/35/2048 Jan 25 21:02:01 mercurius kernel: hn1: Ethernet address:
> 00:15:5d:ac:11:09 Jan 25 21:02:01 mercurius kernel: hn2: <Synthetic=20
> Network
> Interface> on vmbus0 Jan 25 21:02:01 mercurius kernel: hn2: unknown=20
> Interface> status
> 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: unknown=20
> status
> 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: hv send=20
> offload request succeeded Jan 25 21:02:01 mercurius kernel: hn2: Using de=
faults for TSO:
> 65518/35/2048 Jan 25 21:02:01 mercurius kernel: hn2: Ethernet address:
> 00:15:5d:ac:11:07
>=20
> It worked fine with the 10.1 kernel, and when I boot this kernel, it work=
s again:
>=20
> Jan 25 22:20:02 mercurius kernel: hn0: <Synthetic Network Interface>=20
> on
> vmbus0 Jan 25 22:20:02 mercurius kernel: hn0: Ethernet address:
> 00:15:5d:ac:11:07 Jan 25 22:20:02 mercurius kernel: hn1: <Synthetic=20
> Network
> Interface> on vmbus0 Jan 25 22:20:02 mercurius kernel: hn1: Ethernet addr=
ess:
> 00:15:5d:ac:11:08 Jan 25 22:20:02 mercurius kernel: hn2: <Synthetic=20
> Network
> Interface> on vmbus0 Jan 25 22:20:02 mercurius kernel: hn2: Ethernet addr=
ess:
> 00:15:5d:ac:11:09
>=20
> So I am running a 10.2 system on a 10.1 kernel at the moment.
>=20
> I found nothing in /usr/src/UPDATING and not really anything on the net.
>=20
> So, could you tell why does this happen, and how can I solve this?
>=20
> Thanks for the help!
>=20
> With kind regards,
>=20
> Jac Backus
>=20
>=20
>=20
> _______________________________________________
> freebsd-virtualization@freebsd.org mailing list=20
> https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3a%2f%2flists
> .freebs
> d.org%2fmailman%2flistinfo%2ffreebsd-
> virtualization&data=3D01%7c01%7ckyliel%40064d.mgd.microsoft.com%7cc9ca2e
> 0d0fef482b553f08d325d3aefb%7c72f988bf86f141af91ab2d7cd011db47%7c1&s
> data=3Do%2bMZGuBW0frrQhjAPkhrWlLgNEH8LJ7BiLUyiO4tvR0%3d
> To unsubscribe, send any mail to "freebsd-virtualization-=20
> unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e160d0687e7749f49269b0edc57c1c92>