This adds a -x flag to allow the reboot loop of bhyve(8) to be managed by an external process rather than internally by vmrun.sh
Submitted By: Paul Vixie
I do not believe this is a desirable change, at least it does not do what it claims it does.
Man pages sayes this is reboot, not sure what the differences are yet. I believe it is actually reset, and you have to do the reboot externally by re running the bhyve(8) command.
There are now exit code of 4, "exited due to an error"
The only case that this new code would trigger on would be if the bhyve exit code is 0, and -x was specified. How does that add any exit information?
Furthermore that would break the reboot while [ 1 ] loop, is that what your trying to achive?
Allan, would you update the diff please
Per emails with Paul Vixie we have come up with this:
-x Exit reboot loop even if bhyve exits with reboot code
Allan, can you update the diff please
We should probably call this exit_rebootloop, passthrough has a great deal of other context in bhyve.
@allanjude I know your work load is huge as well, if you need me to push a new diff I can do that, but then you have to agree to commit it or I have to pester bde/phk for an approval.
please do make this exit_rebootloop, no doubts in my mind now as to what is going on here, and that this should not be called passthrough due to confusion factor.
Above statement is correct, we should probably fix up the man page to more clearly explain the exit code 0
Adding a note, to above, yes this is trying to break the reboot while  loop, ie you want to manage reboots in a loop outside bhyve(8).
@rgrimes If you want to commandeer this review and put an updated diff, that would be great.
Note: this was originally submitted by Paul Vixie, it is not my work.
I am happy to commit it, although you are now release from mentorship if you want to commit it yourself, although remember to credit 'Paul Vixie (original version)'