Date: Sat, 26 Oct 2024 21:39:22 +0200 From: Guido Falsi <mad@madpilot.net> To: Mark Johnston <markj@freebsd.org> Cc: Current FreeBSD <freebsd-current@freebsd.org>, "virtualization@freebsd.org" <virtualization@freebsd.org> Subject: Re: bhyve regression (head): windows VMs failing with error 0xc000021a Message-ID: <1e415841-211f-4a36-9efe-d05163a661ae@madpilot.net> In-Reply-To: <Zxzua2WC3fyx17_8@nuc> References: <6a2a37b3-353e-40ca-b8a9-f4ef97733da8@madpilot.net> <ZxwEU6oPVP5a24MO@nuc> <48eb1621-4b22-4080-8e80-059d475244f3@madpilot.net> <Zxzua2WC3fyx17_8@nuc>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26/10/24 15:28, Mark Johnston wrote: > On Fri, Oct 25, 2024 at 11:12:48PM +0200, Guido Falsi wrote: >> On 25/10/24 22:49, Mark Johnston wrote: >>> On Fri, Oct 25, 2024 at 09:24:13PM +0200, Guido Falsi wrote: >>>> Hi, >>>> >>>> I've recently updated my current machines to git commit >>>> 525a177c165740fc697df3de5b92e58b3b41477c (Sun Oct 20 22:43:41 2024 -0800) >>>> and just have Windows 10 VMs fail to start in bhyve with the error in the >>>> subject. >>>> >>>> I've been unable to recover them with usual tricks (automatic recovery, >>>> chkdsk, and other tools provided by the OS). Looks like the machine fails to >>>> read C: after boot. >>>> >>>> These machines were working fine before the update, so my suspect is that >>>> some recent change in bhyve is causing the issue and the VMs would be >>>> otherwise fine. >>>> >>>> The VMs have their filesystems in compressed zvols. >>>> >>>> Anyone has an idea or can point to some change I can test reverting? >>> >>> Just a guess, but you might try adding "-o pci.enable_bars=true" to the >>> bhyve command line arguments >> >> Tried but it looks like it made no difference. >> >>> >>>> I an also try bisecting, I'd guess the issue is quite recent. >>> >>> Which revision did you update from? >> >> I updated from git commit 450a6690f557493bd33d8f3666b22ddc5150703b (Thu Sep >> 19 11:49:40 2024 -0500) >> >> In the while I noticed some commits to TPM emulation/passthorugh, maybe >> they're related? > > It might be, but I don't see any TPM devices configured in the > invocation below. > > There was a number of changes to usr.sbin/bhyve in that window, so > reverting them one by one would probably turn up the culprit. Or, you > need to pick up commit 8c8ebbb045185396083cd3e4d333fe1851930ee7, given > that you're using AHCI emulation. Thanks for the suggestions. I'm using AHCI since it is suggested for windows guests. (BTW I'm trying to get rid of windows guests, but I still need them from time to time) I'll try updating again including the commit you suggest first. I'll report back if that fixes the issue. -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1e415841-211f-4a36-9efe-d05163a661ae>