Each update has to be the complete diff, no diff-update, now I know. Sorryt for the mess.
This is the actually intended update as described in the previous update comment.

Found and fixed some errors after copying rc.d/bhyve onto a old FreeBSD 13.0 productive machine:

Hi Mark, thanks for your review.

Latest revision has some trailing white space fixes (no functional change) and default rc.conf variable "bhyve_conf" adjusted to reflect previous change (bhyve_conf="/etc/bhyve_config.d")

Removed local _ifconfig_descr leftover from previously corrected autoif() hack

Replaced PoC diff with real tested diff - sorry for the mess.
This version corresponds to what the summary and the bug report (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285947) describe.

Better 'ifconfig description' handling - previous hack wasn't limited to ifn_start condition.

• Rename rc.conf(5) variable names "bhyve_cfg" to "bhyve_conf" and "bhyve_startupjournal" to "bhyve_launchstate" along with its filename.

Got it, you are right 'startupjournal' is wrong. Since it's only very loos state tracking, I I hesitated using naything with »state»...
I'm about to do some more production tests and will come up with a new diff these days - will change # REQUIRE: to DAEMON - even in jail motsly everybody will wan netwiork running before VM starts.|
Also the examples were not well generalized - will replace too.
Question for $bhyve_conf:
I guess /etc/bhyve.conf.d is better than /etc/bhyve.d.
jail(8) has jail.conf(5) and e/etc/jail.conf.d.
bhuve(8) has bhyve_config(5) - shall there be a relation to .d/, like /etc/bhyve_config.d ?

Thanks, ev, I was unsure about the uncommon "bhyve_cfgdir" but my reason to keep it uncommon was that the config file itself is in 'uncommon' format too in the context of parsing a config file from an rc(8) script.
But I'm fine with renaming if this kind of hint is more confusing than helpful of course.

In D44487#1042843, @vsasjason_gmail.com wrote:

In D44487#1014651, @mat wrote:

but we want users to stop using ports and use packages

Excuse me for intervention with off topic, but this is extremely important to note, so please don't. The sole reason I use FreeBSD (I'm pretty sure not only me) is easy customization, including customization via ports framework.

Happy consumer of the loader and vt (D35983) patch, thanks a lot (pocket3 PC).
Hope this will make it into main sooner than later!

Couldn't find my old PR - ever since USES= ... python, I limit to build dependency only
Is there anything I miss which requires python for run-time?