Printable View
I am evaluating the 30-day trial of VMware Workstation 7. I virtualized Windows 7 team and have created a virtual machine in Workstation 7. However, you can run the virtual machine. I get an error message that says the time mode is deactivated and a virtual machine with a 64-bit code will not run. Is this a limitation of the Station 7 or a limitation of the trial of 30 days or more? Can someone explain what is happening?
To run 64-bit clients in the VT. BIOS must enable the host operating system
Also, if you go to VM-> Settings (processors) and clearly set the preferred way "Intel VT-x or AMD-V", you acquire a mistake note more informative.
I looked in the BIOS of my real computer (host), but we could not find anything that resembles the letters VT. Can you explain a bit more detail what I'm looking for.
I burned iso to CD and a DVD. But I could not start any of them and the boot process continues until the start of Windows 7. To verify that the BIOS to select the CD player to boot first I installed a WinPE disk in the CD player and start right away. So for some reason I cannot boot the ts.iso.
Obtaining Detailed Diagnostics-
To verify that the VT-x is enabled and locked in each core, download the attached ISO, burn it to CD and boot the machine from the CD. make a note of that the physical machine should boot from this CD image. Do not do any good to start a virtual machine from that image, because VMware does not virtualized product VT-x.
Code:CPU <n>: This core does not support long mode
CPU <n>: This core does not support VT
CPU <n>: Feature control MSR is unlocked!
CPU <n>: VT is disabled in the feature control MSR!
CPU <n>: VT is enabled on this core.
I looked everywhere in the BIOS of virtualization technology and could not find it. I think I'm at an impasse.
This is by now the evasion performance for accessible VMware hosted products (Workstation 7.x, 3.x Player, and Fusion 3.x). For earlier products, the following explanation might help if your firmware VT-x left unlocked, either in the ignition, or after hibernate or sleep. Simply add the following option in the file of the entire system configuration:
Code:Enabling VT-x if Unlocked-
If VT is activated after a power cycle, but is disabled after hybrid sleep, probable cause is the buggy firmware (BIOS / EFI). The best solution is updated firmware for your system vendor. If this is not possible, or if the most recent firmware does not resolve the trouble, you may necessitate disabling hybrid sleep. If the firmware is not closed following leaving VT hybrid sleep, present host of VMware products and lock routinely enable VT. A answer exists for older VMware products. Observe "Enabling VT-x If Unlocked"