OS-6612: reboot in bhyve guest should reboot, not poweroff

Resolution

Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2018-02-15T13:40:57.686Z)

Related Issues

Related Links

Description

When a guest OS issues a reboot, the expectation is that the guest will come back. Curently, the bhyve (or zhyve) process exists and no boot follows.

Comments

Comment by Jerry Jelinek
Created at 2018-02-14T20:56:22.407Z
I've pushed the illumos-joyent side of this but we also need a vmadmd fix to prevent it from halting the zone after it reboots.

Comment by Jerry Jelinek
Created at 2018-02-15T13:31:21.952Z
Josh fixed the vmadmd issue with commit 58ac029ac.

Comment by Jerry Jelinek
Created at 2018-02-16T20:26:49.561Z
Updated at 2018-02-16T20:44:22.886Z
This has been tested with the bhyve brand, along with OS-6626 and OS-6627. The VM will reboot now if the reboot command is issued from within the VM and it will shutdown if the halt command is used. Asking for too much memory will now fail with ENOMEM and we can now ask for more memory than 1/2 of the system's memory. In addition, I have halted and rebooted an lx zone and a native zone (from within the zone).

Comment by Jira Bot
Created at 2018-02-16T22:55:35.900Z
illumos-joyent commit fa7f53629a85f53179cc4dda4b8fb062a7a05124 (branch master, by Jerry Jelinek)

OS-6612 reboot in bhyve guest should reboot, not poweroff
OS-6626 bhyve hangs forever when requesting too much kernel memory
OS-6627 bhyve needs to support 100+ GB RAM
Reviewed by: Patrick Mooney <patrick.mooney@joyent.com>
Reviewed by: Mike Gerdts <mike.gerdts@joyent.com>
Approved by: Patrick Mooney <patrick.mooney@joyent.com>