Date: Mon, 25 May 2015 02:01:46 -0400 From: Allan Jude <allanjude@freebsd.org> To: freebsd-virtualization@freebsd.org Subject: Re: can we get some interaction between halt/reboot and bhyve? Message-ID: <5562BACA.4040104@freebsd.org> In-Reply-To: <5562A5D0.7050207@redbarn.org> References: <5562755C.8090407@redbarn.org> <20150525030835.GB37063@funkthat.com> <5562A5D0.7050207@redbarn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --R18NtFvO4RNG2FiWQQcOVl3cmewS4HObl Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-05-25 00:32, Paul Vixie wrote: >=20 >=20 > John-Mark Gurney wrote: >> Shouldn't shutdown be used instead of reboot/halt? This allows >> various rc.d scripts to run, and you can use that to make sure all >> your bhyve instances are shutdown... >=20 > yes. but, if the reboot or poweroff or halt command is used, i'd like m= y > bhyve's to have enough time to umount their ufs zvol's. the rc.d script= > should pass along some softer signal that can cause the bhyve to do its= > own clean shutdown. but where SIGTERM is used, which is passed on as > ACPI power-off, i'd like busy (that is, not hung, trying hard to shut > down cleanly) bhyve's to get more time. the current poweroff/halt/reboo= t > command only looks for evidence of paging as a reason to extend the tim= e > between SIGTERM and SIGKILL. i'd like to give it some bhyve-relevant > additional reason to delay that SIGKILL. >=20 One option might be a sysctl to control how much time processes are given between the SIGTERM and SIGKILL. Right now, it looks like, unless paging it detected, processes are only given 5 seconds, which is definitely not enough for bhyve and some other processes. A tunable gives people the option of how long they want to wait. On my laptop, I likely want to shutdown in a hurry, but on my virtualization server, I'm willing to wait a few minutes to keep the shutdown clean. --=20 Allan Jude --R18NtFvO4RNG2FiWQQcOVl3cmewS4HObl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJVYrrNAAoJEJrBFpNRJZKfWGgQAINXV2z3PszdKo4eY3/FIEP0 fqbd1t19enf9Q0aTqoDzKXzSlvpWGi0B/rKgh7XGJsXEdRlZJC6TXpWt8Itkv01J oF+bLVdnjTS32pRS8OEphMdDKdHoWKyjrL+hgsiJPpVcNOdGXn5HSL+P7MLcuuPj Mnb6q07UxdjEiyqBZcjamwOJxXBsuBo+jAsqlYe9OdVV4yY87SqxbDW1uhDn2s4v TvE3wUClbFMjN7z1Sr9zvU4u5qAdI8Lz4g5yDwl8ku1TTB3yWh05kGnlKcpMDEA3 OAm4b1tcKhZueRCCpXP4l0c6r90OLTSpneeHzk3XF6FpHjS8gyE80TVRnP7fqe8C xw8R6ZuMaAV1WsZ60dZO7EXBsDSp1HZ7fbhUsJ6z7YwamzxR8LXI1B7rmxPNEERO vAmcY4WnmHLyMb8zPoF+UPkWm9GTTTbyOCAP5EItee67D8Ffh3xXkHAb8om6PT9H A/sPtYqci2cpNRYQYPUMlFCgr71ej2ArHx/ciEjgdHQ7Yt1JAnpZSNRqpF4QJ6jf r1B+Gpb3CBGwL0TcanosQdieldZBbGZUk83YWDm4pt9XUbLvHPecgiuad7jYwilS CvS5uMILNZ0uZbMI3SsvkWuwuzy7Moo7Xqw9VeYySTQgZMI59Tu1Yr7ad3oYai/Z 3IV9MBNt59TiTz8DE9fA =QcfQ -----END PGP SIGNATURE----- --R18NtFvO4RNG2FiWQQcOVl3cmewS4HObl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5562BACA.4040104>