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;

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

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

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

VirtFS support in bhyve

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:

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

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

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

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

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,

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

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

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,

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

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

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

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: