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

2016-02-02 Thread 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 >; 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,

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

Re: VirtFS support in bhyve

2016-02-02 Thread Nikos Vassiliadis 



On 02/01/16 04:22, jc...@freebsd.org wrote:

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.


Hi Jakub,

This is a very cool project! Does this apply to 10-STABLE also?
Could you provide a patch for the people who are not familiar with
github?

Thanks,
Nikos
___
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-02-02 Thread 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 ; 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

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 >; 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,

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