RE: Hyper-V networking: problem after upgrade to 10.2

[Dexuan Cui]

Hi Jac,
Thanks for confirming the fixes!

Please let me explain the issue a little more. The issue exists in the VMBus 
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 with 
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 is 
always registered before NIC2.

About another issue ("calcru: runtime went backwards"), I made a fix recently: 
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.bac...@bugworks.com]
Sent: Friday, February 5, 2016 15:55
To: Dexuan Cui <de...@microsoft.com>; Sephe Qiao (Wicresoft) 
<v-yan...@microsoft.com>; Kylie Liang <kyl...@microsoft.com>; 
'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org>; BSD 
Integration Components for Hyper-V <bs...@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 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) - 
'2bff04

RE: Hyper-V networking: problem after upgrade to 10.2

[Dexuan Cui]

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>; Sephe Qiao (Wicresoft) 
<v-yan...@microsoft.com>; Kylie Liang <kyl...@microsoft.com>; 
'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org>; BSD 
Integration Components for Hyper-V <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: We

RE: Hyper-V networking: problem after upgrade to 10.2

[Dexuan Cui]

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>; Sephe Qiao (Wicresoft) 
<v-yan...@microsoft.com>; Kylie Liang <kyl...@microsoft.com>; 
'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org>; BSD 
Integration Components for Hyper-V <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=01%7c01%7cdecui%40064d.mgd.microsoft.com%7ce1d0508d7e1a475e9c5d08d32bfef518%7c72f988bf86f141af91ab2d7cd011db47%7c1=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

RE: Hyper-V networking: problem after upgrade to 10.2

[Jac Backus]

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=01%7c01%7cdecui%40064d.mgd.microsoft.com%7ce1d0508d7e1a475e9c5d08d32bfef518%7c72f988bf86f141af91ab2d7cd011db47%7c1=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

RE: Hyper-V networking: problem after upgrade to 10.2

[Dexuan Cui]

Or, you can just use the 10/stable branch, which has included the fixes for 
this issue:

git clone 
g...@github.com:freebsd/freebsd.git<mailto:g...@github.com:freebsd/freebsd.git>
cd freebsd
git checkout -b local/stable/10 origin/stable/10
make buildkernel KERNCONF=GENERIC -j8
make installkernel
reboot

Thanks,
-- Dexuan

From: Dexuan Cui
Sent: Wednesday, February 3, 2016 17:05
To: Jac Backus <j.bac...@bugworks.com>; Sephe Qiao (Wicresoft) 
<v-yan...@microsoft.com>; Kylie Liang <kyl...@microsoft.com>; 
'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org>; BSD 
Integration Components for Hyper-V <bs...@microsoft.com>
Subject: 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=01%7c01%7cdecui%40064d.mgd.microsoft.com%7ce1d0508d7e1a475e9c5d08d32bfef

RE: Hyper-V networking: problem after upgrade to 10.2

[Jac Backus]

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=01%7c01%7cdecui%40064d.mgd.microsoft.com%7ce1d0508d7e1a475e9c5d08d32bfef518%7c72f988bf86f141af91ab2d7cd011db47%7c1=SIv6Bi0qESksmQD3f1UKYUkoV9yGRL1xajG6K1qSdZA%3d>)?

Thanks,
-- Dexuan

From: Jac Backus [mailto:j

RE: Hyper-V networking: problem after upgrade to 10.2

[Jac Backus]

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)?

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 ma

RE: Hyper-V networking: problem after upgrade to 10.2

[Dexuan Cui]

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>; Sephe Qiao (Wicresoft) 
<v-yan...@microsoft.com>; Kylie Liang <kyl...@microsoft.com>; 
'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org>; BSD 
Integration Components for Hyper-V <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=01%7c01%7cdecui%40064d.mgd.microsoft.com%7ce1d0508d7e1a475e9c5d08d32bfef518%7c72f988bf86f141af91ab2d7cd011db47%7c1=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 m

RE: Hyper-V networking: problem after upgrade to 10.2

[Dexuan Cui]

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)?

Thanks,
-- Dexuan

From: Jac Backus [mailto:j.bac...@bugworks.com]
Sent: Monday, February 1, 2016 17:17
To: Dexuan Cui <de...@microsoft.com>; Sephe Qiao (Wicresoft) 
<v-yan...@microsoft.com>; Kylie Liang <kyl...@microsoft.com>; 
'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org>; BSD 
Integration Components for Hyper-V <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
 ?  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
Onde

RE: Hyper-V networking: problem after upgrade to 10.2

[Jac Backus]

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  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
 ?  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: 

RE: Hyper-V networking: problem after upgrade to 10.2

[Jac Backus]

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
 ?  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' 

RE: Hyper-V networking: problem after upgrade to 10.2

[Dexuan Cui]

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>; Sephe Qiao (Wicresoft) 
<v-yan...@microsoft.com>; Kylie Liang <kyl...@microsoft.com>; 
'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org>; BSD 
Integration Components for Hyper-V <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
 ?  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.

# unam

RE: Hyper-V networking: problem after upgrade to 10.2

[Jac Backus]

Hello Dexuan,

Out of the blue, now it works!

After my test with the static arp entry, I found the following:
http://unix.stackexchange.com/questions/247569/freebsd-adding-ip-alias-to-interface-breaks-network-on-primary-ip

So I rebooted the 10.2 kernel again, to test this. Nothing else. And networking 
worked! I am completely baffled.

When it starts working like this, it could stop working again as easy, so it 
would be nice  to know what the problem is.

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
 ?  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.b

RE: Hyper-V networking: problem after upgrade to 10.2

[Jac Backus]

Hello Marie Helene,

Thanks for your reply!

All hardware acceleration is disabled in the Hyper-V settings, so is DHCP 
guard. All addresses of the VM are fixed.
How do I check this enabled or disabled in the FreeBSD VM? I did not configure 
it.

With kind regards,

Jac

Van: Marie Helene Kvello-Aune [mailto:mariehelen...@gmail.com]
Verzonden: zondag 31 januari 2016 13:25
Aan: Dexuan Cui; 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

I had this issue with a Windows Server 2012 R2 Hyper-V host and FreeBSD 10.1 
sometime last year, but chalked it up to a random fault during upgrade. It 
wasn't a production VM so I didn't put much effort into debugging it at the 
time.

I remember I was using SR-IOV on the virtual network switch, and had it enabled 
on the VM as well. I had also enabled DHCP guard. Maybe some of these settings 
are relevant to reproducing the bug?

Regards,
Marie Helene Kvello-Aune

On Sun, Jan 31, 2016 at 1:15 PM Dexuan Cui 
<de...@microsoft.com<mailto:de...@microsoft.com>> wrote:
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<mailto:j.bac...@bugworks.com>]
Sent: Sunday, January 31, 2016 3:42
To: Dexuan Cui 
<de...@microsoft.com<mailto:de...@microsoft.com><mailto:de...@microsoft.com<mailto:de...@microsoft.com>>>;
 Sephe Qiao (Wicresoft) 
<v-yan...@microsoft.com<mailto:v-yan...@microsoft.com><mailto:v-yan...@microsoft.com<mailto:v-yan...@microsoft.com>>>;
 Kylie Liang 
<kyl...@microsoft.com<mailto:kyl...@microsoft.com><mailto:kyl...@microsoft.com<mailto:kyl...@microsoft.com>>>;
 
'freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>' 
<freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org><mailto:freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>>>;
 BSD Integration Components for Hyper-V 
<bs...@microsoft.com<mailto:bs...@microsoft.com><mailto: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
 ?  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<mailto:de...@microsoft.com>]
Verzonden: vrijdag 29 januari 2016 9:59
Aan: Jac Backus; Sephe Qiao (Wicresoft); Kylie Liang; 
'freebsd-virtualization@freebsd.org<mailto: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<mailto:j.bac...@bugworks.com>]
Sent: Friday, January 29, 2016 15:36
To: Dexuan Cui 
<de...@microsoft.com<mailto:de...@microsoft.com><mailto:de...@microsoft.com<mailto:de...@microsoft.com>>>;
 Sephe Qiao (Wicresoft) 
<v-yan...@microsoft.com<mailto:v-yan...@microsoft.com><mailto:v-yan...@microsoft.com<mailto:v-yan...@microsoft.com>>>;
 Kylie Liang 
