Jump to content

deadsmiley

T|I Elite Legacy
  • Posts

    201
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by deadsmiley

  1. deadsmiley

    Clevo P370SM3

    I think the control you are looking for is IA32_FEATURE_CONTROL on page 5. 23.7 ENABLING AND ENTERING VMX OPERATION Before system software can enter VMX operation, it enables VMX by setting CR4.VMXE[bit 13] = 1. VMX operation is then entered by executing the VMXON instruction. VMXON causes an invalid-opcode exception (#UD) if executed with CR4.VMXE = 0. Once in VMX operation, it is not possible to clear CR4.VMXE (see Section 23.8). System soft- ware leaves VMX operation by executing the VMXOFF instruction. CR4.VMXE can be cleared outside of VMX opera- tion after executing of VMXOFF. VMXON is also controlled by the IA32_FEATURE_CONTROL MSR (MSR address 3AH). This MSR is cleared to zero when a logical processor is reset. The relevant bits of the MSR are: • Bit 0 is the lock bit. If this bit is clear, VMXON causes a general-protection exception. If the lock bit is set, WRMSR to this MSR causes a general-protection exception; the MSR cannot be modified until a power-up reset condition. System BIOS can use this bit to provide a setup option for BIOS to disable support for VMX. To enable VMX support in a platform, BIOS must set bit 1, bit 2, or both (see below), as well as the lock bit. • Bit 1 enables VMXON in SMX operation. If this bit is clear, execution of VMXON in SMX operation causes a general-protection exception. Attempts to set this bit on logical processors that do not support both VMX operation (see Section 23.6) and SMX operation (see Chapter 6, “Safer Mode Extensions Reference,” in Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 2B) cause general-protection exceptions. • Bit 2 enables VMXON outside SMX operation. If this bit is clear, execution of VMXON outside SMX operation causes a general-protection exception. Attempts to set this bit on logical processors that do not support VMX operation (see Section 23.6) cause general-protection exceptions.
  2. deadsmiley

    Clevo P370SM3

    I think the root cause of why your mod didn't work is because you were flipping the wrong bits. You should be looking at IA32_FEATURE_CONTROL as described on this page. Activating the Intel VT Virtualization Feature - Thomas Krenn Wiki This got me interested in sharing your quest. I must freely admit that I have never attempted to alter a BIOS. I don't even know where to start, but I read tech manuals every day in my line of work. Perhaps I should start? Here is another link to enabling virtualization that I am still trying to digest. Maybe our fine friend Prema can be convinced to look into this problem for us? Can a hypervisor rootkit enable hardware-assisted virtualization when it has been disabled by the BIOS? - Information Security Stack Exchange
  3. deadsmiley

    Clevo P370SM3

    Eeewww... I would like to know the answer to this as well. I am very close to pulling the trigger on this laptop and I use VMWare quite a bit. Oh, and this is my first post to this forum.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.