Changes between Initial Version and Version 1 of Ticket #12049, comment 6
- Timestamp:
- Oct 21, 2013 8:23:05 AM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #12049, comment 6
initial v1 1 That forum thread is only talking about VT-x and '''not''' AMD-V. There is no such MSR on AMD systems. On AMD CPUs, the MSR in question would be 0xc0010114. Particularly, bit 4 of that MSR must be clear (zero) for AMD-V to be enabled. If the BIOS sets this bit, then according to the AMD-spec. AMD-V cannot be enabled which is what VirtualBox will report as "VERR_SVM_DISABLED".1 That forum thread is only talking about VT-x and '''not''' AMD-V. There is no such MSR on AMD systems. On AMD CPUs, the MSR in question would be 0xc0010114. Particularly, bit 4 of that MSR must be clear (zero) for AMD-V to be enabled. If the BIOS sets this bit, then according to the AMD-spec. AMD-V cannot be enabled which is what !VirtualBox will report as "VERR_SVM_DISABLED". 2 2 3 3 Since the log file shows AMD-V is enabled, perhaps it is a typo/bug in the Support driver code that differs from the VM-initialization code (which was what it was for VT-x) but I checke and as far as I can see that is not the case. … … 37 37 }}} 38 38 39 This will then expose 64-bit CPU features to the guest. VirtualBox 4.3 is much more strict regarding the distinction between 32 and 64-bit guests.39 This will then expose 64-bit CPU features to the guest. !VirtualBox 4.3 is much more strict regarding the distinction between 32 and 64-bit guests.
