BIOSes are also just software, and we have to deal with bugs in them
*all the time*. The reality is that we're going to have to deal with
both vendor and user reluctance to upgrade, and therefore have to deal
with brokenness in the field. As far as detection code is concerned, I
certainly have pushed back on the most disgusting (and broken) attempts,
as well insisted that the code be properly centralized.
It's functionally equivalent to hardware workarounds. There is always a
judgement call when something should be forked off into a separate
driver, which is exactly what this amounts to.
That is a possibility, but that is a technical issue versus a
pseudo-philosophical issue. However, there are clearly a few different
problems here with the start-and-stop nature of the virtual environment
versus the needs of physical environments, and it's not clear to me that
they are inherently compatible, or whether that would entail dangerous