<kyl...@microsoft.com<mailto:kyl...@microsoft.com><mailto:kyl...@microsoft.com<mailto:kyl...@microsoft.com>>>;
 
'freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>' 
<freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org><mailto:freebsd-virtualization@freebsd.org<mailto:freebsd-virtualization@freebsd.org>>>;
 BSD Integration Components for Hyper-V 
<bs...@microsoft.com<mailto:bs...@microsoft.com><mailto:bs...@microsoft.com<mailt

RE: Hyper-V networking: problem after upgrade to 10.2

[Dexuan Cui]

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
 ?  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<

Re: Hyper-V networking: problem after upgrade to 10.2

[Marie Helene Kvello-Aune]

Hey Jac.
The setting was enabled in the VM configuration in Hyper-V, for the network
card. No such configuration in the guest OS itself.
As you've not enabled these features, it doesn't seem those are related to
the problem.

Regards,
Marie Helene

On Sun, Jan 31, 2016 at 1:45 PM Jac Backus <j.bac...@bugworks.com> wrote:

> Hello Marie Helene,
>
>
>
> Thanks for your reply!
>
>
>
> All hardware acceleration is disabled in the Hyper-V settings, so is DHCP
> guard. All addresses of the VM are fixed.
>
> How do I check this enabled or disabled in the FreeBSD VM? I did not
> configure it.
>
>
>
> With kind regards,
>
>
>
> Jac
>
>
>
> *Van:* Marie Helene Kvello-Aune [mailto:mariehelen...@gmail.com]
> *Verzonden:* zondag 31 januari 2016 13:25
> *Aan:* Dexuan Cui; 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
>
>
>
> I had this issue with a Windows Server 2012 R2 Hyper-V host and FreeBSD
> 10.1 sometime last year, but chalked it up to a random fault during
> upgrade. It wasn't a production VM so I didn't put much effort into
> debugging it at the time.
>
>
>
> I remember I was using SR-IOV on the virtual network switch, and had it
> enabled on the VM as well. I had also enabled DHCP guard. Maybe some of
> these settings are relevant to reproducing the bug?
>
>
>
> Regards,
>
> Marie Helene Kvello-Aune
>
>
>
> On Sun, Jan 31, 2016 at 1:15 PM Dexuan Cui <de...@microsoft.com> wrote:
>
> 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
>  ?  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,
>
> T

Re: Hyper-V networking: problem after upgrade to 10.2

[Marie Helene Kvello-Aune]

I had this issue with a Windows Server 2012 R2 Hyper-V host and FreeBSD
10.1 sometime last year, but chalked it up to a random fault during
upgrade. It wasn't a production VM so I didn't put much effort into
debugging it at the time.

I remember I was using SR-IOV on the virtual network switch, and had it
enabled on the VM as well. I had also enabled DHCP guard. Maybe some of
these settings are relevant to reproducing the bug?

Regards,
Marie Helene Kvello-Aune

On Sun, Jan 31, 2016 at 1:15 PM Dexuan Cui <de...@microsoft.com> wrote:

> 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
>  ?  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:
&

RE: Hyper-V networking: problem after upgrade to 10.2

[Jac Backus]

Hello Dexuan,

I would think too this would work, but it doesn't. After adding, the entry is 
there, but I can not ping it.

No, the nic never works. Although I can ping it from the server itself. And 
ifconfig shows it as up, of course.

Of course I could this as a test, the upgrade. And see if it has the same 
problem?

It looks like the nics in the 10.2 are working as such. So does Hyper-V 
networking. But  there is no communication between the nics in the 10.2 kernel 
and the Hyper-V network environment.

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
 ?  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

RE: Hyper-V networking: problem after upgrade to 10.2

[Jac Backus]

And, yes, after a reboot is gone again.

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
 ?  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>&g

RE: Hyper-V networking: problem after upgrade to 10.2

[Jac Backus]

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
 ?  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: Hy

RE: Hyper-V networking: problem after upgrade to 10.2

[Dexuan Cui]

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>; Sephe Qiao (Wicresoft) 
<v-yan...@microsoft.com>; Kylie Liang <kyl...@microsoft.com>; 
'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org>; BSD 
Integration Components for Hyper-V <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 

RE: Hyper-V networking: problem after upgrade to 10.2

[Jac Backus]

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 

RE: Hyper-V networking: problem after upgrade to 10.2

[Jac Backus]

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@01D158E9.38DFF280]



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@01D158E9.38DFF280]

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=01%7c01%7cv-yanqia%40064d.mgd.microsoft.com%7cef82474449e745da88c908d3263e7e48%7c72f988bf86f141af91ab2d7cd011db47%7c1=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 "

RE: Hyper-V networking: problem after upgrade to 10.2

[Jac Backus]

Hello Dexuan,

I did fresh installation with the current FreeBSD-10.2-RELEASE-amd64-dvd1.iso 
and this works.
Even with the message, as you already mentioned.

With kind regards,

Jac

-Oorspronkelijk bericht-
Van: Dexuan Cui [mailto:de...@microsoft.com] 
Verzonden: dinsdag 26 januari 2016 7:49
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,
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>; 'freebsd-virtualization@freebsd.org'
> <freebsd-virtualization@freebsd.org>; BSD Integration Components for 
> Hyper-V <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] On Behalf Of Jac Backus
> Sent: Tuesday, January 26, 2016 5:56 AM
> To: 'freebsd-virtualization@freebsd.org' 
> <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:  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:  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:  
> 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:  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:  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 mailing list 
> https://na01.safelinks.protection.outlook.com/

RE: Hyper-V networking: problem after upgrade to 10.2

[Dexuan Cui]

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>; Dexuan Cui <de...@microsoft.com>; Kylie 
Liang <kyl...@microsoft.com>; 'freebsd-virtualization@freebsd.org' 
<freebsd-virtualization@freebsd.org>; BSD Integration Components for Hyper-V 
<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@01D158F3.2E0CC0E0]



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@01D158F3.2E0CC0E0]

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=01%7c01%7cv-yanqia%40064d.mgd.microsoft.com%7cef82474449e745da88c908d3263e7e48%7c72f988bf86f141af91ab2d7cd011db47%7c1=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-

RE: Hyper-V networking: problem after upgrade to 10.2

[Jac Backus]

Hello Dexuan,

You too, thanks for the reply!

I disabled TSO, but it makes no difference. I disable VMQ

I mentioned the message because it was the only difference I saw.

I will do this installation later today. I'll let you know.

I did the upgrade according to  2.2 Upgrading FreeBSD from  
https://www.freebsd.org/releases/10.2R/installation.html
So, essentially I did run:
freebsd-update upgrade -r 10.2-RELEASE
It went without a problem, as far as I can see.

With kind regards,

Jac
-Oorspronkelijk bericht-
Van: Dexuan Cui [mailto:de...@microsoft.com] 
Verzonden: dinsdag 26 januari 2016 7:49
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,
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>; 'freebsd-virtualization@freebsd.org'
> <freebsd-virtualization@freebsd.org>; BSD Integration Components for 
> Hyper-V <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] On Behalf Of Jac Backus
> Sent: Tuesday, January 26, 2016 5:56 AM
> To: 'freebsd-virtualization@freebsd.org' 
> <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:  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:  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:  
> 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:  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:  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 doe

RE: Hyper-V networking: problem after upgrade to 10.2

[Kylie Liang]

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:  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://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2flists.freebsd.org%2fmailman%2flistinfo%2ffreebsd-virtualization=01%7c01%7ckyliel%40064d.mgd.microsoft.com%7cc9ca2e0d0fef482b553f08d325d3aefb%7c72f988bf86f141af91ab2d7cd011db47%7c1=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"

RE: Hyper-V networking: problem after upgrade to 10.2

[Dexuan Cui]

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 <kyl...@microsoft.com>; Jac Backus <j.bac...@bugworks.com>;
> 'freebsd-virtualization@freebsd.org' <freebsd-virtualization@freebsd.org>; BSD
> Integration Components for Hyper-V <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>; 'freebsd-
> virtualizat...@freebsd.org'
> > <freebsd-virtualization@freebsd.org>; BSD Integration Components for Hyper-
> V
> > <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] On Behalf Of Jac Backus
> > Sent: Tuesday, January 26, 2016 5:56 AM
> > To: 'freebsd-virtualization@freebsd.org' 
> > <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 vm

