Closed jclulow closed 12 years ago
It turns out that this intr_info
is a Double Fault, so is presumably deeply related to something we're still duffing in the SPT handling.
Sounds likely.
When someone in #illumos it this, I did some looking around and it appeared that folks had it it on vanilla joyent bits, as well. That may mean that whatever we're screwing can be reached without hitting any of the other bits which we already fixed (in my imagination, at least, this narrows things down somewhat).
Were they vanilla joyent bits from before the EPT-check was in place though? (thus still potentially exercising the SPT code if run on non-EPT hardware)
Yes they were, but that's not necessarily relevant to what I was hoping, in that I believe that on a non-EPT machine they'd usually panic. Unless my memory is failing me, this isn't the usual symptom of lacking EPT on those chips.
I'm reasonably confident, at this stage, that this is just another manifestation of the problems behind #7. Both issues have seemingly gone away since ensuring the 32bit root SPT was allocated in the first 4GB of physical memory.
Sometimes a VM will start, but instead of being useful will loop forever outputting this:
The only place it appears that this could come from in the code is
handle_exception
inkvm_vmx.c
. On that basis...(NB: this is using KVM built from branch rebase0 with hacks to target VMX and remove the requirement for EPT)