Page MenuHomeFreeBSD

bhyve: allow for automatic destruction on power-off
ClosedPublic

Authored by kaktus on Jun 23 2020, 5:58 PM.
Tags
None
Referenced Files
F136997213: D25414.id.diff
Thu, Nov 20, 11:00 PM
F136993921: D25414.id73551.diff
Thu, Nov 20, 10:48 PM
F136993787: D25414.id73531.diff
Thu, Nov 20, 10:48 PM
F136993428: D25414.id73625.diff
Thu, Nov 20, 10:47 PM
F136991553: D25414.diff
Thu, Nov 20, 10:41 PM
Unknown Object (File)
Tue, Nov 18, 10:26 PM
Unknown Object (File)
Tue, Nov 18, 3:39 PM
Unknown Object (File)
Tue, Nov 18, 6:42 AM

Details

Summary

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

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

grehan added a subscriber: grehan.

Nice change. Don't forget to update the man page.

This revision is now accepted and ready to land.Jun 23 2020, 8:35 PM
kaktus added a reviewer: manpages.

Update man page.

@grehan happy for a MFC in say 2 weeks after commit to head?

This revision now requires review to proceed.Jun 23 2020, 10:04 PM

happy for a MFC in say 2 weeks after commit to head?

Yep, sounds good.

0mp added a subscriber: 0mp.

LGTM when it comes to the manual.

Also, maybe Relnotes: yes?

This revision is now accepted and ready to land.Jun 23 2020, 10:12 PM

This is a really great, thank you so much! Overall, this looks very good, only noticed one minor question.

usr.sbin/bhyve/bhyverun.c
807 ↗(On Diff #73551)

Not sure 1 still makes sense in this case. It's not indicating a failure or issue of some kind, is it?

As mentioned on irc, I believe we're bound by the already defined exit codes, as describes in section EXIT STATUS of bhyve(8).