It didn't 'disappear', it was held for moderation. Moderation happens to all new users for the first 10 posts and 10 days. Mods aren't around 24/7 though, so things might be stuck in the moderation queue for a few hours.
% bhyve -k
bhyve: option requires an argument -- k
Usage: bhyve [-AaCDeHhPSuWwxY]
[-c [[cpus=]numcpus][,sockets=n][,cores=n][,threads=n]]
[-G port] [-k config_file] [-l lpc] [-m mem] [-o var=value]
[-p vcpu:hostcpu] [-r file] [-s pci] [-U uuid] vmname
…
-k: key=value flat config file
…
%Thanks for giving it a try but I don't see as what you see so the configuration file is not relevant yet.
% bhyve -k
bhyve: illegal option -- k
Usage: bhyve [-aehuwxACDHPSWY]
[-c [[cpus=]numcpus][,sockets=n][,cores=n][,threads=n]]
[-l <lpc>]
[-m mem] [-p vcpu:hostcpu] [-s <pci>] [-U uuid] <vm>
-a: local apic is in xAPIC mode (deprecated)
-A: create ACPI tables
-c: number of cpus and/or topology specification
-C: include guest memory in core file
-D: destroy on power-off
-e: exit on unhandled I/O access
-h: help
-H: vmexit from the guest on hlt
-l: LPC device configuration
-m: memory size in MB
-p: pin 'vcpu' to 'hostcpu'
-P: vmexit from the guest on pause
-s: <slot,driver,configinfo> PCI slot config
-S: guest memory cannot be swapped
-u: RTC keeps UTC time
-U: uuid
-w: ignore unimplemented MSRs
-W: force virtio to use single-vector MSI
-x: local apic is in x2APIC mode
-Y: disable MPtable generationBased on bhyve(8), my first thought would be that the
-k option disappeared between patchlevels 4 and 5?
root@molly:~ # bhyve -k
bhyve: option requires an argument -- k
Usage: bhyve [-AaCDeHhPSuWwxY]
[-c [[cpus=]numcpus][,sockets=n][,cores=n][,threads=n]]
[-G port] [-k config_file] [-l lpc] [-m mem] [-o var=value]
[-p vcpu:hostcpu] [-r file] [-s pci] [-U uuid] vmname
-A: create ACPI tables
-a: local apic is in xAPIC mode (deprecated)
-C: include guest memory in core file
-c: number of CPUs and/or topology specification
-D: destroy on power-off
-e: exit on unhandled I/O access
-G: start a debug server
-H: vmexit from the guest on HLT
-h: help
-k: key=value flat config file
-l: LPC device configuration
-m: memory size in MB
-o: set config 'var' to 'value'
-P: vmexit from the guest on pause
-p: pin 'vcpu' to 'hostcpu'
-S: guest memory cannot be swapped
-s: <slot,driver,configinfo> PCI slot config
-U: UUID
-u: RTC keeps UTC time
-W: force virtio to use single-vector MSI
-w: ignore unimplemented MSRs
-x: local APIC is in x2APIC mode
-Y: disable MPtable generationIf I may suggest, just to cover all bases:
freebsd-version -ukr% man freebsd-version
<snip>
-k Print the version and patch level of the installed kernel.
Unlike uname(1), if a new kernel has been installed but the
system has not yet rebooted, freebsd-version will print the
version and patch level of the new kernel.
-r Print the version and patch level of the running kernel. Un-
like uname(1), this is unaffected by environment variables.same book: p. 415 (Section 8.10):
There are basically two parts, the vmm(4) kernel module and the bhyve(8), bhyvectl(8) and bhyveload(8) userland tools to manage them. So it's both. The kernel module doesn't do much without the userland tools and the userland tools don't work without the kernel module.
from your screenshot, it looks like you have userland (theHere are some additional information:
-u option to freebsd-version) at patchlevel 4, while kernel (the -k option) is at patchlevel 5. I guess mentally, I'm still stuck onto that bit of info. 
% uname -iKrsU
FreeBSD 14.0-CURRENT GENERIC-NODEBUG 1400046 1400046
% bhyve -k to present what's seen at <https://forums.freebsd.org/threads/command-doesnt-understand-k-option.83596/post-549862> above.grahamperrin@mowa219-gjp4-vm-freebsd-13-zfs:~ % freebsd-version -kru
13.0-RELEASE-p4
13.0-RELEASE-p4
13.0-RELEASE-p5
grahamperrin@mowa219-gjp4-vm-freebsd-13-zfs:~ % su -
Password:
root@mowa219-gjp4-vm-freebsd-13-zfs:~ # setenv PAGER cat && freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 2 mirrors found.
Fetching metadata signature for 13.0-RELEASE from update1.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
No updates needed to update system to 13.0-RELEASE-p5.
root@mowa219-gjp4-vm-freebsd-13-zfs:~ # bhyve -k
bhyve: illegal option -- k
Usage: bhyve [-aehuwxACDHPSWY]
[-c [[cpus=]numcpus][,sockets=n][,cores=n][,threads=n]]
[-l <lpc>]
[-m mem] [-p vcpu:hostcpu] [-s <pci>] [-U uuid] <vm>
-a: local apic is in xAPIC mode (deprecated)
-A: create ACPI tables
-c: number of cpus and/or topology specification
-C: include guest memory in core file
-D: destroy on power-off
-e: exit on unhandled I/O access
-h: help
-H: vmexit from the guest on hlt
-l: LPC device configuration
-m: memory size in MB
-p: pin 'vcpu' to 'hostcpu'
-P: vmexit from the guest on pause
-s: <slot,driver,configinfo> PCI slot config
-S: guest memory cannot be swapped
-u: RTC keeps UTC time
-U: uuid
-w: ignore unimplemented MSRs
-W: force virtio to use single-vector MSI
-x: local apic is in x2APIC mode
-Y: disable MPtable generation
root@mowa219-gjp4-vm-freebsd-13-zfs:~ #stable/13, are
github.com
github.com
fprintf(stderr,
"Usage: %s [-AaCDeHhPSuWwxY]\n"
" %*s [-c [[cpus=]numcpus][,sockets=n][,cores=n][,threads=n]]\n"
" %*s [-G port] [-k config_file] [-l lpc] [-m mem] [-o var=value]\n" case 'k':
parse_simple_config_file(optarg);
break;static void
parse_simple_config_file(const char *path)
{
Unless you're thoroughly familiar with the code and documentation and how things even add up, "15-minute bug-quash" is a total joke.