From nobody Mon Sep 22 16:12:06 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 4cVp6926nLz685xJ for ; Mon, 22 Sep 2025 16:12:17 +0000 (UTC) (envelope-from jon@xyinn.org) Received: from mail-4317.protonmail.ch (mail-4317.protonmail.ch [185.70.43.17]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4cVp666Ny0z3h3x for ; Mon, 22 Sep 2025 16:12:14 +0000 (UTC) (envelope-from jon@xyinn.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=xyinn.org header.s=protonmail3 header.b=Sj4i3uh6; dmarc=pass (policy=none) header.from=xyinn.org; spf=pass (mx1.freebsd.org: domain of jon@xyinn.org designates 185.70.43.17 as permitted sender) smtp.mailfrom=jon@xyinn.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xyinn.org; s=protonmail3; t=1758557531; x=1758816731; bh=LauRQ0rexgjcqo1b1F+shTsjYGSzAEIIAzEsa8kCuos=; h=Date:To:From:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=Sj4i3uh6Z/8xtvm6YsdmEgwuej9WjySGdN0JwbRrGbsh10Sy3eDHybhqZkmZHjbVx IZ72mWXWyr6sdX3nCXHbh3/qgK7hLQFuXf/7mXpnyNdW0bZASEjj8n4GmmVihc7piH N1x2OnSoXsS9ZBtL39K/YCldJCFconsm+fxDf5iqMjuiia2o2CtRm0T4tUb/tVgZcf FPBMD3PWBEYhajjiynszgX6sETw8yT9mQ3nwLYnNlelsSm1wkAfcmhcwtWT7dN5pw/ fFg7Dnkg6KWPSma/EMZKH2vwM4QhQSaVSG5fQ4hFv5zXRfjsD3CXxOKIjKUE0N2JZP jxXI1CeEFYWqA== Date: Mon, 22 Sep 2025 16:12:06 +0000 To: "virtualization@freebsd.org" From: Jonathan Vasquez Subject: Re: GPU Passthrough on FreeBSD 14.3 (AMD Radeon RX 6900 XT and Windows 10 Pro) Message-ID: In-Reply-To: <21e892ba-bea5-4e65-91cf-409e5e927f67@FreeBSD.org> References: <6CV-OY6BcErrWRit9jSpi6fWsYBG3E_Z3u6eTLPcz6foPAZV1gQpZYaZTR7JA_1ot5RQVqrWQaLxJFySXjspIhSbBJGxmckcDQyzxhALNus=@xyinn.org> <7YJWddCC_SUuB_mwDmHL3xecft8_rMou1xosTzBIK1UP_Fw-B786LWZX6CQ8XG6smJQRlxbfJbCq8fmTI15RouBn8GN73IfJvPOg7k6jr-s=@xyinn.org> <21e892ba-bea5-4e65-91cf-409e5e927f67@FreeBSD.org> Feedback-ID: 12351801:user:proton X-Pm-Message-ID: 0208653425ad4b23e510c61479afb79b264e1b0d 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=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.40 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[xyinn.org,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[185.70.43.17:from]; R_DKIM_ALLOW(-0.20)[xyinn.org:s=protonmail3]; R_SPF_ALLOW(-0.20)[+ip4:185.70.43.0/24]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_ONE(0.00)[1]; MISSING_XM_UA(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEFALL_USER(0.00)[jon]; RCVD_COUNT_ZERO(0.00)[0]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[185.70.43.17:from]; TO_DN_EQ_ADDR_ALL(0.00)[]; MLMMJ_DEST(0.00)[virtualization@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[xyinn.org:+] X-Rspamd-Queue-Id: 4cVp666Ny0z3h3x The machine ran for 22+ hours with no issues. I decided today to do a fresh restart of the host and the vm to continue testing the "deterministic stability" of the setup. A few minutes after it started, the= VM exited with a 0x88. This is a new error code that I haven't seen before. I then rebooted the host/vm again and so far it's be= en running fine for the past 1h27m on idle. So the stability still seems to be MUCH better than when I was using the multi-functional de= vice on 18/0/0 for the USB controller. Using the 13/0/0 USB controller (th= at isn't multi-functional) has massively increased stability. I'm not expecting the VM to be perfectly stable for 365 days 24/= 7 given that even regular "real" machines also act weird / have issues ever= y once in a while. I've uploaded some of the crashes I got back when I had = the 18/0/0 setup which was giving me more frequent crashes with error 0x60,= and I've also posted the one I got today after the reboot with 0x88. I'm n= ot sure if this is enough because it's hard to get debug information from t= he console output that bhyve is displaying. Usually when the VM crashes I j= ust see my console say: exited with NDELAY mode or something like that. Which is the same message I= see when I do a regular shut down. So not very helpful. You can find the output of "bhyvectl --vm=3D --get-all" (which includ= es --get-exit-reason) here: https://xyinn.org/freebsd/files/gpu_pass/bhyve_= crashes/ also, does anyone know how I can send the ACPI shutdown signal to my bhyve = VM? I looked at the source code for vm-bhyve, and I just see it does a regu= lar 'kill'. I also saw some people online recommending to do a "pkill bhyve= ", but regardless of what I do, doing a kill/pkill on the PID running my bh= yve vm doesn't actually do anything. The VM still continues functioning per= fectly fine. I would like to be able to shutdown the machine from the host = so I can do a graceful shutdown. I can easily run my start up script by add= ing: @reboot root /path/to/gaming/script.sh in /etc/crontab, and that works fine, but I can't get it a signal from the = host to the vm so I can automate the shutdown counterpart. Thank you!