[Bug 274389] bhyve in 15-CURRENT unable to boot OpenBSD anymore

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274389

--- Comment #8 from John Baldwin <jhb@FreeBSD.org> ---
So it's an OS bug that it's writing 0 to "disable" a BAR as that doesn't work. 
However, bhyve crashing isn't really ideal either.  For a case like this where
there is a conflict, I think we should do something that isn't a crash. 
Probably the guest OS will assign a new range in the future if it actually
cares about the BAR in question.  The simplest approach might be to let the
"first" BAR that claims a region win and have other register attempts simply
fail (but mark the BAR as "unmapped" so we don't try to unregister it in the
future).  This would not fix the edge case that if the first device to register
the range moves its BAR (or disables decoding), the second device's BAR would
not start working, instead it would remain disabled.  However, given how odd of
a case this is, I'm fine with that.

Note that this is just about the assertion failure, and it doesn't help with
the first error reported as the original bug here which I think we still don't
understand.

-- 
You are receiving this mail because:
You are the assignee for the bug.