From nobody Tue Sep 23 11:10:07 2025 X-Original-To: freebsd-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 4cWHM640Zmz68V9f for ; Tue, 23 Sep 2025 11:10:10 +0000 (UTC) (envelope-from meka@tilda.center) Received: from mail.nsd1.sysit.solutions (meka.rs [109.93.255.137]) (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 4cWHM56b68z4JYf for ; Tue, 23 Sep 2025 11:10:09 +0000 (UTC) (envelope-from meka@tilda.center) Authentication-Results: mx1.freebsd.org; none Received: from [192.168.111.162] (hal9000.nsd.sysit.solutions [192.168.111.162]) by mail.nsd1.sysit.solutions (Postfix) with ESMTPSA id 6D39B69520; Tue, 23 Sep 2025 11:10:07 +0000 (UTC) Message-ID: <44d9286c-0866-4805-827d-5cb91511800b@tilda.center> Date: Tue, 23 Sep 2025 13:10:07 +0200 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 User-Agent: Mozilla Thunderbird Subject: Re: GPU Passthrough on FreeBSD 14.3 (AMD Radeon RX 6900 XT and Windows 10 Pro) To: Matt Churchyard , Jonathan Vasquez Cc: "freebsd-virtualization@freebsd.org" References: <6CV-OY6BcErrWRit9jSpi6fWsYBG3E_Z3u6eTLPcz6foPAZV1gQpZYaZTR7JA_1ot5RQVqrWQaLxJFySXjspIhSbBJGxmckcDQyzxhALNus=@xyinn.org> <21e892ba-bea5-4e65-91cf-409e5e927f67@FreeBSD.org> <77221679b528434788d667441d1a32a2@userve.net> Content-Language: en-US From: =?UTF-8?Q?Goran_Meki=C4=87?= In-Reply-To: <77221679b528434788d667441d1a32a2@userve.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8400, ipnet:109.92.0.0/15, country:RS] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4cWHM56b68z4JYf On 9/23/25 10:59, Matt Churchyard wrote: > Bhyve is designed to trap a kill (term) signal and trigger acpi poweroff, so this is the documented and intended way to power off a guest > > From the man page: > > SIGNAL HANDLING > bhyve deals with the following signals: > SIGTERM Trigger ACPI poweroff for a VM > > This definitely works and is completely reliable with most guests. Vm-bhyve sends it twice as this seemed to get Windows to respond to the request much more consistently and it would often appear to completely ignore a single kill command. I don't know why this is the case though or whether other hypervisors do something different when requesting a shutdown compared to what bhyve does. Simply triggering acpi poweroff "should" be enough. I can just guess about this. When I press a power button on a desktop with Windows 10, it just ends screensaver (well, blank screen, to be precise), so I have to press it another time to actually turn it off. It does sound like a similar "issue". Regards, meka