RE: Hyper-V networking: problem after upgrade to 10.2
Hi Jac, BTW, what do you mean by saying "networking does not work anymore" -- can you please check if your issue is the same as Bug 187006 - [hyper-v] dynamic address (dhcp) obtaining doesn't work on HYPER-V OS 2012 R2 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187006 ? Thanks, -- Dexuan > -Original Message- > From: Dexuan Cui > Sent: Tuesday, January 26, 2016 14:49 > To: Kylie Liang ; Jac Backus ; > 'freebsd-virtualization@freebsd.org' ; BSD > Integration Components for Hyper-V > Subject: 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 > unnecessary 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 ; 'freebsd- > virtualizat...@freebsd.org' > > ; BSD Integration Components for Hyper- > V > > > > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 > > > > Hi Jac, > > > > Thank you for asking. To isolate your issue, could you please try disabling > > SO > on > > your 10.2 system first? Thank you. > > > > 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. > > > > Thanks, > > Kylie Liang > > > > -Original Message- > > From: owner-freebsd-virtualizat...@freebsd.org [mailto:owner-freebsd- > > virtualizat...@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 > patched > > 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 > > vmbus0 Jan 25 21:02:01 mercurius kernel: hn0: unknown status 1073872902 > > received Jan 25 21:02:01 mercurius kernel: hn0: unknown status 1073872902 > > received 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/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: > Interface> on vmbus0 Jan 25 21:02:01 mercurius kernel: hn1: unknown status > > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: unknown status > > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: hv send offload > > request succeeded Jan 25 21:02:01 mercurius kernel: hn1: Using defaults 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: > Interface> on vmbus0 Jan 25 21:02:01 mercurius kernel: hn2: unknown status > > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: unknown status > > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: hv send offload > > request succeeded 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 > > 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: > Interface> on vmbus0 Jan 25 22:20:02 mercurius kernel: hn1: Ethernet > > address: > > 00:15:5d:ac:11:08 Jan 25 22:20:02 mercurius kernel: hn2: > Interface> 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.protection.outlook.com/?url=https%3a%2f%2flists.freebs > > d.org%2fmailman%2flistinfo%2ffreebsd- > > > virtualization&data=01%7c01%7ckyliel%40064d.mgd.microsoft.com%7cc9ca2e > > > 0d0fef482b553f08d325d3aefb%7c72f988bf86f141af91ab2d7cd011db47%7c1&s > > data=o%2bMZGuBW0frrQhjAPkhrWlLgNEH8
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 unnecessary 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 ; 'freebsd-virtualization@freebsd.org' > ; BSD Integration Components for Hyper-V > > Subject: RE: Hyper-V networking: problem after upgrade to 10.2 > > Hi Jac, > > Thank you for asking. To isolate your issue, could you please try disabling > SO on > your 10.2 system first? Thank you. > > 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. > > Thanks, > Kylie Liang > > -Original Message- > From: owner-freebsd-virtualizat...@freebsd.org [mailto:owner-freebsd- > virtualizat...@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 > patched > 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 > vmbus0 Jan 25 21:02:01 mercurius kernel: hn0: unknown status 1073872902 > received Jan 25 21:02:01 mercurius kernel: hn0: unknown status 1073872902 > received 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/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: Interface> on vmbus0 Jan 25 21:02:01 mercurius kernel: hn1: unknown status > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: unknown status > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: hv send offload > request succeeded Jan 25 21:02:01 mercurius kernel: hn1: Using defaults 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: Interface> on vmbus0 Jan 25 21:02:01 mercurius kernel: hn2: unknown status > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: unknown status > 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: hv send offload > request succeeded 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 > 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: Interface> on vmbus0 Jan 25 22:20:02 mercurius kernel: hn1: Ethernet address: > 00:15:5d:ac:11:08 Jan 25 22:20:02 mercurius kernel: hn2: Interface> 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.protection.outlook.com/?url=https%3a%2f%2flists.freebs > d.org%2fmailman%2flistinfo%2ffreebsd- > virtualization&data=01%7c01%7ckyliel%40064d.mgd.microsoft.com%7cc9ca2e > 0d0fef482b553f08d325d3aefb%7c72f988bf86f141af91ab2d7cd011db47%7c1&s > data=o%2bMZGuBW0frrQhjAPkhrWlLgNEH8LJ7BiLUyiO4tvR0%3d > To unsubscribe, send any mail to "freebsd-virtualization- > unsubscr...@freebsd.org" ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 206630] [Hyper-V]FreeBSD 10.2 on Windows 10 & 2016 server may not boot due to multiple invalid disks issue
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206630 Mark Linimon changed: What|Removed |Added Keywords||patch Assignee|freebsd-b...@freebsd.org|emulat...@freebsd.org -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 206630] [Hyper-V]FreeBSD 10.2 on Windows 10 & 2016 server may not boot due to multiple invalid disks issue
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206630 Kylie changed: What|Removed |Added CC||delp...@freebsd.org, ||freebsd-virtualization@Free ||BSD.org, ||kyl...@microsoft.com, ||roy...@freebsd.org -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
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 patched 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 vmbus0 Jan 25 21:02:01 mercurius kernel: hn0: unknown status 1073872902 received Jan 25 21:02:01 mercurius kernel: hn0: unknown status 1073872902 received 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/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: on vmbus0 Jan 25 21:02:01 mercurius kernel: hn1: unknown status 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: unknown status 1073872902 received Jan 25 21:02:01 mercurius kernel: hn1: hv send offload request succeeded Jan 25 21:02:01 mercurius kernel: hn1: Using defaults 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: on vmbus0 Jan 25 21:02:01 mercurius kernel: hn2: unknown status 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: unknown status 1073872902 received Jan 25 21:02:01 mercurius kernel: hn2: hv send offload request succeeded 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 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: on vmbus0 Jan 25 22:20:02 mercurius kernel: hn1: Ethernet address: 00:15:5d:ac: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://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"