Date: Fri, 5 Feb 2016 08:22:56 +0000 From: Dexuan Cui <decui@microsoft.com> To: Jac Backus <j.backus@bugworks.com>, "Sephe Qiao (Wicresoft)" <v-yanqia@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: <2cdde8e104d04875a3e2614686426375@HKXPR3004MB0088.064d.mgd.msft.net> In-Reply-To: <c8ae33163e914682a17ce33032934c5b@ORTELIUS.internal.bugworks.com> References: <cdb46889a0164856987da43537a104de@ORTELIUS.internal.bugworks.com> <8572369fcc3b408891fc1a5a7d11e892@SG2PR3002MB0107.064d.mgd.msft.net> <bcca15b9c5cd4e0db3d80b40bde7405a@HKXPR3004MB0088.064d.mgd.msft.net> <1430812ff38c4e08a4b91ea25fdb5a7b@HKXPR3004MB0088.064d.mgd.msft.net> <1fdbb9b939c54e31ac00329f61bf6f41@ORTELIUS.internal.bugworks.com> <2323532a95934cdfae0142a9d6f88fd8@SG2PR3004MB0090.064d.mgd.msft.net> <2b22a9544c6c4ff3b017133a346e75e2@SG2PR3004MB0090.064d.mgd.msft.net> <7df41cc958ee408297487d4ffbb91903@HKXPR3004MB0088.064d.mgd.msft.net> <4e85ad234a0b4618ae5862fbcd266e3d@ORTELIUS.internal.bugworks.com> <0f761afc10864ad3aeb89ee7c9b6e8ac@HKXPR3004MB0088.064d.mgd.msft.net> <d1f0f7492a8d4bcca6acc4e7062e7855@ORTELIUS.internal.bugworks.com> <4105829efb1e4b3a91bc17f7fbdf8ac8@HKXPR3004MB0088.064d.mgd.msft.net> <0ce04bf413204478b1e7cc71ac28ecac@ORTELIUS.internal.bugworks.com> <1aba0d827b9041b79b85a09cf70e52b1@HKXPR3004MB0088.064d.mgd.msft.net> <dab71654578744c99e0ca2f800df7929@ORTELIUS.internal.bugworks.com> <d4e895d3f7324773bbe3459bc6522dd3@HKXPR3004MB0088.064d.mgd.msft.net> <e23579410d8240fd92e21cbd5bec98ac@ORTELIUS.internal.bugworks.com> <4a98b41221ed4c3b84a8c733aa23f24d@HKXPR3004MB0088.064d.mgd.msft.net> <d9312cab2a514d2790d4ad6e452b1c05@ORTELIUS.internal.bugworks.com> <da559e9f67414d6baa0a57267a64d837@HKXPR3004MB0088.064d.mgd.msft.net> <5a09277abe094f5989fb145c12a511df@ORTELIUS.internal.bugworks.com> <17b639f383df4f42b1e050f6e40d1ad2@HKXPR3004MB0088.064d.mgd.msft.net> <53238096372f4362b436382a430bde57@ORTELIUS.internal.bugworks.com> <c6faac28f3c34158a3b15743017b67ea@HKXPR3004MB0088.064d.mgd.msft.net> <c8ae33163e914682a17ce33032934c5b@ORTELIUS.internal.bugworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Jac,
Thanks for confirming the fixes!
Please let me explain the issue a little more. The issue exists in the VMBu=
s driver. Since the network driver depends on the VMBus driver, we have the=
issue.
The issue is: the VMBus doesn't guarantee the serialization of registering =
multiple NICs, e.g., supposing the VM has 2 NICs (NIC1 with MAC1 and NIC2 w=
ith MAC2), 2 kernel threads (FreeBSD's taskqueues) are created to register =
the NICs concurrently; if sometimes NIC1 is registered first, NIC1 will be =
"hn0"and sometimes if NIC2 is registered first, NIC2 will be "hn0"...
My fixes make sure the proper serialization, so now we can make sure NIC1 i=
s always registered before NIC2.
About another issue ("calcru: runtime went backwards"), I made a fix recent=
ly: https://reviews.freebsd.org/D5174. Please try it.
I'm trying to push this fix to the Head branch.
Thanks,
-- Dexuan
From: Jac Backus [mailto:j.backus@bugworks.com]
Sent: Friday, February 5, 2016 15:55
To: Dexuan Cui <decui@microsoft.com>; Sephe Qiao (Wicresoft) <v-yanqia@micr=
osoft.com>; Kylie Liang <kyliel@microsoft.com>; 'freebsd-virtualization@fre=
ebsd.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
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 de=
fined 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 o=
f these messages when I boot:
calcru: runtime went backwards from 1672 usec to 845 usec for pid 144 (adjk=
erntz)
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_ite=
rator)
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 (ge=
om)
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 (k=
ernel)
I happens since I virtualized the server.
Again, I thank you very much for the help. And, of course, especially for t=
he fix!
With kind regards,
Jac
Van: Dexuan Cui [mailto:decui@microsoft.com]
Verzonden: donderdag 4 februari 2016 7:01
Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualizati=
on@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_ord=
er" (please see the top 2 patches) :
https://github.com/dcui/freebsd/commits/decui/10.2/fix_mac_order (I resolve=
d a small code conflict)
I verified the 2 patches could be cleanly applied to a clean installation o=
f 10.2 VM:
[root@decui-bsd102 /usr/src]# pwd
/usr/src
[root@decui-bsd102 /usr/src]# wget https://github.com/dcui/freebsd/commit/b=
706b383da285376554bcb69f44c4cc10270de24.patch
--2016-02-04 13:37:04-- https://github.com/dcui/freebsd/commit/b706b383da2=
85376554bcb69f44c4cc10270de24.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 [ <=3D> =
] 7.13=
K --.-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 < b706b383da285376554bcb69f44c4cc1=
0270de24.patch
[root@decui-bsd102 /usr/src]# wget https://github.com/dcui/freebsd/commit/2=
bff041dbed26b5da88c4be72b4701bbf6c460cd.patch
--2016-02-04 13:37:26-- https://github.com/dcui/freebsd/commit/2bff041dbed=
26b5da88c4be72b4701bbf6c460cd.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 [ <=3D> =
] 4.22=
K --.-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 < 2bff041dbed26b5da88c4be72b4701bb=
f6c460cd.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/de=
v/hyperv. You can use the "Raw" format functionality to get the related URL=
s 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.backus@bugworks.com]
Sent: Thursday, February 4, 2016 7:18
To: Dexuan Cui <decui@microsoft.com<mailto:decui@microsoft.com>>; Sephe Qia=
o (Wicresoft) <v-yanqia@microsoft.com<mailto:v-yanqia@microsoft.com>>; Kyli=
e Liang <kyliel@microsoft.com<mailto:kyliel@microsoft.com>>; 'freebsd-virtu=
alization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-v=
irtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bsdic@=
microsoft.com<mailto:bsdic@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:decui@microsoft.com]
Verzonden: woensdag 3 februari 2016 10:05
Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualizati=
on@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 introdu=
ced.
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/850d0994e48b0ef68d33875e2632=
6d44931fcf1e.patch
patch -sp1 < 850d0994e48b0ef68d33875e26326d44931fcf1e.patch
wget https://github.com/freebsd/freebsd/commit/1e469c559048fe6ec3641da3bb21=
ab87215c6506.patch
patch -sp1 < 1e469c559048fe6ec3641da3bb21ab87215c6506.patch
make buildkernel KERNCONF=3DGENERIC -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.backus@bugworks.com]
Sent: Wednesday, February 3, 2016 16:10
To: Dexuan Cui <decui@microsoft.com<mailto:decui@microsoft.com>>; Sephe Qia=
o (Wicresoft) <v-yanqia@microsoft.com<mailto:v-yanqia@microsoft.com>>; Kyli=
e Liang <kyliel@microsoft.com<mailto:kyliel@microsoft.com>>; 'freebsd-virtu=
alization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-v=
irtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bsdic@=
microsoft.com<mailto:bsdic@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 ke=
rnel 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:decui@microsoft.com]
Verzonden: woensdag 3 februari 2016 1:50
Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualizati=
on@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 co=
ming 10.3.
For 10.1 and 10.2 , I'm afraid you'll have to manually apply the patches an=
d 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 someti=
mes we can't.
Thanks,
-- Dexuan
From: Jac Backus [mailto:j.backus@bugworks.com]
Sent: Wednesday, February 3, 2016 2:28
To: Dexuan Cui <decui@microsoft.com<mailto:decui@microsoft.com>>; Sephe Qia=
o (Wicresoft) <v-yanqia@microsoft.com<mailto:v-yanqia@microsoft.com>>; Kyli=
e Liang <kyliel@microsoft.com<mailto:kyliel@microsoft.com>>; 'freebsd-virtu=
alization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-v=
irtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bsdic@=
microsoft.com<mailto:bsdic@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:decui@microsoft.com]
Verzonden: maandag 1 februari 2016 10:41
Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualizati=
on@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 ne=
twork can stop working after a VM reboot):
Bug 205156 - [Hyper-V] NICs' (hn0, hn1) MAC addresses can appear in an unce=
rtain way across reboot (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=
=3D205156<https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3a%2f%=
2fbugs.freebsd.org%2fbugzilla%2fshow_bug.cgi%3fid%3d205156&data=3D01%7c01%7=
cdecui%40064d.mgd.microsoft.com%7ce1d0508d7e1a475e9c5d08d32bfef518%7c72f988=
bf86f141af91ab2d7cd011db47%7c1&sdata=3DSIv6Bi0qESksmQD3f1UKYUkoV9yGRL1xajG6=
K1qSdZA%3d>)?
Thanks,
-- Dexuan
From: Jac Backus [mailto:j.backus@bugworks.com]
Sent: Monday, February 1, 2016 17:17
To: Dexuan Cui <decui@microsoft.com<mailto:decui@microsoft.com>>; Sephe Qia=
o (Wicresoft) <v-yanqia@microsoft.com<mailto:v-yanqia@microsoft.com>>; Kyli=
e Liang <kyliel@microsoft.com<mailto:kyliel@microsoft.com>>; 'freebsd-virtu=
alization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-v=
irtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bsdic@=
microsoft.com<mailto:bsdic@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 root@amd64-builder.daemonology.net:/usr/obj/u=
sr/src/sys/GENERIC<mailto:root@amd64-builder.daemonology.net:/usr/obj/usr/s=
rc/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:decui@microsoft.com]
Verzonden: maandag 1 februari 2016 3:07
Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualizati=
on@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 issu=
e???
Can you please do another quick test: shut down the "buggy" VM and remove i=
t in Hyper-V Manager (this will keep the .vhdx image) and then re-create th=
e VM with the .vhdx image?
Thanks,
-- Dexuan
From: Jac Backus [mailto:j.backus@bugworks.com]
Sent: Sunday, January 31, 2016 23:21
To: Dexuan Cui <decui@microsoft.com<mailto:decui@microsoft.com>>; Sephe Qia=
o (Wicresoft) <v-yanqia@microsoft.com<mailto:v-yanqia@microsoft.com>>; Kyli=
e Liang <kyliel@microsoft.com<mailto:kyliel@microsoft.com>>; 'freebsd-virtu=
alization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-v=
irtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bsdic@=
microsoft.com<mailto:bsdic@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 i=
t works well.
With kind regards,
Jac
Van: Dexuan Cui [mailto:decui@microsoft.com]
Verzonden: zondag 31 januari 2016 7:07
Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualizati=
on@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 de=
bug purpose.
During the VM boot-up, can you keep pinging the VM from the other host. I m=
ean: 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., d=
o a fresh installation of 10.1 VM and upgrade it to 10.2.
@Sephe, any idea?
Thanks,
-- Dexuan
From: Jac Backus [mailto:j.backus@bugworks.com]
Sent: Sunday, January 31, 2016 3:42
To: Dexuan Cui <decui@microsoft.com<mailto:decui@microsoft.com>>; Sephe Qia=
o (Wicresoft) <v-yanqia@microsoft.com<mailto:v-yanqia@microsoft.com>>; Kyli=
e Liang <kyliel@microsoft.com<mailto:kyliel@microsoft.com>>; 'freebsd-virtu=
alization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-v=
irtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bsdic@=
microsoft.com<mailto:bsdic@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:decui@microsoft.com]
Verzonden: vrijdag 29 januari 2016 9:59
Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualizati=
on@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 iss=
ue?
Thanks,
-- Dexuan
From: Jac Backus [mailto:j.backus@bugworks.com]
Sent: Friday, January 29, 2016 15:36
To: Dexuan Cui <decui@microsoft.com<mailto:decui@microsoft.com>>; Sephe Qia=
o (Wicresoft) <v-yanqia@microsoft.com<mailto:v-yanqia@microsoft.com>>; Kyli=
e Liang <kyliel@microsoft.com<mailto:kyliel@microsoft.com>>; 'freebsd-virtu=
alization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-v=
irtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bsdic@=
microsoft.com<mailto:bsdic@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: N=
o 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:decui@microsoft.com]
Verzonden: vrijdag 29 januari 2016 4:25
Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 'freebsd-virtualizati=
on@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 s=
cp 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 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GE=
NERIC<mailto:root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERI=
C> 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.backus@bugworks.com]
Sent: Wednesday, January 27, 2016 17:35
To: Dexuan Cui <decui@microsoft.com<mailto:decui@microsoft.com>>; Sephe Qia=
o (Wicresoft) <v-yanqia@microsoft.com<mailto:v-yanqia@microsoft.com>>; Kyli=
e Liang <kyliel@microsoft.com<mailto:kyliel@microsoft.com>>; 'freebsd-virtu=
alization@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-v=
irtualization@freebsd.org>>; BSD Integration Components for Hyper-V <bsdic@=
microsoft.com<mailto:bsdic@microsoft.com>>
Subject: RE: Hyper-V networking: problem after upgrade to 10.2
Hello Dexuan,
Unfortunetely, no OACTIVE flag:
hn0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=3D31b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,TSO6>
With kind regards,
Jac
Van: Dexuan Cui [mailto:decui@microsoft.com]
Verzonden: woensdag 27 januari 2016 4:09
Aan: Sephe Qiao (Wicresoft); Jac Backus; Kylie Liang; 'freebsd-virtualizati=
on@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 fro=
m 10.2).
We suspect it may be a known OACTIVE issue and "ifconfig -a' can confirm th=
is, the output has the string "OACTIVE".
It looks somehow the issue doesn't happen when we use a 10.2 fresh installa=
tion.
Thanks,
-- Dexuan
From: Sephe Qiao (Wicresoft)
Sent: Wednesday, January 27, 2016 9:13
To: Jac Backus <j.backus@bugworks.com<mailto:j.backus@bugworks.com>>; Dexua=
n Cui <decui@microsoft.com<mailto:decui@microsoft.com>>; Kylie Liang <kylie=
l@microsoft.com<mailto:kyliel@microsoft.com>>; 'freebsd-virtualization@free=
bsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@=
freebsd.org>>; BSD Integration Components for Hyper-V <bsdic@microsoft.com<=
mailto:bsdic@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.backus@bugworks.com<mailto:j.backus@bugworks.com>>; Dexua=
n Cui <decui@microsoft.com<mailto:decui@microsoft.com>>; Kylie Liang <kylie=
l@microsoft.com<mailto:kyliel@microsoft.com>>; 'freebsd-virtualization@free=
bsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@=
freebsd.org>>; BSD Integration Components for Hyper-V <bsdic@microsoft.com<=
mailto:bsdic@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.backus@bugworks.com]
Sent: Tuesday, January 26, 2016 6:37 PM
To: Dexuan Cui <decui@microsoft.com<mailto:decui@microsoft.com>>; Kylie Lia=
ng <kyliel@microsoft.com<mailto:kyliel@microsoft.com>>; 'freebsd-virtualiza=
tion@freebsd.org' <freebsd-virtualization@freebsd.org<mailto:freebsd-virtua=
lization@freebsd.org>>; BSD Integration Components for Hyper-V <bsdic@micro=
soft.com<mailto:bsdic@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:decui@microsoft.com]
Verzonden: dinsdag 26 januari 2016 7:55
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,
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 HYP=
ER-V OS 2012 R2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D187006<https://na01.saf=
elinks.protection.outlook.com/?url=3Dhttps%3a%2f%2fbugs.freebsd.org%2fbugzi=
lla%2fshow_bug.cgi%3fid%3d187006&data=3D01%7c01%7cv-yanqia%40064d.mgd.micro=
soft.com%7cef82474449e745da88c908d3263e7e48%7c72f988bf86f141af91ab2d7cd011d=
b47%7c1&sdata=3D1IyQb3x7ecm%2f6uESQmVAAyAyOQr4ZMJ3Fkawp93dZgQ%3d> ?
Thanks,
-- Dexuan
> -----Original Message-----
> From: Dexuan Cui
> Sent: Tuesday, January 26, 2016 14:49
> To: Kylie Liang <kyliel@microsoft.com<mailto:kyliel@microsoft.com>>; Jac =
Backus
> <j.backus@bugworks.com<mailto:j.backus@bugworks.com>>; 'freebsd-virtualiz=
ation@freebsd.org'
> <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd=
.org>>; BSD Integration Components for
> Hyper-V <bsdic@microsoft.com<mailto:bsdic@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.backus@bugworks.com<mailto:j.backus@bugworks.com>>; '=
freebsd-
> virtualization@freebsd.org<mailto:virtualization@freebsd.org>'
> > <freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freeb=
sd.org>>; BSD Integration Components for
> > Hyper-
> V
> > <bsdic@microsoft.com<mailto:bsdic@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-virtualization@freebsd.org<mailto:owner-freebsd-vir=
tualization@freebsd.org>
> > [mailto:owner-freebsd- virtualization@freebsd.org<mailto:virtualization=
@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@freeb=
sd.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: U=
sing 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 wo=
rks 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 ad=
dress:
> > 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 ad=
dress:
> > 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@freebs=
d.org> mailing list
> >
> 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-
> > unsubscribe@freebsd.org<mailto:unsubscribe@freebsd.org>"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2cdde8e104d04875a3e2614686426375>