Opened 4 years ago
Last modified 6 months ago
#16664 new bug
Virtualization: support hyper-v
| Reported by: | nephele | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Drivers | Version: | R1/beta2 |
| Keywords: | Cc: | ||
| Blocked By: | #13310, #16665, #18882 | Blocking: | |
| Platform: | All |
Description
We should support running as a hyper-v guest.
This requires we add some support, for instance a video driver to get resolutions above the 1152x768 the hyper-v bios gives us.
Reference from MS: https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/tlfs/tlfs
linux has a file called hyperv_fb.c in their fbdev driver that adds their support.
Change History (7)
comment:1 by , 4 years ago
| Blocked By: | 16665 added |
|---|
comment:2 by , 4 years ago
comment:3 by , 8 months ago
| Blocked By: | 18882 added |
|---|
comment:4 by , 6 months ago
Support for the non-legacy network adapter would be good, as FreeBSD deprecated and removed the network driver on which ours for the legacy network adapter is based (see ticket:18550:11).
comment:5 by , 6 months ago
I‘m confused, hyper-v is a windows specific thing, does FreeBSD support it too?
comment:6 by , 6 months ago
FreeBSD has a network driver for the modern (non-legacy) network adapter of Hyper-V (https://man.freebsd.org/cgi/man.cgi?query=hv_netvsc&sektion=4&apropos=0&manpath=FreeBSD+14.0-RELEASE). They removed the driver for the legacy network adapter ("de") starting from FreeBSD 13. Our network driver dec21xxx is based on that.
comment:7 by , 6 months ago
Ah okay, I think for the short term their removal of the driver does not affect us much.
Before we can port this driver we likely need the basic hyper-v protocol down first (which is iirc basically a ring buffer in RAM for commands).
But this is good to know.
Good call, upvoting!