Re: Hyper-V

[Pavel Timofeev]

I figured out another operations that cause caclru message appearance,
such as 'top -n', car /proc/0/status, etc.
But I tried these on 9.2-RELEASE LIVE CD and I saw calcru messages.

So it seems like it's not related to brand new hyper-v integrated
components. It's related to whole FreeBSD system. Which part? I don't
know.

2013/11/12 Pavel Timofeev tim...@gmail.com:
 So, we catched the bug that caused crash. Thanks to all. Cool!

 As regards the messages about calcru: I tried to install CentOS 6.4
 on new virt machine on same host system. Linux doesn't have any
 strange messages about time.
 I tried to migrate FreeBSD and CentOS virt machines to another host
 which has another hardware. Same story.

 For example, try to boot beta-3 in LIVE CD mode. You won't see calcru
 messages. But if you try to run 'dclient hn0' you'll see calcru
 message storm for some time.
 On already installed system I can cause messages by doing
 service zabbix_server start (even if it's not allowed in rc.conf (!))

 But I can start mysql-server, zabbix_agentd, apache22 and it doesn't
 cause appearance of calcru messages.


 Any ideas? How and where can I dig?

 2013/11/6 Pavel Timofeev tim...@gmail.com:
 Small fix:
 kern.timecounter.hardware=TSC covered messages, but now it looks stange
 % time sleep 30
20.24 real 0.00 user 0.00 sys

 2013/11/6 Pavel Timofeev tim...@gmail.com:
 I already tried disabling Hyper-v time syncing, setting
 kern.timecounter.hardware to different type from
 kern.timecounter.choice, setting kern.hz to different values. But
 nothing helped.
 I'll try to install CentOS 6.4 on this machine and see what happens.

 2013/11/6 Pavel Timofeev tim...@gmail.com:
 Does anybody know how to disable Hyper-v time syncing it guest FreeBSD
 OS? I'd like to try this one.

 2013/11/6 Pavel Timofeev tim...@gmail.com:
 Thank you very much!
 I started to dig, and found that I can reboot my server running under
 Hyper-V by doing 'sysctl -a'.
 Can anybody confirm same behavoiur?

 FreeBSD 10.0-BETA3, Win 2012 Datacenter

 2013/11/5 Julian Elischer jul...@freebsd.org:
 On 11/4/13, 11:13 PM, Pavel Timofeev wrote:

 Hi! I upgraded to 10.0-BETA3 but still see messages like

 Tue Nov  5 11:09:05 MSK 2013
 calcru: runtime went backwards from 1728 usec to 889 usec for pid 981
 (zabbix_server)
 calcru: runtime went backwards from 1229 usec to 703 usec for pid 976
 (zabbix_server)
 calcru: runtime went backwards from 1019 usec to 595 usec for pid 978
 (zabbix_server)
 calcru: runtime went backwards from 3041 usec to 1611 usec for pid 969
 (zabbix_server)
 calcru: runtime went backwards from 1078 usec to 595 usec for pid 975
 (zabbix_server)
 calcru: runtime went backwards from 1114 usec to 617 usec for pid 980
 (zabbix_server)
 calcru: runtime went backwards from 1086 usec to 602 usec for pid 977
 (zabbix_server)
 calcru: runtime went backwards from 1195 usec to 782 usec for pid 970
 (zabbix_server)
 calcru: runtime went backwards from 3206 usec to 2157 usec for pid 979
 (zabbix_server)
 calcru: runtime went backwards from 2179 usec to 1542 usec for pid 972
 (zabbix_server)
 calcru: runtime went backwards from 1833 usec to 927 usec for pid 1026
 (cron)
 calcru: runtime went backwards from 1091 usec to 551 usec for pid 1022
 (sendmail)
 calcru: runtime went backwards from 823 usec to 416 usec for pid 1022
 (sendmail)
 calcru: runtime went backwards from 4691 usec to 2735 usec for pid
 1011 (sendmail)
 calcru: runtime went backwards from 1162 usec to 587 usec for pid 1011
 (sendmail)
 calcru: runtime went backwards from 947 usec to 478 usec for pid 1010
 (httpd)
 calcru: runtime went backwards from 895 usec to 452 usec for pid 1009
 (httpd)
 calcru: runtime went backwards from 954 usec to 482 usec for pid 1008
 (httpd)
 calcru: runtime went backwards from 909 usec to 459 usec for pid 1007
 (httpd)
 calcru: runtime went backwards from 1214 usec to 653 usec for pid 1006
 (httpd)
 calcru: runtime went backwards from 201793 usec to 102672 usec for pid
 996 (httpd)
 calcru: runtime went backwards from 1105 usec to 1064 usec for pid 991
 (sshd)
 calcru: runtime went backwards from 45196 usec to 23221 usec for pid
 974 (zabbix_server)
 calcru: runtime went backwards from 2192 usec to 1436 usec for pid 973
 (zabbix_server)
 calcru: runtime went backwards from 605 usec to 306 usec for pid 968
 (zabbix_server)
 calcru: runtime went backwards from 626 usec to 316 usec for pid 967
 (zabbix_server)
 calcru: runtime went backwards from 773 usec to 391 usec for pid 966
 (zabbix_server)
 calcru: runtime went backwards from 663 usec to 335 usec for pid 965
 (zabbix_server)
 calcru: runtime went backwards from 799 usec to 404 usec for pid 964
 (zabbix_server)
 calcru: runtime went backwards from 37723 usec to 19422 usec for pid
 963 (zabbix_server)
 calcru: runtime went backwards from 49425 usec to 26265 usec for pid
 962 (zabbix_server)
 calcru: runtime went backwards from 38883 usec to 20993 usec for pid
 961 (zabbix_server)
 

Re: Hyper-V

[Julian Elischer]

On 11/4/13, 11:13 PM, Pavel Timofeev wrote:

Hi! I upgraded to 10.0-BETA3 but still see messages like

Tue Nov  5 11:09:05 MSK 2013
calcru: runtime went backwards from 1728 usec to 889 usec for pid 981
(zabbix_server)
calcru: runtime went backwards from 1229 usec to 703 usec for pid 976
(zabbix_server)
calcru: runtime went backwards from 1019 usec to 595 usec for pid 978
(zabbix_server)
calcru: runtime went backwards from 3041 usec to 1611 usec for pid 969
(zabbix_server)
calcru: runtime went backwards from 1078 usec to 595 usec for pid 975
(zabbix_server)
calcru: runtime went backwards from 1114 usec to 617 usec for pid 980
(zabbix_server)
calcru: runtime went backwards from 1086 usec to 602 usec for pid 977
(zabbix_server)
calcru: runtime went backwards from 1195 usec to 782 usec for pid 970
(zabbix_server)
calcru: runtime went backwards from 3206 usec to 2157 usec for pid 979
(zabbix_server)
calcru: runtime went backwards from 2179 usec to 1542 usec for pid 972
(zabbix_server)
calcru: runtime went backwards from 1833 usec to 927 usec for pid 1026 (cron)
calcru: runtime went backwards from 1091 usec to 551 usec for pid 1022
(sendmail)
calcru: runtime went backwards from 823 usec to 416 usec for pid 1022 (sendmail)
calcru: runtime went backwards from 4691 usec to 2735 usec for pid
1011 (sendmail)
calcru: runtime went backwards from 1162 usec to 587 usec for pid 1011
(sendmail)
calcru: runtime went backwards from 947 usec to 478 usec for pid 1010 (httpd)
calcru: runtime went backwards from 895 usec to 452 usec for pid 1009 (httpd)
calcru: runtime went backwards from 954 usec to 482 usec for pid 1008 (httpd)
calcru: runtime went backwards from 909 usec to 459 usec for pid 1007 (httpd)
calcru: runtime went backwards from 1214 usec to 653 usec for pid 1006 (httpd)
calcru: runtime went backwards from 201793 usec to 102672 usec for pid
996 (httpd)
calcru: runtime went backwards from 1105 usec to 1064 usec for pid 991 (sshd)
calcru: runtime went backwards from 45196 usec to 23221 usec for pid
974 (zabbix_server)
calcru: runtime went backwards from 2192 usec to 1436 usec for pid 973
(zabbix_server)
calcru: runtime went backwards from 605 usec to 306 usec for pid 968
(zabbix_server)
calcru: runtime went backwards from 626 usec to 316 usec for pid 967
(zabbix_server)
calcru: runtime went backwards from 773 usec to 391 usec for pid 966
(zabbix_server)
calcru: runtime went backwards from 663 usec to 335 usec for pid 965
(zabbix_server)
calcru: runtime went backwards from 799 usec to 404 usec for pid 964
(zabbix_server)
calcru: runtime went backwards from 37723 usec to 19422 usec for pid
963 (zabbix_server)
calcru: runtime went backwards from 49425 usec to 26265 usec for pid
962 (zabbix_server)
calcru: runtime went backwards from 38883 usec to 20993 usec for pid
961 (zabbix_server)
calcru: runtime went backwards from 53478 usec to 27411 usec for pid
960 (zabbix_server)
calcru: runtime went backwards from 40845 usec to 21750 usec for pid
959 (zabbix_server)
calcru: runtime went backwards from 47835 usec to 24455 usec for pid
958 (zabbix_server)
calcru: runtime went backwards from 2257 usec to 1612 usec for pid 957
(zabbix_server)
calcru: runtime went backwards from 2361 usec to 1193 usec for pid 932
(zabbix_agentd)
calcru: runtime went backwards from 32053 usec to 16204 usec for pid
928 (zabbix_server)
calcru: runtime went backwards from 32517 usec to 19280 usec for pid 697 (sh)
calcru: runtime went backwards from 1128021 usec to 868022 usec for pid 697 (sh)
calcru: runtime went backwards from 9609 usec to 5601 usec for pid 601 (syslogd)
calcru: runtime went backwards from 688 usec to 348 usec for pid 106 (adjkerntz)
calcru: runtime went backwards from 12 usec to 6 usec for pid 3 (sctp_iterator)
calcru: runtime went backwards from 5467 usec to 2853 usec for pid 2 (fdc0)
calcru: runtime went backwards from 11306 usec to 8408 usec for pid 14
(rand_harvestq)
calcru: runtime went backwards from 136242 usec to 76230 usec for pid 13 (geom)
calcru: runtime went backwards from 156117 usec to 118882 usec for pid 12 (intr)
calcru: runtime went backwards from 7820 usec to 4847 usec for pid 1 (init)
calcru: runtime went backwards from 2340313 usec to 1226503 usec for
pid 1 (init)
calcru: runtime went backwards from 4114 usec to 2164 usec for pid 0 (kernel)


Is it bad? Or I have to ignore them?


I'm not talking authoratatively but in some virtualization systems, if 
the TSCs on the various processors are not sufficiently synchronized, 
then when the hypervisor switches you from one CPU to another, you can 
get odd (sometimes negative) time readings which give messages like this..



___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org




___
freebsd-virtualization@freebsd.org mailing list

Re: Hyper-V

[Pavel Timofeev]

Thank you very much!
I started to dig, and found that I can reboot my server running under
Hyper-V by doing 'sysctl -a'.
Can anybody confirm same behavoiur?

FreeBSD 10.0-BETA3, Win 2012 Datacenter

2013/11/5 Julian Elischer jul...@freebsd.org:
 On 11/4/13, 11:13 PM, Pavel Timofeev wrote:

 Hi! I upgraded to 10.0-BETA3 but still see messages like

 Tue Nov  5 11:09:05 MSK 2013
 calcru: runtime went backwards from 1728 usec to 889 usec for pid 981
 (zabbix_server)
 calcru: runtime went backwards from 1229 usec to 703 usec for pid 976
 (zabbix_server)
 calcru: runtime went backwards from 1019 usec to 595 usec for pid 978
 (zabbix_server)
 calcru: runtime went backwards from 3041 usec to 1611 usec for pid 969
 (zabbix_server)
 calcru: runtime went backwards from 1078 usec to 595 usec for pid 975
 (zabbix_server)
 calcru: runtime went backwards from 1114 usec to 617 usec for pid 980
 (zabbix_server)
 calcru: runtime went backwards from 1086 usec to 602 usec for pid 977
 (zabbix_server)
 calcru: runtime went backwards from 1195 usec to 782 usec for pid 970
 (zabbix_server)
 calcru: runtime went backwards from 3206 usec to 2157 usec for pid 979
 (zabbix_server)
 calcru: runtime went backwards from 2179 usec to 1542 usec for pid 972
 (zabbix_server)
 calcru: runtime went backwards from 1833 usec to 927 usec for pid 1026
 (cron)
 calcru: runtime went backwards from 1091 usec to 551 usec for pid 1022
 (sendmail)
 calcru: runtime went backwards from 823 usec to 416 usec for pid 1022
 (sendmail)
 calcru: runtime went backwards from 4691 usec to 2735 usec for pid
 1011 (sendmail)
 calcru: runtime went backwards from 1162 usec to 587 usec for pid 1011
 (sendmail)
 calcru: runtime went backwards from 947 usec to 478 usec for pid 1010
 (httpd)
 calcru: runtime went backwards from 895 usec to 452 usec for pid 1009
 (httpd)
 calcru: runtime went backwards from 954 usec to 482 usec for pid 1008
 (httpd)
 calcru: runtime went backwards from 909 usec to 459 usec for pid 1007
 (httpd)
 calcru: runtime went backwards from 1214 usec to 653 usec for pid 1006
 (httpd)
 calcru: runtime went backwards from 201793 usec to 102672 usec for pid
 996 (httpd)
 calcru: runtime went backwards from 1105 usec to 1064 usec for pid 991
 (sshd)
 calcru: runtime went backwards from 45196 usec to 23221 usec for pid
 974 (zabbix_server)
 calcru: runtime went backwards from 2192 usec to 1436 usec for pid 973
 (zabbix_server)
 calcru: runtime went backwards from 605 usec to 306 usec for pid 968
 (zabbix_server)
 calcru: runtime went backwards from 626 usec to 316 usec for pid 967
 (zabbix_server)
 calcru: runtime went backwards from 773 usec to 391 usec for pid 966
 (zabbix_server)
 calcru: runtime went backwards from 663 usec to 335 usec for pid 965
 (zabbix_server)
 calcru: runtime went backwards from 799 usec to 404 usec for pid 964
 (zabbix_server)
 calcru: runtime went backwards from 37723 usec to 19422 usec for pid
 963 (zabbix_server)
 calcru: runtime went backwards from 49425 usec to 26265 usec for pid
 962 (zabbix_server)
 calcru: runtime went backwards from 38883 usec to 20993 usec for pid
 961 (zabbix_server)
 calcru: runtime went backwards from 53478 usec to 27411 usec for pid
 960 (zabbix_server)
 calcru: runtime went backwards from 40845 usec to 21750 usec for pid
 959 (zabbix_server)
 calcru: runtime went backwards from 47835 usec to 24455 usec for pid
 958 (zabbix_server)
 calcru: runtime went backwards from 2257 usec to 1612 usec for pid 957
 (zabbix_server)
 calcru: runtime went backwards from 2361 usec to 1193 usec for pid 932
 (zabbix_agentd)
 calcru: runtime went backwards from 32053 usec to 16204 usec for pid
 928 (zabbix_server)
 calcru: runtime went backwards from 32517 usec to 19280 usec for pid 697
 (sh)
 calcru: runtime went backwards from 1128021 usec to 868022 usec for pid
 697 (sh)
 calcru: runtime went backwards from 9609 usec to 5601 usec for pid 601
 (syslogd)
 calcru: runtime went backwards from 688 usec to 348 usec for pid 106
 (adjkerntz)
 calcru: runtime went backwards from 12 usec to 6 usec for pid 3
 (sctp_iterator)
 calcru: runtime went backwards from 5467 usec to 2853 usec for pid 2
 (fdc0)
 calcru: runtime went backwards from 11306 usec to 8408 usec for pid 14
 (rand_harvestq)
 calcru: runtime went backwards from 136242 usec to 76230 usec for pid 13
 (geom)
 calcru: runtime went backwards from 156117 usec to 118882 usec for pid 12
 (intr)
 calcru: runtime went backwards from 7820 usec to 4847 usec for pid 1
 (init)
 calcru: runtime went backwards from 2340313 usec to 1226503 usec for
 pid 1 (init)
 calcru: runtime went backwards from 4114 usec to 2164 usec for pid 0
 (kernel)


 Is it bad? Or I have to ignore them?


 I'm not talking authoratatively but in some virtualization systems, if the
 TSCs on the various processors are not sufficiently synchronized, then when
 the hypervisor switches you from one CPU to another, you can get odd
 (sometimes negative) time readings which give messages like this..

 

Re: [Hyper-V][camlock] storvsc driver panics during boot with patches from camlock project

[Alexander Motin]

Hi.

I took some look and think problems are in scan_for_luns() routine:
 - After the locking changes scanning normally uses different locks, 
not the SIM one. That probably caused panic.
 - But I think that scanning is simply not needed there -- FreeBSD CAM 
scans every new bus automatically on registration (Even for late 
registered buses it is done I think at least since FreeBSD 8). I think 
everything should just work if you remove scan_for_luns() at all.
 - If you still wish to force scan (due to having information about 
changed list of devices, etc), then you can make CAM do all the magic 
for you by calling xpt_rescan().


On 24.10.2013 08:34, Oleg Sidorkin wrote:

Hello again.

Camlock patches are now committed and -CURRENT on Hyper-V now panics
with almost the same stacktrace:

FreeBSD 11.0-CURRENT #16 r257016: Wed Oct 23 21:08:44 UTC 2013
 olsi@current:/usr/obj/usr/src/sys/HYPERVKERNEL amd64
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
CPU: Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz (1309.57-MHz K8-class CPU)
   Origin = GenuineIntel  Id = 0x206a7  Family = 0x6  Model = 0x2a
Stepping = 7

..

ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 10.000 msec
storvsc0 on vmbus0
kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x20
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x804f58cc
stack pointer   = 0x28:0xfe011dd5f5d0
frame pointer   = 0x28:0xfe011dd5f600
code segment= base 0x0, limit 0xf, type 0x1b
 = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= resume, IOPL = 0
current process = 0 (hv_control_1 taskq)
[ thread pid 0 tid 100047 ]
Stopped at  turnstile_broadcast+0x8c:   movq0x20(%rbx,%rax,1),%rdx
db bt
Tracing pid 0 tid 100047 td 0xf8000331e000
turnstile_broadcast() at turnstile_broadcast+0x8c/frame 0xfe011dd5f600
__mtx_unlock_sleep() at __mtx_unlock_sleep+0x60/frame 0xfe011dd5f630
unlock_mtx() at unlock_mtx+0x2a/frame 0xfe011dd5f640
_sleep() at _sleep+0x18e/frame 0xfe011dd5f6c0
cam_periph_runccb() at cam_periph_runccb+0x9e/frame 0xfe011dd5f7f0
storvsc_attach() at storvsc_attach+0x6d4/frame 0xfe011dd5f890
device_attach() at device_attach+0x3a2/frame 0xfe011dd5f8f0
hv_vmbus_child_device_register() at
hv_vmbus_child_device_register+0xdb/frame 0xfe011dd5f990
vmbus_channel_process_offer() at
vmbus_channel_process_offer+0x133/frame 0xfe011dd5f9d0
work_item_callback() at work_item_callback+0x26/frame 0xfe011dd5f9f0
taskqueue_run_locked() at taskqueue_run_locked+0xe6/frame 0xfe011dd5fa40
taskqueue_thread_loop() at taskqueue_thread_loop+0xa8/frame 0xfe011dd5fa70
fork_exit() at fork_exit+0x9a/frame 0xfe011dd5fab0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe011dd5fab0
--- trap 0, rip = 0, rsp = 0xfe011dd5fb70, rbp = 0 ---


Thanks

On Tue, Sep 24, 2013 at 3:04 AM, Abhishek Gupta (LIS)
abgu...@microsoft.com wrote:

Hi Oleg,

Please give us some time. I shall look at it. Thanks for reporting.

Regards,
Abhishek

-Original Message-
From: owner-freebsd-virtualizat...@freebsd.org 
[mailto:owner-freebsd-virtualizat...@freebsd.org] On Behalf Of Oleg Sidorkin
Sent: Monday, September 23, 2013 7:21 AM
To: freebsd-virtualization@freebsd.org
Cc: Alexander Motin
Subject: [Hyper-V][camlock] storvsc driver panics during boot with patches from 
camlock project

Hello.

I'm running the latest current (amd64) under Hyper-V with hyper-v services 
enabled.
If camlock patches are applied
(http://people.freebsd.org/~mav/camlock_patches/camlock_20130906.patch),
I'm hitting the following  kernel panic during boot:

FreeBSD 10.0-ALPHA2 #5 r255762M: Sun Sep 22 16:48:21 UTC 2013
 olsi@current:/usr/obj/usr/src/sys/HYPERVKERNEL amd64 FreeBSD clang version 
3.3 (tags/RELEASE_33/final 183502) 20130610
CPU: Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz (1309.17-MHz K8-class CPU)
   Origin = GenuineIntel  Id = 0x206a7  Family = 0x6  Model = 0x2a Stepping =
 7

Timecounter Hyper-V frequency 1000 Hz quality 1000 ZFS NOTICE: 
Prefetch is disabled by default if less than 4GB of RAM is present;
 to enable, add vfs.zfs.prefetch_disable=0 to /boot/loader.conf.
ZFS filesystem version: 5
ZFS storage pool version: features support (5000) Timecounters tick every 
10.000 msec
storvsc0 on vmbus0
Netvsc initializing... SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03
fault virtual address   = 0x20
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x804f444c
stack pointer   = 0x28:0xfe011df38610

RE: [Hyper-V][camlock] storvsc driver panics during boot with patches from camlock project

[Abhishek Gupta (LIS)]

Hi Oleg,

Please give us some time. I shall look at it. Thanks for reporting.

Regards,
Abhishek

-Original Message-
From: owner-freebsd-virtualizat...@freebsd.org 
[mailto:owner-freebsd-virtualizat...@freebsd.org] On Behalf Of Oleg Sidorkin
Sent: Monday, September 23, 2013 7:21 AM
To: freebsd-virtualization@freebsd.org
Cc: Alexander Motin
Subject: [Hyper-V][camlock] storvsc driver panics during boot with patches from 
camlock project

Hello.

I'm running the latest current (amd64) under Hyper-V with hyper-v services 
enabled.
If camlock patches are applied
(http://people.freebsd.org/~mav/camlock_patches/camlock_20130906.patch),
I'm hitting the following  kernel panic during boot:

FreeBSD 10.0-ALPHA2 #5 r255762M: Sun Sep 22 16:48:21 UTC 2013
olsi@current:/usr/obj/usr/src/sys/HYPERVKERNEL amd64 FreeBSD clang version 
3.3 (tags/RELEASE_33/final 183502) 20130610
CPU: Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz (1309.17-MHz K8-class CPU)
  Origin = GenuineIntel  Id = 0x206a7  Family = 0x6  Model = 0x2a Stepping =
7

Timecounter Hyper-V frequency 1000 Hz quality 1000 ZFS NOTICE: 
Prefetch is disabled by default if less than 4GB of RAM is present;
to enable, add vfs.zfs.prefetch_disable=0 to /boot/loader.conf.
ZFS filesystem version: 5
ZFS storage pool version: features support (5000) Timecounters tick every 
10.000 msec
storvsc0 on vmbus0
Netvsc initializing... SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03
fault virtual address   = 0x20
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x804f444c
stack pointer   = 0x28:0xfe011df38610
frame pointer   = 0x28:0xfe011df38640
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= resume, IOPL = 0
current process = 0 (hv_control_1 taskq)
[ thread pid 0 tid 100046 ]
Stopped at  turnstile_broadcast+0x8c:   movq0x20(%rbx,%rax,1),%rdx
db bt
Tracing pid 0 tid 100046 td 0xf80001f20490
turnstile_broadcast() at turnstile_broadcast+0x8c/frame 0xfe011df38640
__mtx_unlock_sleep() at __mtx_unlock_sleep+0x60/frame 0xfe011df38670
unlock_mtx() at unlock_mtx+0x2a/frame 0xfe011df38680
_sleep() at _sleep+0x18e/frame 0xfe011df38700
cam_periph_runccb() at cam_periph_runccb+0x9e/frame 0xfe011df38800
storvsc_attach() at storvsc_attach+0x6d4/frame 0xfe011df388a0
device_attach() at device_attach+0x396/frame 0xfe011df388f0
hv_vmbus_child_device_register() at
hv_vmbus_child_device_register+0xdb/frame 0xfe011df38990
vmbus_channel_process_offer() at
vmbus_channel_process_offer+0x133/frame 0xfe011df389d0
work_item_callback() at work_item_callback+0x26/frame 0xfe011df389f0
taskqueue_run_locked() at taskqueue_run_locked+0xe6/frame 0xfe011df38a40
taskqueue_thread_loop() at taskqueue_thread_loop+0xa8/frame 0xfe011df38a70
fork_exit() at fork_exit+0x9a/frame 0xfe011df38ab0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe011df38ab0
--- trap 0, rip = 0, rsp = 0xfe011df38b70, rbp = 0 ---
db


This patch is not commited yet (CFT thread with changes description is
here: 
http://lists.freebsd.org/pipermail/freebsd-hackers/2013-September/04.html),
but it is going to be commited till the end of the year.

As far as I understand, the invocation chain is 
storvsc_attach-scan_for_luns-cam_periph_runccb

Thanks
--
Oleg Sidorkin
___
freebsd-virtualization@freebsd.org mailing list 
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

RE: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?

[Abhishek Gupta (LIS)]

Hi Karl,

Thanks for reporting the issue. Please give us some time to investigate and get 
back to you on this. In the meantime I wanted to ask if setting up a Hyper-V 
replica for the FreeBSD VM and then a manual failover reproduces the same 
symptoms? Please let me know.

Thanks,
Abhishek

From: owner-freebsd-virtualizat...@freebsd.org 
owner-freebsd-virtualizat...@freebsd.org on behalf of Karl Pielorz 
kpielorz_...@tdx.co.uk
Sent: Wednesday, September 18, 2013 5:42 AM
To: freebsd-virtualization@freebsd.org
Subject: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?

Hi,

As you've probably seen from my previous posts, we're looking at using
Hyper-V with FreeBSD.

We built a test system (2 node cluster) - and had 2 HA hosts running on it
(a Windows 7 install, and a FreeBSD install from base/projects/hyperv
r255634).

Live migration works for both hosts (i.e. to the other cluster node, and
back) - but a failure of the node [power pulled / non-graceful shutdown]
running the VM's - seems to trash the FreeBSD system.

Hyper-V correctly see's the node fail, and restarts both VM's on the
remaining node. Windows 7 boots fine (says it wasn't shut down correctly -
which is correct) - but FreeBSD doesn't survive.

At boot time we get a blank screen with - on it (i.e. the first part of
the boot 'spinner') - and nothing else.

Booting to a network copy of FreeBSD and looking at the underlying virtual
disk - it appears to be trashed. You can mount it (but it understandably
warns it's not clean) - however, any access leads to an instant panic ('bad
dir ino 2 at offset 0: mangled entry').

Trying to run fsck against the file system throws up an impressive amounts
of 'bad magic' errors and 'rebuild cylinder group?' prompts.

Should the current FreeBSD Hyper-V drivers support this? (like I said, live
migration worked without an issue - and Windows recovered fine from the
failure).

The Hyper-V is running under WS2012, with a Synology SAN - if you need any
more info, let me know,

Thanks,

-Karl
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

RE: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?

[Abhishek Gupta (LIS)]

Thanks again Karl! Yes, it should work. My understanding is that the failover 
should be agnostic to the guest OS but there could be some integration 
component that we might have missed. So it would be good to get to the bottom 
of this.

Regards,

Abhishek

From: Karl Pielorz kpielorz_...@tdx.co.uk
Sent: Wednesday, September 18, 2013 7:45 AM
To: Abhishek Gupta (LIS); freebsd-virtualization@freebsd.org
Subject: RE: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?

--On 18 September 2013 14:23 + Abhishek Gupta (LIS)
abgu...@microsoft.com wrote:

 Hi Karl,

 Thanks for reporting the issue. Please give us some time to investigate
 and get back to you on this. In the meantime I wanted to ask if setting
 up a Hyper-V replica for the FreeBSD VM and then a manual failover
 reproduces the same symptoms? Please let me know.

Hi,

Manual fail-over appears to work OK - in order, I tested:

 - Live migration from one node to the other, and back again (worked)

 - Stopping the cluster service on one of the nodes (i.e. from Failover
Cluster Manager) - this showed the VM moving from the node that was
stopped, over to the other node (again worked).

 - Pulling the power on the active node hosting both VM's (i.e. Windows
guest, and FreeBSD guest) - this showed the remaining node trying to bring
up the VM's (of which Windows came up OK, and FreeBSD got corrupted).


I've had to stop now as the guy here looking after the Synology kit on the
test network is applying a firmware update (this is apparently for some
appletalk issue or something).

I'll re-run the test after this has been done - if it still fails, I'll
come back with a 'how to reproduce' type report (and I'll obviously let you
know if we can't reproduce it again!).

At least I know it 'should' work now :)

Thanks,

-Karl

___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

turn off 220V on UPS device =} file system got corrupted Re: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?

[Victor Miasnikov]

Hi!

K.P. - Pulling the power on the active node hosting both VM's (i.e. Windows
K.P. guest, and FreeBSD guest) - this showed the remaining node trying to bring
K.P. up the VM's (of which Windows came up OK, and FreeBSD [file system]  got 
corrupted).


A.G. Yes, it should work.
A.G.My understanding is that the failover should be agnostic to the guest OS but there could be some integration 
component that we might have missed.



What _exactly_ should work ?


1)  This issue not related Hyper-V cluster itself
!)  When Pulling the power i.e. turn off 220V in Europa ( or 110V in USA ) on UPS device _both_  FAT on Windows and 
FreeBSD [file system]  got corrupted


