Re: bhyve regression (head): windows VMs failing with error 0xc000021a

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.

HI again, thanks for the suggestion, updating to a newer head including 
this commit "fixed" the issue.

SO if there was a regression it's already been fixed.

Thanks again for your help!

-- 
Guido Falsi <mad@madpilot.net>