Introduce -D flag that allows for the VM to be destroyed on guest initiated power-off by the bhyve(8) process itself.
This is quality of life change that allows for simpler deployments without the need for bhyvectl --destroy.
Requested by: swills
Paths
| Differential D25414 Authored by kaktus on Jun 23 2020, 5:58 PM.
Details Summary Introduce -D flag that allows for the VM to be destroyed on guest initiated power-off by the bhyve(8) process itself. Requested by: swills
Diff Detail
Event TimelineHerald added subscribers: bcran, rgrimes, imp. · View Herald TranscriptJun 23 2020, 5:58 PM2020-06-23 17:58:53 (UTC+0) Harbormaster completed remote builds in B31900: Diff 73531.Jun 23 2020, 5:58 PM2020-06-23 17:58:56 (UTC+0) This revision is now accepted and ready to land.Jun 23 2020, 8:35 PM2020-06-23 20:35:11 (UTC+0) This revision now requires review to proceed.Jun 23 2020, 10:04 PM2020-06-23 22:04:54 (UTC+0) Harbormaster completed remote builds in B31910: Diff 73551.Jun 23 2020, 10:04 PM2020-06-23 22:04:56 (UTC+0) This revision is now accepted and ready to land.Jun 23 2020, 10:12 PM2020-06-23 22:12:02 (UTC+0) Comment Actions This is a really great, thank you so much! Overall, this looks very good, only noticed one minor question.
Comment Actions As mentioned on irc, I believe we're bound by the already defined exit codes, as describes in section EXIT STATUS of bhyve(8). Closed by commit rS362612: bhyve: allow for automatic destruction on power-off (authored by kaktus). · Explain WhyJun 25 2020, 12:35 PM2020-06-25 12:35:43 (UTC+0) This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 73625 head/usr.sbin/bhyve/bhyve.8
head/usr.sbin/bhyve/bhyverun.c
|
style(9) was recently changed to permit the braces that were here. I personally prefer the braces, especially in cases like this, where the else has braces.