Hello Dexuan, I build a new kernel and the problem is gone.
I tried to understand your description of the patch. What I find remarkable is, that there is apparently no fixed relation between the virtual nics defined in Hyper-V (with a fixed mac address) and the devices, hn0, hn1, etc in the guest, and is the order determined at boot time. Something completely different: maybe you can point me to an explanation of these messages when I boot: calcru: runtime went backwards from 1672 usec to 845 usec for pid 144 (adjkerntz) calcru: runtime went backwards from 5 usec to 2 usec for pid 7 (pagezero) calcru: runtime went backwards from 126 usec to 63 usec for pid 4 (sctp_iterator) calcru: runtime went backwards from 6920 usec to 3743 usec for pid 3 (fdc0) calcru: runtime went backwards from 33080 usec to 16732 usec for pid 13 (geom) calcru: runtime went backwards from 12117 usec to 6318 usec for pid 1 (init) calcru: runtime went backwards from 155335 usec to 104098 usec for pid 0 (kernel) I happens since I virtualized the server. Again, I thank you very much for the help. And, of course, especially for the fix! With kind regards, Jac Van: Dexuan Cui [mailto:de...@microsoft.com] Verzonden: donderdag 4 februari 2016 7:01 Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualization@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hi Jac, The easiest way to get the fixes is just using the latest stable/10 branch as I mentioned in another mail. Alternatively, if you want to use your local 10.2 source code in /usr/src/ + the fixes only, please read the below: I put the 10.2-specific fixes onto my github branch "decui/10.2/fix_mac_order" (please see the top 2 patches) : https://github.com/dcui/freebsd/commits/decui/10.2/fix_mac_order (I resolved a small code conflict) I verified the 2 patches could be cleanly applied to a clean installation of 10.2 VM: [root@decui-bsd102 /usr/src]# pwd /usr/src [root@decui-bsd102 /usr/src]# wget https://github.com/dcui/freebsd/commit/b706b383da285376554bcb69f44c4cc10270de24.patch --2016-02-04 13:37:04-- https://github.com/dcui/freebsd/commit/b706b383da285376554bcb69f44c4cc10270de24.patch Resolving github.com (github.com)... 192.30.252.131 Connecting to github.com (github.com)|192.30.252.131|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/plain] Saving to: 'b706b383da285376554bcb69f44c4cc10270de24.patch.1' b706b383da285376554bcb69f44c4cc10270de24.pa [ <=> ] 7.13K --.-KB/s in 0.006s 2016-02-04 13:37:05 (1.22 MB/s) - 'b706b383da285376554bcb69f44c4cc10270de24.patch.1' saved [7297] [root@decui-bsd102 /usr/src]# patch -sp1 < b706b383da285376554bcb69f44c4cc10270de24.patch [root@decui-bsd102 /usr/src]# wget https://github.com/dcui/freebsd/commit/2bff041dbed26b5da88c4be72b4701bbf6c460cd.patch --2016-02-04 13:37:26-- https://github.com/dcui/freebsd/commit/2bff041dbed26b5da88c4be72b4701bbf6c460cd.patch Resolving github.com (github.com)... 192.30.252.129 Connecting to github.com (github.com)|192.30.252.129|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/plain] Saving to: '2bff041dbed26b5da88c4be72b4701bbf6c460cd.patch.1' 2bff041dbed26b5da88c4be72b4701bbf6c460cd.pa [ <=> ] 4.22K --.-KB/s in 0.003s 2016-02-04 13:37:27 (1.31 MB/s) - '2bff041dbed26b5da88c4be72b4701bbf6c460cd.patch.1' saved [4323] [root@decui-bsd102 /usr/src]# patch -sp1 < 2bff041dbed26b5da88c4be72b4701bbf6c460cd.patch [root@decui-bsd102 /usr/src]# If the related files in your /usr/src/sys/dev/hyperv/ were messed up by the previous failed patch commands, you can replace the files with the version here (https://github.com/dcui/freebsd/tree/decui/10.2/fix_mac_order/sys/dev/hyperv. You can use the "Raw" format functionality to get the related URLs of the files and use 'wget' to get them): sys/dev/hyperv/include/hyperv.h sys/dev/hyperv/vmbus/hv_channel_mgmt.c sys/dev/hyperv/vmbus/hv_vmbus_drv_freebsd.c sys/dev/hyperv/vmbus/hv_vmbus_priv.h Please let me know if this will work for you. Thanks, -- Dexuan From: Jac Backus [mailto:j.bac...@bugworks.com] Sent: Thursday, February 4, 2016 7:18 To: Dexuan Cui <de...@microsoft.com<mailto:de...@microsoft.com>>; Sephe Qiao (Wicresoft) <v-yan...@microsoft.com<mailto:v-yan...@microsoft.com>>; Kylie Liang <kyl...@microsoft.com<mailto:kyl...@microsoft.com>>; 'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bs...@microsoft.com<mailto:bs...@microsoft.com>> Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Hello Dexuan, The first patch gives no messages. When trying the second: 112 # patch -sp1 < 1e469c559048fe6ec3641da3bb21ab87215c6506.patch 1 out of 7 hunks failed--saving rejects to sys/dev/hyperv/vmbus/hv_channel_mgmt.c.rej Attached you find the patched file (as a session log). With kind regards, Jac Van: Dexuan Cui [mailto:de...@microsoft.com] Verzonden: woensdag 3 februari 2016 10:05 Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualization@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Thanks for the confirmation, Jac. I might be wrong with 10.1 - it may not have the issue. In 10.2 we made a lot of changes and I think the race condition was introduced. To test the 2 patches, you can do something like cd /usr/src (supposing the 10.2 kernel code is in the sys/ sub-directory) wget https://github.com/freebsd/freebsd/commit/850d0994e48b0ef68d33875e26326d44931fcf1e.patch patch -sp1 < 850d0994e48b0ef68d33875e26326d44931fcf1e.patch wget https://github.com/freebsd/freebsd/commit/1e469c559048fe6ec3641da3bb21ab87215c6506.patch patch -sp1 < 1e469c559048fe6ec3641da3bb21ab87215c6506.patch make buildkernel KERNCONF=GENERIC -j8 make installkernel reboot You may get a small issue when applying the second patch as I did: 1 out of 8 hunks failed--saving rejects to sys/dev/hyperv/vmbus/hv_channel_mgmt.c.rej You can fix this by checking the .patch/.c files and manually editing the .c file. Thanks, -- Dexuan From: Jac Backus [mailto:j.bac...@bugworks.com] Sent: Wednesday, February 3, 2016 16:10 To: Dexuan Cui <de...@microsoft.com<mailto:de...@microsoft.com>>; Sephe Qiao (Wicresoft) <v-yan...@microsoft.com<mailto:v-yan...@microsoft.com>>; Kylie Liang <kyl...@microsoft.com<mailto:kyl...@microsoft.com>>; 'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bs...@microsoft.com<mailto:bs...@microsoft.com>> Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Good day Dexuan, I think it is. I should like to test. Are there some instructions for patching the 10.2 kernel source? You mention 10.1 too, but I never had the problem with 10.1. Thanks very for your kind help! With kind regards, Jac Van: Dexuan Cui [mailto:de...@microsoft.com] Verzonden: woensdag 3 februari 2016 1:50 Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualization@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Jac, really great news! So, can I think the whole issue in your side is caused by Bug 205156? The fix to the bug has been in the 10/stable branch and should be in the coming 10.3. For 10.1 and 10.2 , I'm afraid you'll have to manually apply the patches and build a new kernel. BTW, the bug is actually a race condition when the netvsc driver registers multiple NIC devices, so sometimes we can easily repro the issue and sometimes we can't. Thanks, -- Dexuan From: Jac Backus [mailto:j.bac...@bugworks.com] Sent: Wednesday, February 3, 2016 2:28 To: Dexuan Cui <de...@microsoft.com<mailto:de...@microsoft.com>>; Sephe Qiao (Wicresoft) <v-yan...@microsoft.com<mailto:v-yan...@microsoft.com>>; Kylie Liang <kyl...@microsoft.com<mailto:kyl...@microsoft.com>>; 'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bs...@microsoft.com<mailto:bs...@microsoft.com>> Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Dexuan, you are briljant! That is the problem: Hn0 has the mac address of hn1, hn1 of hn2 and hn2 of hn0. So they have shifted one position to the left. With kind regards, Jac Van: Dexuan Cui [mailto:de...@microsoft.com] Verzonden: maandag 1 februari 2016 10:41 Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualization@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hmm, it's really strange... what's the difference between your existing 10.1 VM and a fresh 10.1 VM... :( BTW, please check if you are seeing this bug (it looks in your side the network can stop working after a VM reboot): Bug 205156 - [Hyper-V] NICs' (hn0, hn1) MAC addresses can appear in an uncertain way across reboot (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205156<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fbugs.freebsd.org%2fbugzilla%2fshow_bug.cgi%3fid%3d205156&data=01%7c01%7cdecui%40064d.mgd.microsoft.com%7ce1d0508d7e1a475e9c5d08d32bfef518%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=SIv6Bi0qESksmQD3f1UKYUkoV9yGRL1xajG6K1qSdZA%3d>)? Thanks, -- Dexuan From: Jac Backus [mailto:j.bac...@bugworks.com] Sent: Monday, February 1, 2016 17:17 To: Dexuan Cui <de...@microsoft.com<mailto:de...@microsoft.com>>; Sephe Qiao (Wicresoft) <v-yan...@microsoft.com<mailto:v-yan...@microsoft.com>>; Kylie Liang <kyl...@microsoft.com<mailto:kyl...@microsoft.com>>; 'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bs...@microsoft.com<mailto:bs...@microsoft.com>> Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Good day Dexuan, I did. Unfortunately, no difference. And at the moment the server is running on the 10.2 kernel: uname -a FreeBSD roadrunner.acme.inc 10.2-RELEASE-p9 FreeBSD 10.2-RELEASE-p9 #0: Thu Jan 14 01:32:46 UTC 2016 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC<mailto:r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC> amd64 But there is a big chance, that after a reboot, the network is gone again. I will see if, when it works, it keeps working. I suppose it does. With kind regards, Jac Van: Dexuan Cui [mailto:de...@microsoft.com] Verzonden: maandag 1 februari 2016 3:07 Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualization@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hi Jac, Good to know this! It looks to me something in the VM or in the host might be causing the issue??? Can you please do another quick test: shut down the "buggy" VM and remove it in Hyper-V Manager (this will keep the .vhdx image) and then re-create the VM with the .vhdx image? Thanks, -- Dexuan From: Jac Backus [mailto:j.bac...@bugworks.com] Sent: Sunday, January 31, 2016 23:21 To: Dexuan Cui <de...@microsoft.com<mailto:de...@microsoft.com>>; Sephe Qiao (Wicresoft) <v-yan...@microsoft.com<mailto:v-yan...@microsoft.com>>; Kylie Liang <kyl...@microsoft.com<mailto:kyl...@microsoft.com>>; 'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bs...@microsoft.com<mailto:bs...@microsoft.com>> Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Hello Dexuan, I did a fresh install of a 10.1 VM and upgraded it to 10.2. Is looks like it works well. With kind regards, Jac Van: Dexuan Cui [mailto:de...@microsoft.com] Verzonden: zondag 31 januari 2016 7:07 Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualization@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hi Jac, Good to know the information. Since I can't repro the issue, it's difficult for me to debug it. :( I'm guessing if it would help if you use a permanent ARP entry in the VM ("arp -s hostname ether_addr") for the other end - surely this is only for debug purpose. During the VM boot-up, can you keep pinging the VM from the other host. I mean: it looks the NIC never works since it becomes UP in the VM? BTW, I'm not sure if it's easy for you to do the same test as mine, i.e., do a fresh installation of 10.1 VM and upgrade it to 10.2. @Sephe, any idea? Thanks, -- Dexuan From: Jac Backus [mailto:j.bac...@bugworks.com] Sent: Sunday, January 31, 2016 3:42 To: Dexuan Cui <de...@microsoft.com<mailto:de...@microsoft.com>>; Sephe Qiao (Wicresoft) <v-yan...@microsoft.com<mailto:v-yan...@microsoft.com>>; Kylie Liang <kyl...@microsoft.com<mailto:kyl...@microsoft.com>>; 'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bs...@microsoft.com<mailto:bs...@microsoft.com>> Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Good day Dexuan, There is something wrong with getting mac addresses for host on the lan, it seems. When I ping the 10.2 server from a host on the net, I see on that host arp requests (Wireshark: who has ... Tell ...) for the 10.2 server. Arp -a on the 10.2 server itself says for the non-server entries ? <address> at (imcomplete) on hn0 expired [ethernet] Tcpdump on the 10.2 server only shows arp requests: ARP, Request who-has ... tell ... Does this help? With kind regards, Jac Van: Dexuan Cui [mailto:de...@microsoft.com] Verzonden: vrijdag 29 januari 2016 9:59 Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualization@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hmm, it's strange we can't repro. I suppose you can't ping the netgate VM (or machine) 's IP address either? When this happens, can you check the arp table in both sides? Can you please run tcpdump in the VM and in the gateway to diagnose the issue? Thanks, -- Dexuan From: Jac Backus [mailto:j.bac...@bugworks.com] Sent: Friday, January 29, 2016 15:36 To: Dexuan Cui <de...@microsoft.com<mailto:de...@microsoft.com>>; Sephe Qiao (Wicresoft) <v-yan...@microsoft.com<mailto:v-yan...@microsoft.com>>; Kylie Liang <kyl...@microsoft.com<mailto:kyl...@microsoft.com>>; 'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bs...@microsoft.com<mailto:bs...@microsoft.com>> Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Hello Dexuan, That remarkable. My uname -a is indentical. I can ping local interfaces. Ping to other addresses in local subnet gives: Ping: sendto: Host is down. Ping to other addresses gives: Ping: sendto: No route to host. Routing tables (netstat -rn) for both versions look the same. Is there something I can test? With kind regards, Jac Van: Dexuan Cui [mailto:de...@microsoft.com] Verzonden: vrijdag 29 januari 2016 4:25 Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualization@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hi Jac, I installed a 10.1 VM with FreeBSD-10.1-RELEASE-amd64-dvd1.iso and upgraded it to 10.2 by running "freebsd-update upgrade -r 10.2-RELEASE". Everything worked just fine. With the new kernel (see the below), ssh and scp still works fine for me. # uname -a FreeBSD bsd101 10.2-RELEASE-p9 FreeBSD 10.2-RELEASE-p9 #0: Thu Jan 14 01:32:46 UTC 2016 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC<mailto:r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC> amd64 What's the specific symptom for "networking does not work anymore" in your side(upgrading from 10.1 to 10.2)? Thanks, -- Dexuan From: Jac Backus [mailto:j.bac...@bugworks.com] Sent: Wednesday, January 27, 2016 17:35 To: Dexuan Cui <de...@microsoft.com<mailto:de...@microsoft.com>>; Sephe Qiao (Wicresoft) <v-yan...@microsoft.com<mailto:v-yan...@microsoft.com>>; Kylie Liang <kyl...@microsoft.com<mailto:kyl...@microsoft.com>>; 'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bs...@microsoft.com<mailto:bs...@microsoft.com>> Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Hello Dexuan, Unfortunetely, no OACTIVE flag: hn0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=31b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,TSO6> With kind regards, Jac Van: Dexuan Cui [mailto:de...@microsoft.com] Verzonden: woensdag 27 januari 2016 4:09 Aan: Sephe Qiao (Wicresoft); Jac Backus; Kylie Liang; 'freebsd-virtualization@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2 Hi Jac, Please show 'ifconfig -a' when the issue happens (when you upgrade 10.1 from 10.2). We suspect it may be a known OACTIVE issue and "ifconfig -a' can confirm this, the output has the string "OACTIVE". It looks somehow the issue doesn't happen when we use a 10.2 fresh installation. Thanks, -- Dexuan From: Sephe Qiao (Wicresoft) Sent: Wednesday, January 27, 2016 9:13 To: Jac Backus <j.bac...@bugworks.com<mailto:j.bac...@bugworks.com>>; Dexuan Cui <de...@microsoft.com<mailto:de...@microsoft.com>>; Kylie Liang <kyl...@microsoft.com<mailto:kyl...@microsoft.com>>; 'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bs...@microsoft.com<mailto:bs...@microsoft.com>> Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Oh, please ignore this, I think its solved :) From: Sephe Qiao (Wicresoft) Sent: Wednesday, January 27, 2016 9:10 AM To: Jac Backus <j.bac...@bugworks.com<mailto:j.bac...@bugworks.com>>; Dexuan Cui <de...@microsoft.com<mailto:de...@microsoft.com>>; Kylie Liang <kyl...@microsoft.com<mailto:kyl...@microsoft.com>>; 'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bs...@microsoft.com<mailto:bs...@microsoft.com>> Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Hi Jac, What's the output of 'ifconfig -a' when this happened? Thanks, sephe From: Jac Backus [mailto:j.bac...@bugworks.com] Sent: Tuesday, January 26, 2016 6:37 PM To: Dexuan Cui <de...@microsoft.com<mailto:de...@microsoft.com>>; Kylie Liang <kyl...@microsoft.com<mailto:kyl...@microsoft.com>>; 'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bs...@microsoft.com<mailto:bs...@microsoft.com>> Subject: RE: Hyper-V networking: problem after upgrade to 10.2 Hello Dexuan, It seems, it is not completely correct, although the effect is as if it is not working. Systat -ifstat 1 shows this: [cid:image001.png@01D159DA.65A3A0E0] So something is happening. But I can not reach anything. And the server can not be reached from the lan (hn0) or internet (hn1 and hn2). I get a firewall message in /var/log/messages (first message from 11:18:55): [cid:image002.png@01D159DA.65A3A0E0] But this is just caused by the problem? If I can help with further information, please let me know. Regarding Bug 187006, all interfaces have fixed addresses. With kind regards, Jac -----Oorspronkelijk bericht----- Van: Dexuan Cui [mailto:de...@microsoft.com] Verzonden: dinsdag 26 januari 2016 7:55 Aan: Kylie Liang; Jac Backus; 'freebsd-virtualization@freebsd.org'; BSD Integration Components for Hyper-V Onderwerp: 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<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fbugs.freebsd.org%2fbugzilla%2fshow_bug.cgi%3fid%3d187006&data=01%7c01%7cv-yanqia%40064d.mgd.microsoft.com%7cef82474449e745da88c908d3263e7e48%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=1IyQb3x7ecm%2f6uESQmVAAyAyOQr4ZMJ3Fkawp93dZgQ%3d> ? Thanks, -- Dexuan > -----Original Message----- > From: Dexuan Cui > Sent: Tuesday, January 26, 2016 14:49 > To: Kylie Liang <kyl...@microsoft.com<mailto:kyl...@microsoft.com>>; Jac > Backus > <j.bac...@bugworks.com<mailto:j.bac...@bugworks.com>>; > 'freebsd-virtualization@freebsd.org' > <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>>; > BSD Integration Components for > Hyper-V <bs...@microsoft.com<mailto:bs...@microsoft.com>> > 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 <j.bac...@bugworks.com<mailto:j.bac...@bugworks.com>>; > > 'freebsd- > virtualizat...@freebsd.org<mailto:virtualizat...@freebsd.org>' > > <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>>; > > BSD Integration Components for > > Hyper- > V > > <bs...@microsoft.com<mailto:bs...@microsoft.com>> > > 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> > > [mailto:owner-freebsd- > > virtualizat...@freebsd.org<mailto:virtualizat...@freebsd.org>] On Behalf Of > > Jac > > Backus > > Sent: Tuesday, January 26, 2016 5:56 AM > > To: 'freebsd-virtualization@freebsd.org' > > <freebsd-virtualization@freebsd.org<mailto: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: <Synthetic Network Interface> > > 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: <Synthetic > > Network > > Interface> on vmbus0 Jan 25 21:02:01 mercurius kernel: hn1: unknown > > Interface> 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: <Synthetic > > Network > > Interface> on vmbus0 Jan 25 21:02:01 mercurius kernel: hn2: unknown > > Interface> 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: <Synthetic Network Interface> > > 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 > > Network > > 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: <Synthetic > > Network > > 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<mailto: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<mailto: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"
