The message about the MTRRs is just a warning. The PSOD was the result of a #GP exception. Please boot ESXi with the additional vmkernel option "vmbASLR=FALSE" and post an image of the PSOD.
Thanks Jmattson! It works now...
It is strange!
I successfully created a esxi 5.5 in a virtualbox which is running on my Ubuntu Laptop, however, It failed while I tried to do the same thing in the Virtualbox on CentOS6.6...
The exact same PSOD I got. What else?
I suspect that the issue is an unimplemented MSR in VirtualBox--one that should be available on the CPU in your CentOS machine, but not on the CPU in your Ubuntu machine.
If that's the case, the two solutions that come to mind are (1) configuring VirtualBox to ignore unimplemented MSRs or (2) configuring VirtualBox to report a different CPU model, that doesn't support the MSR in question. Based on the PSOD, I'm guessing that the MSR is 130H, CPUID1_FEATURE_MASK, described in http://www.intel.com/content/dam/www/public/us/en/documents/application-notes/virtualization-technology-flexmigration-application-note.pdf.
If you boot ESXi with the additional vmkernel option "vmbASLR=FALSE" and post an image of the PSOD, I can confirm my guess.
Thank you very much, Jmattson!
Since I am in the vacation of the Chinese New Year holiday, I will do a try as soon as I get back to work and let you know about the result.
Thanks again, and all best wishes!
As I suspected, we are trying to read MSR 130H, and VirtualBox is raising a #GP exception on this access. This is a bug in VirtualBox.
There may be a way to have VirtualBox report a different virtual CPU model. Changing the CPU model to one that doesn't implement MSR 130H is one way to work around this problem.
Alternatively, it may be possible to configure VirtualBox to ignore unimplemented MSRs. That would be another way to work around this problem.
OK, Thanks Jmattson! I will give it a try...
I am facing exactly same problem but I don't know how to configure VirtualBox to ignore unimplemented MSRs. So do you have any idea about it?
Thanks in advance
Sorry; I don't.