Re: Understanding Bhyve shutdown

2016-04-20 Thread Roman Bogorodskiy
Neel Natu wrote: > Hi Roman, > > On Wed, Apr 13, 2016 at 3:55 AM, Roman Bogorodskiy > wrote: > > Hi, > > > > I was trying to get better understanding of how to properly shutdown VMs > > in bhyve, but unfortunately the documentation does not provide much > > details on that. > > > > Specificall

Re: Understanding Bhyve shutdown

2016-04-19 Thread Neel Natu
Hi Roman, On Wed, Apr 13, 2016 at 3:55 AM, Roman Bogorodskiy wrote: > Hi, > > I was trying to get better understanding of how to properly shutdown VMs > in bhyve, but unfortunately the documentation does not provide much > details on that. > > Specifically, handbook [I] suggests to reboot a machi

Re: Understanding Bhyve shutdown

2016-04-16 Thread Roman Bogorodskiy
Matt Churchyard wrote: > As I understand it > > 1) shutdown from guest > 2) 'kill ' -> pressing the power button once. > 3) --force-poweroff -> holding power button in > 4) --force-reset -> pressing the reset button > 5) bhyvectl --destroy -> same as 3? (although vmm is destroyed as well) > >

RE: Understanding Bhyve shutdown

2016-04-13 Thread Matt Churchyard via freebsd-virtualization
ssible of course. Matt -Original Message- From: owner-freebsd-virtualizat...@freebsd.org [mailto:owner-freebsd-virtualizat...@freebsd.org] On Behalf Of Roman Bogorodskiy Sent: 13 April 2016 11:55 To: freebsd-virtualization@FreeBSD.org Subject: Understanding Bhyve shutdown Hi, I was t

Re: Understanding Bhyve shutdown

2016-04-13 Thread Nikos Vassiliadis
Hi Roman, On 04/13/16 13:55, Roman Bogorodskiy wrote: Q1: Is there a way to know if a guest reacted to power button but waiting for the bhyve process to terminate? I just signal repeatedly $bhyve_pid until it's gone. For what it's worth, I use this /etc/rc.shutdown.local: PATH=/sbin:

Understanding Bhyve shutdown

2016-04-13 Thread Roman Bogorodskiy
Hi, I was trying to get better understanding of how to properly shutdown VMs in bhyve, but unfortunately the documentation does not provide much details on that. Specifically, handbook [I] suggests to reboot a machine and then run bhyvectl --destroy on it. The bhyvectl(8) manpage mentions the '