Re: MFC of bhyve UEFI / Windows support?

[Peter Grehan]

Hi,


just a small question: Is a MFC of the bhyve UEFI / Windows support
planed in time for FreeBSD 10.3?


 Thanks to your work :), now in 10-stable as of

https://svnweb.freebsd.org/changeset/base/295124

later,

Peter.

___
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]

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

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