(  Windows came up OK  look like because on this VM file system is NTFS )


K.P. Hyper-V correctly see's the node fail, and restarts both VM's on the
K.P. remaining node. Windows 7 boots fine (says it wasn't shut down correctly -
K.P. which is correct) - but FreeBSD doesn't survive.
K.P.
K.P. At boot time we get a blank screen with - on it (i.e. the first part of
K.P. the boot 'spinner') - and nothing else.
K.P.
K.P. Booting to a network copy of FreeBSD and looking at the underlying virtual
K.P. disk - it appears to be trashed. You can mount it (but it understandably
K.P. warns it's not clean) - however, any access leads to an instant panic 
('bad
K.P. dir ino 2 at offset 0: mangled entry').
K.P.
K.P. Trying to run fsck against the file system throws up an impressive amounts
K.P. of 'bad magic' errors and 'rebuild cylinder group?' prompts.

To Karl: I ask You about some details . . .
Are You see related e-mail?


Best regards, Victor Miasnikov
Blog:  http://vvm.blog.tut.by/




- Original Message - 
From: Abhishek Gupta (LIS)

To: Karl Pielorz
Sent: Wednesday, September 18, 2013 5:50 PM
Subject: RE: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?



Thanks again Karl! Yes, it should work.
My understanding is that the failover should be agnostic to the guest OS but there could be some integration component 
that we might have missed.

So it would be good to get to the bottom of this.

Regards,

Abhishek




From: Karl Pielorz
Sent: Wednesday, September 18, 2013 7:45 AM
To: Abhishek Gupta (LIS);
Subject: RE: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?

--On 18 September 2013 14:23 + Abhishek Gupta (LIS)
wrote:


Hi Karl,

Thanks for reporting the issue. Please give us some time to investigate
and get back to you on this. In the meantime I wanted to ask if setting
up a Hyper-V replica for the FreeBSD VM and then a manual failover
reproduces the same symptoms? Please let me know.


Hi,

Manual fail-over appears to work OK - in order, I tested:

- Live migration from one node to the other, and back again (worked)

- Stopping the cluster service on one of the nodes (i.e. from Failover
Cluster Manager) - this showed the VM moving from the node that was
stopped, over to the other node (again worked).

- Pulling the power on the active node hosting both VM's (i.e. Windows
guest, and FreeBSD guest) - this showed the remaining node trying to bring
up the VM's (of which Windows came up OK, and FreeBSD got corrupted).


I've had to stop now as the guy here looking after the Synology kit on the
test network is applying a firmware update (this is apparently for some
appletalk issue or something).

I'll re-run the test after this has been done - if it still fails, I'll
come back with a 'how to reproduce' type report (and I'll obviously let you
know if we can't reproduce it again!).

At least I know it 'should' work now :)

Thanks,

-Karl


___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

RE: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?

[Abhishek Gupta (LIS)]

Great! Thanks for verifying!
Abhishek

From: Karl Pielorz kpielorz_...@tdx.co.uk
Sent: Wednesday, September 18, 2013 8:56 AM
To: Abhishek Gupta (LIS); freebsd-virtualization@freebsd.org
Subject: RE: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?

--On 18 September 2013 14:50 + Abhishek Gupta (LIS)
abgu...@microsoft.com wrote:

 Thanks again Karl! Yes, it should work. My understanding is that the
 failover should be agnostic to the guest OS but there could be some
 integration component that we might have missed. So it would be good to
 get to the bottom of this.

Ok, I've repeated the test twice now - and it's succeeded both times, so it
looks likely the Synology patch did 'something' that had a knock on effect
for this.

fwiw/incase anyone else hit this - our test setup comprises of a pair of
D412+ NAS's (active/passive) and they're now running DSM v4.3-3776-1 (which
was apparently released in the last few days) - so far (fingers crossed)
this appears to be working for us now.

I'll be re-testing it probably multiple times over the next few days - if I
hit any other issues - I'll let you know, and thanks again,

Regards,

-Karl
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

RE: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?

[Karl Pielorz]

--On 18 September 2013 14:50 + Abhishek Gupta (LIS) 
abgu...@microsoft.com wrote:



Thanks again Karl! Yes, it should work. My understanding is that the
failover should be agnostic to the guest OS but there could be some
integration component that we might have missed. So it would be good to
get to the bottom of this.


Ok, I've repeated the test twice now - and it's succeeded both times, so it 
looks likely the Synology patch did 'something' that had a knock on effect 
for this.


fwiw/incase anyone else hit this - our test setup comprises of a pair of 
D412+ NAS's (active/passive) and they're now running DSM v4.3-3776-1 (which 
was apparently released in the last few days) - so far (fingers crossed) 
this appears to be working for us now.


I'll be re-testing it probably multiple times over the next few days - if I 
hit any other issues - I'll let you know, and thanks again,


Regards,

-Karl
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Hyper-V driver development status

[Karl Pielorz]

--On 11 September 2013 16:43 +0400 Pavel Timofeev tim...@gmail.com wrote:


I've just checked out and built projects/hyperv and everything looks good.


I just did that as well this morning...

FreeBSD  10.0-CURRENT FreeBSD 10.0-CURRENT #6 r255470: Wed Sep 11 10:29:25 
UTC 2013   root@:/usr/obj/src/sys/GENERIC  amd64


I'm running under Windows Hyper V Server 2012 - the only things I've 
noticed so far (not been testing long):


- I get a myriad of caclru: runtime went backwards from xxx usec to yyy 
usec for pid  on the console every now and again.


- On the Hyper-V Manager, under Networking it says:

Status: Degraded (Integration services upgrade required)

  [I have just the 'Network Adapter' present in the VM - not the Legacy 
Adapter].


Heartbeat shows as 'OK (No Application Data)' - which I'm guessing is 
probably cosmetic?


-Karl

___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

RE: Hyper-V driver development status

[Abhishek Gupta (LIS)]

Hi guys,

Thanks for the feedback.

I have seen the caclru: runtime went backwards from xxx usec to yyy usec for 
pid  off an on but I have not seen any visible system impact because of 
that. It could be because the clock is virtualized and the system is taking 
some time to adjust to it. We can file this as a bug in our database and work 
on resolving it.

The Status: Degraded (Integration services upgrade required) issue is benign.

The Heartbeat shows as 'OK (No Application Data) is benign too.

Let us know if you guys are seeing some other issues.
Thanks,
Abhishek

From: Karl Pielorz kpielorz_...@tdx.co.uk
Sent: Wednesday, September 11, 2013 6:15 AM
To: Pavel Timofeev; Abhishek Gupta (LIS)
Cc: freebsd-virtualization@freebsd.org
Subject: Re: Hyper-V driver development status

--On 11 September 2013 16:43 +0400 Pavel Timofeev tim...@gmail.com wrote:

 I've just checked out and built projects/hyperv and everything looks good.

I just did that as well this morning...

FreeBSD  10.0-CURRENT FreeBSD 10.0-CURRENT #6 r255470: Wed Sep 11 10:29:25
UTC 2013   root@:/usr/obj/src/sys/GENERIC  amd64

I'm running under Windows Hyper V Server 2012 - the only things I've
noticed so far (not been testing long):

 - I get a myriad of caclru: runtime went backwards from xxx usec to yyy
usec for pid  on the console every now and again.

 - On the Hyper-V Manager, under Networking it says:

 Status: Degraded (Integration services upgrade required)

   [I have just the 'Network Adapter' present in the VM - not the Legacy
Adapter].

Heartbeat shows as 'OK (No Application Data)' - which I'm guessing is
probably cosmetic?

-Karl

___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: Hyper-V driver development status

[Pavel Timofeev]

So, is it going to be included in FreeBSD 10 now? As I can see code
freeze for CURRENT is planned on 7 September 2013 (10 days from now).
http://www.freebsd.org/releases/10.0R/schedule.html
It's not much time.

2013/8/17 Abhishek Gupta (LIS) abgu...@microsoft.com:
 Hi Pavel,

 Thanks for inquiring about the BSD drivers for Hyper-V. We (Microsoft) are 
 actively working on these drivers and the intent is to get them integrated in 
 to the kernel within the next month or so. There are some issues we are 
 trying to address:

 a) Witness panic during boot time due to a specific memory allocation.
 b) Bypass usage of disk labels to ensure that devices do not get reordered 
 under FreeBSD.
 c) Locks up on 32 bit builds.
 d) Lack of KVP support for BSD drivers

 We are working hard every day to finish these items.

 Even though an official announcement has not gone out, I would highly 
 encourage you to start testing the drivers. As they are in project branch now 
 they should be easy to compile. The only requirement is to set up disk labels 
 before rebooting a kernel that includes the Hyper-V drivers otherwise the 
 system will not boot up.

 Please let me know if you have more questions or have feedback.

 Thanks again for your interest.
 Abhishek
 
 From: Peter Grehan gre...@freebsd.org
 Sent: Friday, August 16, 2013 11:30 AM
 To: Abhishek Gupta (LIS)
 Subject: Fwd: Hyper-V driver development status

 Want to reply to this ?


  Original Message 
 Subject: Hyper-V driver development status
 Date: Fri, 16 Aug 2013 17:00:57 +0400
 From: Pavel Timofeev tim...@gmail.com
 To: freebsd-virtualization@freebsd.org

 Hi all!
 I'd like to know what's happening with hyper-v driver development in
 FreeBSD.
 I know about svn branch but there is no active progress in there.
 What's the roadmap? Or we are waiting for something?

 What is the current status of that project?
 I could do some tests. Or it's too early?
 I'm looking forward to use it =)
 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to
 freebsd-virtualization-unsubscr...@freebsd.org



