Date: Fri, 25 Oct 2024 16:49:23 -0400 From: Mark Johnston <markj@freebsd.org> To: Guido Falsi <mad@madpilot.net> 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: <ZxwEU6oPVP5a24MO@nuc> In-Reply-To: <6a2a37b3-353e-40ca-b8a9-f4ef97733da8@madpilot.net> References: <6a2a37b3-353e-40ca-b8a9-f4ef97733da8@madpilot.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 > I an also try bisecting, I'd guess the issue is quite recent. Which revision did you update from? > Thanks in advance for any advice. > > Obviously if any further info is needed just ask. What command line arguments are passed to bhyve? What boot firmware are you using?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZxwEU6oPVP5a24MO>