#FreeBSD friends, who do I nudge in which direction for an update to the following:
"Windows installation has been tested with [Server] 2012r2" - although technically that's only fully EOL like a fortnight ago? (!!)
#FreeBSD friends, who do I nudge in which direction for an update to the following:
"Windows installation has been tested with [Server] 2012r2" - although technically that's only fully EOL like a fortnight ago? (!!)
@voltagex
I didn't know there was any Windows support. OOC, have you tried a newer version of Windows to see if it works?
@jbowen short on hardware and fast storage at the moment (gestures to the everything)
Evaluating moving from QEMU to bhyve.
@jbowen https://wiki.freebsd.org/bhyve/Windows pointing to some random batch file with over a thousand lines of code is somewhat gutsy.
@voltagex also, is the 2016 firmware appropriate?
Orientation: the manual page is in the FreeBSD ports collection, not base.
<https://www.freshports.org/sysutils/vm-bhyve/> has the maintainer's email address, and leads to the GitHub repo, which is in the FreeBSD organisation:
<https://github.com/freebsd/vm-bhyve>
You can use the second of the two bug icons in FreshPorts to make a report.
Cc @dexter
RE: https://beige.party/@fuzzy/117495054590263511
FYI – IMHO this is not a FreshPorts issue:
― for casual users (without an account in Bugzilla for FreeBSD), it seems that the first of the two bug icons in the FreshPorts page for a port is no longer effective.
For example, via <https://www.freshports.org/sysutils/vm-bhyve/>:
Error 403 This search operator requires an account.
Cc @voltagex