___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

RE: Hyper-V driver development status

[Abhishek Gupta (LIS)]

Hi Pavel,

Yes, FreeBSD 10 is still the target. We are working to make it in to the tree. 
You should see some traction next week.

Thanks,
Abhishek

From: Pavel Timofeev tim...@gmail.com
Sent: Thursday, August 29, 2013 3:31 AM
To: Abhishek Gupta (LIS)
Cc: Peter Grehan; freebsd-virtualization@freebsd.org
Subject: Re: Hyper-V driver development status

So, is it going to be included in FreeBSD 10 now? As I can see code
freeze for CURRENT is planned on 7 September 2013 (10 days from now).
http://www.freebsd.org/releases/10.0R/schedule.html
It's not much time.

2013/8/17 Abhishek Gupta (LIS) abgu...@microsoft.com:
 Hi Pavel,

 Thanks for inquiring about the BSD drivers for Hyper-V. We (Microsoft) are 
 actively working on these drivers and the intent is to get them integrated in 
 to the kernel within the next month or so. There are some issues we are 
 trying to address:

 a) Witness panic during boot time due to a specific memory allocation.
 b) Bypass usage of disk labels to ensure that devices do not get reordered 
 under FreeBSD.
 c) Locks up on 32 bit builds.
 d) Lack of KVP support for BSD drivers

 We are working hard every day to finish these items.

 Even though an official announcement has not gone out, I would highly 
 encourage you to start testing the drivers. As they are in project branch now 
 they should be easy to compile. The only requirement is to set up disk labels 
 before rebooting a kernel that includes the Hyper-V drivers otherwise the 
 system will not boot up.

 Please let me know if you have more questions or have feedback.

 Thanks again for your interest.
 Abhishek
 
 From: Peter Grehan gre...@freebsd.org
 Sent: Friday, August 16, 2013 11:30 AM
 To: Abhishek Gupta (LIS)
 Subject: Fwd: Hyper-V driver development status

 Want to reply to this ?


  Original Message 
 Subject: Hyper-V driver development status
 Date: Fri, 16 Aug 2013 17:00:57 +0400
 From: Pavel Timofeev tim...@gmail.com
 To: freebsd-virtualization@freebsd.org

 Hi all!
 I'd like to know what's happening with hyper-v driver development in
 FreeBSD.
 I know about svn branch but there is no active progress in there.
 What's the roadmap? Or we are waiting for something?

 What is the current status of that project?
 I could do some tests. Or it's too early?
 I'm looking forward to use it =)
 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to
 freebsd-virtualization-unsubscr...@freebsd.org



