From nobody Tue Oct 14 10:05:32 2025 X-Original-To: virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4cm8wx0smDz6C8wv for ; Tue, 14 Oct 2025 10:05:37 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fout-b6-smtp.messagingengine.com (fout-b6-smtp.messagingengine.com [202.12.124.149]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4cm8ww0g4Mz3wbN for ; Tue, 14 Oct 2025 10:05:36 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=CMgYwdLr; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=lebGSQOq; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 202.12.124.149 as permitted sender) smtp.mailfrom=void@f-m.fm Received: from phl-compute-04.internal (phl-compute-04.internal [10.202.2.44]) by mailfout.stl.internal (Postfix) with ESMTP id BBD3C1D000F6 for ; Tue, 14 Oct 2025 06:05:34 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-04.internal (MEProxy); Tue, 14 Oct 2025 06:05:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm2; t=1760436334; x=1760522734; bh=SKDzFtfTyc wBIv59qVlmyII+prulAa2o42gxrcsiArQ=; b=CMgYwdLrUhOxAwtCLjUjuz93wk 8kQYBsEDjlCw23j4IoPcVMQ+oyEKohUsMJc+gv7vxJZvuMupZ+g0vZK+cUxEQ6SJ YKMh7o/GzT5QQNGnpqGDaD7BKBXJZJrrBzJAKstRBWghJhk21w/0wmLa0y2ifuCR 7VTIFvKSMFukfUkDhukvt7ZPuVAtAq1cKstx2+8uyz8RZ9gLA3/80DM5wRCN8prP XZWE+UgNgT/n7Yoq97AmB4GKvJfAYpFJIE+Er9ceA4mO2eEo3cZMLGNmR7WES9Bl 18IoQMmSnyePlzOyTmw4dABRkAPG8jSZiChc4BWc5lMU3ekOGlJCVwfpPQUg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1760436334; x=1760522734; bh=SKDzFtfTycwBIv59qVlmyII+prulAa2o42g xrcsiArQ=; b=lebGSQOqcEXLn0oIdZrOsbwVzcMOz5VW57SQo3vxkrWMTbe/kt0 +3C5rIlh/WCpsgOAhcL9KqVYLdzf9ZSsKUxtKHwbyuNuB9IgzRPfkbxr63Ox757w witccGBTPSTiEXuBl4Q743EAkvAGXwl8AmYYbcwCbMC8CPeD1efiCaUfyxAbdLBa ZG7hyFnBWFWt9JfvTV+ULtE8AggW1Klx38vd2dIERsXU0qW8XyeIVK2PUlSXnf1m Fp34JWQjnU+xXahkdZKzSJrRqCLJr2QjCwgJZRA/XIucWOuf6udpUUgbVSdYmKaR o9s1WWT6DDuEvqwSj++SPQQh2nmp/PkxJjw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggdduvddtvdehucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtredttd dtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgrthht vghrnhepkeeluddvlefhieelfefggffhffektdehleelgfdugfdvgeekjeejuddtheehgf eunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepvhho ihgusehfqdhmrdhfmhdpnhgspghrtghpthhtohepuddpmhhouggvpehsmhhtphhouhhtpd hrtghpthhtohepvhhirhhtuhgrlhhiiigrthhiohhnsehfrhgvvggsshgurdhorhhg X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Tue, 14 Oct 2025 06:05:34 -0400 (EDT) Date: Tue, 14 Oct 2025 11:05:32 +0100 From: void To: virtualization@freebsd.org Subject: Re: how to make bhyve gracefully shutdown a guest Message-ID: References: List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-virtualization@freebsd.org Sender: owner-freebsd-virtualization@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.02 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.995]; NEURAL_HAM_SHORT(-0.99)[-0.989]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; NEURAL_HAM_LONG(-0.44)[-0.439]; R_SPF_ALLOW(-0.20)[+ip4:202.12.124.128/27]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; RCVD_IN_DNSWL_LOW(-0.10)[202.12.124.149:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[virtualization@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MLMMJ_DEST(0.00)[virtualization@freebsd.org]; ASN(0.00)[asn:151847, ipnet:202.12.124.0/24, country:AU]; RCVD_VIA_SMTP_AUTH(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] X-Rspamd-Queue-Id: 4cm8ww0g4Mz3wbN On Mon, Oct 13, 2025 at 06:38:15PM -0700, Paul Vixie wrote: >Kill(1) on bhyve with the default TERM signal makes bhyve >send acpi shutdown to the guest. This is what vm-bhyve seems to do. OK thanks for that. Kind of surprised bhyvectl doesn't, well, ctl in this way, but here we are. The context is where there's a stable/15 server running various linux and otherbsd guests. I want sysutils/nut (client) to shut down everything gracefully when battery gets to 10%. I thought I could do that by getting nut to tell the server via bhyvectl to gently poweroff the clients directly. Or failing that, run nut on the server to do the same. In the datacentres there's different equipment to handle this. It's the first time i'm hand-rollong it. --