If so, then please ensure that you don’t have duplicate entries in the configuration file or your VM will fail to boot and produce the “Dictionary Problem” error. VDX file may already have an entry for vhv.enable. You should check the Virtually Ghetto blog for a neat post that outlines a whole bunch of undocumented.
vhv.enable = “TRUE”: This option enables nested virtualization. mce.enable = “TRUE”: This option enables Machine Check Exception (MCE), which enable the Windows Server 2012 VM to report CPU hardware issues. 0 = “FALSE”: This option tricks the Windows Server 2012 into “thinking” it is not running in a virtualized instance. I’ve given you a picture of my configuration file in the following figure. VMware configuration files can be opened with any text editor. VDX configuration file to match the following screenshot. You can find the working directory by navigating to the Options page in the Virtual Machine Settings dialog box and checking the Working directory field.Īdd the following three new entries to the. VDX configuration file from the VM’s working directory. In the Virtual Machine Settings dialog box, enable the Virtualization engine options as shown in the following figure. 
We will need to make two tweaks to the VM configuration in order to (fully) support Hyper-V Server: Open VMware Workstation and create a new VM by using the Windows Server 2012 template.
We’ll then demonstrate that nested virtualization works by deploying a virtual machine (VMs) inside the “outer” VM.
Windows 8 vmware workstation 10 install#
Our goal here is to install and run the Hyper-V server role in an already virtualized instance of Windows Server 2012.
0 kommentar(er)
