Date: Fri, 29 Jan 2016 03:24:36 +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: <0f761afc10864ad3aeb89ee7c9b6e8ac@HKXPR3004MB0088.064d.mgd.msft.net> In-Reply-To: <4e85ad234a0b4618ae5862fbcd266e3d@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 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>; 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,
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?0f761afc10864ad3aeb89ee7c9b6e8ac>