___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Tmp. disable BlkVSC (paravirtual IDE) functional? Re: ATA controller and Hyper-V synthetic storage driver handle the IDE disks devices ( but not for the CD-ROM) Re: Hyper-V on FreeBSD

[Victor Miasnikov]

Hi!

Short:

{{
L.M. Removing our ATA patches, on the other hand, results in a huge
L.M. performance loss. This is because the root file system is managed by the
L.M. ATA driver, which is emulated under Hyper-V.
VVM Place on IDE disk only \boot ( and bootloader), other on SCSI .
+
VVM Disable both primary and secondary ATA controller prevent use CD-ROM 
device in VM ( guest)
VVM Because synthetic storage driver not handle CD-ROM devices

 May be temporary disable BlkVSC (paravirtual IDE) functional?

And enable [imm.]after implement work on Hyper-V both CD-ROM and ATA disks



==

--- 000\hv_storvsc_drv_freebsd.c Wed Apr 10 06:18:58 2013
+++ hv_storvsc_drv_freebsd.c Wed May 08 11:59:06 2013

. . .

 * Using the type GUID, determine if this is a StorVSC (paravirtual
 * SCSI or BlkVSC (paravirtual IDE) device.

. . .

 if (!memcmp(p, gBlkVscDeviceType, sizeof(hv_guid))) {
-   return DRIVER_BLKVSC;
+  /* TODO: enable after implement work on Hyper-V both CD-ROM and ATA disks
+   * return DRIVER_BLKVSC;  
+   */
+   return (DRIVER_UNKNOWN);  


. . .

==

}}




Full:


On Tue, May 7, 2013 at 12:40 AM, Victor Miasnikov vvm (at) tut.by wrote:




L.M. ==
L.M. . . .
L.M. On 23.04.2013 17:07, Larry Melia wrote:
L.M. . . .
L.M.
L.M. Removing our ATA patches, on the other hand, results in a huge
L.M. performance loss. This is because the root file system is managed by the
L.M. ATA driver, which is emulated under Hyper-V.
L.M.
L.M. ==

VVM
VVM Place on IDE disk only \boot ( and bootloader), other on SCSI .
VVM



prevent default OS driver from attaching to emulated ATA controller when  
Hyper-V


VVM
VVM Disable both primary and secondary ATA controller prevent use CD-ROM 
device in VM ( guest)
VVM
VVM Because synthetic storage driver not handle CD-ROM devices
VVM ( IMHO, even more: Hyper-V host work with CD-ROM only as PCI bus device)


L.M.Regarding the CD-ROM drive, there's a known problem with CD-ROM support and using our synthetic storage driver. 
L.M.At the moment, it's not supported correctly on FreeBSD, 
L.M.but  . . . there's a workaround  ( details skipped by VVM, {= not all simply , long story )  , 
L.M.which we will try to get working on FreeBSD. 
L.M.This will be addressed shortly, but . . . ( skipped by VVM ) . 



 May be temporary disable BlkVSC (paravirtual IDE) functional?
And enable after implement work on Hyper-V both CD-ROM and ATA disks


==
--- 000\hv_storvsc_drv_freebsd.cWed Apr 10 06:18:58 2013
+++ hv_storvsc_drv_freebsd.cWed May 08 11:59:06 2013
@@ -1449,22 +1449,25 @@
/**
 * @brief Determine type of storage device from GUID
 *
 * Using the type GUID, determine if this is a StorVSC (paravirtual
 * SCSI or BlkVSC (paravirtual IDE) device.
 *
 * @param dev a device
 * returns an enum
 */
static enum hv_storage_type
storvsc_get_storage_type(device_t dev)
{
const char *p = vmbus_get_type(dev);

if (!memcmp(p, gBlkVscDeviceType, sizeof(hv_guid))) {
-return DRIVER_BLKVSC;
+/* TODO: enable after implement work on Hyper-V both CD-ROM and ATA 
disks
+ * return DRIVER_BLKVSC;  
+ */
+return (DRIVER_UNKNOWN);   
} else if (!memcmp(p, gStorVscDeviceType, sizeof(hv_guid))) {

return DRIVER_STORVSC;
}
return (DRIVER_UNKNOWN);
}


==


Best regards, Victor Miasnikov
Blog:  http://vvm.blog.tut.by/


P.S.  Sorry, for code style -- is primary demo of _idea_ 




___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: ATA controller and Hyper-V synthetic storage driver handle the IDE disks devices ( but not for the CD-ROM) Re: Hyper-V on FreeBSD

[Alexander Motin]

On 07.05.2013 10:40, Victor Miasnikov wrote:

prevent default OS driver from attaching to emulated ATA controller
when Hyper-V


Disable both primary and secondary ATA controller prevent use CD-ROM
device in VM ( guest)

Because synthetic storage driver not handle CD-ROM devices
( IMHO, even more: Hyper-V host work with CD-ROM only as PCI bus device)


Then may be possibility of blocking/hiding specific ATA channels or 
devices could be investigated.



http://lists.freebsd.org/pipermail/freebsd-virtualization/2013-April/001180.html

==
. . .
On 23.04.2013 17:07, Larry Melia wrote:
. . .

Removing our ATA patches, on the other hand, results in a huge
performance loss. This is because the root file system is managed by the
ATA driver, which is emulated under Hyper-V.

==

Place on IDE disk only \boot ( and bootloader), other on SCSI .


May be instead of splitting filesystem it could be better to boot from 
SCSI completely and forget about ATA? Or there is no option ROM for 
SCSI boot in Hyper-V?


--
Alexander Motin
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: ATA controller and Hyper-V synthetic storage driver handle the IDE disks devices ( but not for the CD-ROM) Re: Hyper-V on FreeBSD

[Victor Miasnikov]

Hi!



On 07.05.2013 10:40, Victor Miasnikov wrote:

prevent default OS driver from attaching to emulated ATA controller
when Hyper-V


Disable both primary and secondary ATA controller prevent use CD-ROM
device in VM ( guest)

Because synthetic storage driver not handle CD-ROM devices
( IMHO, even more: Hyper-V host work with CD-ROM only as PCI bus device)



A.M. Then may be possibility of blocking/hiding specific ATA channels or
A.M. devices could be investigated.

IMHO, this ( or some like this) must be investigated
In any case, need carefully testing work CD-ROM ( primary for LiveCD and (or) .ISO for setup FreeBSD) in Hyper-V 
enviroment




http://lists.freebsd.org/pipermail/freebsd-virtualization/2013-April/001180.html

==
. . .
On 23.04.2013 17:07, Larry Melia wrote:
. . .

L.M. Removing our ATA patches, on the other hand, results in a huge
L.M. performance loss. This is because the root file system is managed by the
L.M. ATA driver, which is emulated under Hyper-V.

==

VVM
VVM Place on IDE disk only \boot ( and bootloader), other on SCSI .
VVM
A.M.
A.M. May be instead of splitting filesystem it could be better to boot from
A.M. SCSI completely and forget about ATA?
A.M. Or there is no option ROM for SCSI boot in Hyper-V?
A.M.

Yes, boot from SCSI disk in Hyper-V VM ( guest) is impossible


Best regards, Victor Miasnikov
Blog:  http://vvm.blog.tut.by/



___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org