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

2016-01-31 Thread 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 >; Sephe Qiao 
(Wicresoft) >; Kylie 
Liang >; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
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 >; Sephe Qiao 
(Wicresoft) >; Kylie 
Liang >; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
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
  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 >; Sephe Qiao 
(Wicresoft) >; Kylie 
Liang >; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
Subject: RE: Hyper-V

Problem reports for freebsd-virtualization@FreeBSD.org that need special attention

2016-01-31 Thread bugzilla-noreply 
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
In Progress |202321 | [bhyve,patch] More verbose error reporting in bhy 
New |202322 | [bhyve,patch] add option to have bhyve write its  

2 problems total for which you should take action.
___
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

2016-01-31 Thread 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 ; Sephe Qiao (Wicresoft) 
; Kylie Liang ; 
'freebsd-virtualization@freebsd.org' ; BSD 
Integration Components for Hyper-V 
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 >; Sephe Qiao 
(Wicresoft) >; Kylie 
Liang >; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
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 >; Sephe Qiao 
(Wicresoft) >; Kylie 
Liang >; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
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

VirtFS support in bhyve

2016-01-31 Thread jceel 
Hello,

I'm working on virtio-9p (so-called VirtFS) support in bhyve. Project consists 
of two parts: BSD-licensed lib9p library and actual virtio-9p driver. Right now 
it's able to do filesystem passthrough using 9P2000.u protocol to Linux guests.

You can check it out here: https://github.com/jceel/freebsd/tree/virtfs

Syntax:
bhyve side: append `-s ,virtio-9p,sharename=/host/path`
linux side: `mount -t 9p -o trans=virtio -o version=9p2000.u sharename 
/mnt/guest/path`

Using 9p as root filesystem for Linux guests should work too.

Plans:
- Definitely in-kernel 9pfs filesystem support for FreeBSD guests using same 
lib9p library
- 9P2000.L support (adds ACLs, extattrs, file locks, atomic reads/writes and so 
on)
- Filesystem backend using AIO
- Ability to export multiple trees for different "aname" values using one 
virtio-9p device (that's actually a low-hanging fruit)

I'm looking forward to your feedback - keep in mind that's totally 
experimental/incomplete/nonworking code.

Jakub.
___
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

2016-01-31 Thread 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 >; Sephe Qiao 
(Wicresoft) >; Kylie 
Liang >; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
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 >; Sephe Qiao 
(Wicresoft) >; Kylie 
Liang >; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
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
  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 >; Sephe Qiao 
(Wicresoft)

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

2016-01-31 Thread 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 
> 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 
>>;
 Sephe Qiao (Wicresoft) 
>>;
 Kylie Liang 
>>;
 
'freebsd-virtualization@freebsd.org' 
>>;
 BSD Integration Components for Hyper-V 
>>
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 
>>;
 Sephe Qiao (Wicresoft) 
>>;
 Kylie Liang 
>>;
 
'freebsd-virtualization@freebsd.org' 
>>;
 BSD Integration Components for Hyper-V 
>>
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:

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

2016-01-31 Thread 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 >; Sephe Qiao 
(Wicresoft) >; Kylie 
Liang >; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
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 >; Sephe Qiao 
(Wicresoft) >; Kylie 
Liang >; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
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
  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 >; Sephe Qiao 
(Wicresoft) >; Kylie 
Liang >; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
Subject: RE: Hyper-V networking: problem after upgrade to 10.2

Hello Dexuan,

Unfortunetely, no OACTIVE flag:

hn0: flags=8843 metric 0 mtu 1500
options=31b

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;

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

2016-01-31 Thread 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  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  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 >; Sephe
> Qiao (Wicresoft) >;
> Kylie Liang >; '
> freebsd-virtualization@freebsd.org'  >; BSD Integration Components
> for Hyper-V >
> 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 >; Sephe
> Qiao (Wicresoft) >;
> Kylie Liang >; '
> freebsd-virtualization@freebsd.org'  >; BSD Integration Components
> for Hyper-V >
> 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';

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

2016-01-31 Thread 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  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 >; Sephe
> Qiao (Wicresoft) >;
> Kylie Liang >; '
> freebsd-virtualization@freebsd.org'  >; BSD Integration Components
> for Hyper-V >
> 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 >; Sephe
> Qiao (Wicresoft) >;
> Kylie Liang >; '
> freebsd-virtualization@freebsd.org'  >; BSD Integration Components
> for Hyper-V >
> 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
> 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 >; Sephe
> Qiao (Wicresoft)

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

2016-01-31 Thread 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 >; Sephe Qiao 
(Wicresoft) >; Kylie 
Liang >; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
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 >; Sephe Qiao 
(Wicresoft) >; Kylie 
Liang >; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
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
  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

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

2016-01-31 Thread 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 >; Sephe Qiao 
(Wicresoft) >; Kylie 
Liang >; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
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 >; Sephe Qiao 
(Wicresoft) >; Kylie 
Liang >; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
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
  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 >; Sephe Qiao 
(Wicresoft) >; Kylie 
Liang >; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
Subject: RE: Hyper-V networking: problem after upgrade to 10.2

Hello Dexuan,

Unfortunetely, no OACTIVE flag: