Many thanks!
Results:
Converted to a binary switch list: 110100000001
Also:
Converted to a binary switch list: 000000001000
(!) This seems to indicate that "
Bit 3" is set.
From article: viewtopic.php?p=176873
Checking whether hardware virtualization is permanently (in current session) disabled
For AMD CPU to check whether you can use hardware virtualization, i.e. it wasn't blocked by BIOS, etc. you have to look at SVME_DISABLE bit (4th, counting from 0) in VM_CR (MSR 0xC0010114).
Per the AMD64 Architecture Manual, vol 2:
LOCK—Bit 3. When this bit is set, writes to LOCK and SVMDIS are silently ignored. When this bit is clear, VM_CR bits 3 and 4 can be written. Once set, LOCK can only be cleared using the SVM_KEY MSR (See Section 15.31.) This bit is not affected by INIT or SKINIT.
SVMDIS—Bit 4. When this bit is set, writes to EFER treat the SVME bit as MBZ. When this bit isclear, EFER.SVME can be written normally. This bit does not prevent CPUID from reporting that SVM is available. Setting SVMDIS while EFER.SVME is 1 generates a #GP fault, regardless of the current state of VM_CR.LOCK. This bit is not affected by SKINIT. It is cleared by INIT when LOCK is cleared to 0; otherwise, it is not affected.
From the reference to Section 15.31 above for LOCK bit:
15.31.1 SVM_KEY MSR (C001_0118h)
The write-only SVM_KEY MSR is used to create a password-protected mechanism to clear VM_CR.LOCK.
When VM_CR.LOCK is zero, writes to SVM_KEY MSR set the 64-bit SVM Key value.
When VM_CR.LOCK is one, writes to SVM_KEY MSR compare the written value to the SVM Key value; if the values match and are non-zero, the VM_CR.LOCK bit is cleared.
If the values mismatch or the SVM Key value is zero, the write to SVM_KEY is ignored, and VM_CR.LOCK is unmodified.
Software should read VM_CR.LOCK after writing SVM_KEY to determine whether the unlock succeeded.
If SVM Key is zero when VM_CR.LOCK is one, VM_CR.LOCK can only be cleared by a processor reset.
To preserve the security of the SVM key, reading the SVM_KEY MSR always returns zero.
So, I have more information, but the implications of these bits on my situation remain clear as mud.
Still, if I get this correctly, "Bit 3" could be a problem? If so, I'd need to clear it...probably by resetting the processor? By powering down for a 1 min+ period?
Let me know your thoughts.
Doch