Date: Tue, 19 Aug 2014 09:32:34 -0700 From: Craig Rodrigues <rodrigc@FreeBSD.org> To: Allan Jude <allanjude@freebsd.org> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: libvirt and rebooting of a bhyve VM Message-ID: <CAG=rPVe6FvEqHnHLx4CT8aJ=Eo5SWwdxC8JH6g4FxkoVqZftvw@mail.gmail.com> In-Reply-To: <53F37A6F.90405@freebsd.org> References: <CAG=rPVcGFSnMcMdrNtWjUtHUc0RLXps-t9WwzokNtyHQwWDfFQ@mail.gmail.com> <20140819154035.GA62903@kloomba> <EBFA02E4-AF67-4988-BF3F-5DB9F7D4BC76@jnielsen.net> <53F37A6F.90405@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 19, 2014 at 9:25 AM, Allan Jude <allanjude@freebsd.org> wrote: > > Yes, this revision adds the ability to 'reboot'. This does not exit > bhyve at all, so there is no exit level > > You can 'reboot' a bhyve externally using: > bhyvectl --force-reset --vm=xxx > > or force a poweroff with: bhyvectl --force-reset --vm=xxx > > SIGTERM simulates an ACPI shutdown > > > the bhyvectl --destroy is to clean up, the instance remains even after a > clean shutdown. In the past, it had to be destroyed and recreated to > start the VM again, although now with reboot support, that may not be > required. Can you suggest patches to vmrun.sh to make these new behaviors more obvious? People who write scripts over bhyve often look at vmrun.sh for inspiration. These new behaviors are definitely going in the right direction. -- Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG=rPVe6FvEqHnHLx4CT8aJ=Eo5SWwdxC8JH6g4FxkoVqZftvw>