By setting your starting memory at 512 MB and enabling Dynamic Memory, machines will request memory as needed and will release it when no longer needed.ĭynamic memory is so efficient that I can run 3 VMs on my Surface Pro. Both Server 2012 and Windows 8 can “run” with 512 MB of RAM. On the next screen, you can configure the virtual memory. Because you are likely creating a test domain, you might name your first VM DC-01 (for domain control 1).
In the Action pane, select New and Virtual Machine. If needed, you can download trial copies from TechNet by using the two previous links. If you want any clients, you’ll also need a copy of Windows 8.1. Time to create our first VM! You will need a copy of Windows Server 2012. You will lose your network connection for a few seconds. Press Yes to the Apply Networking Changes prompt. Give your switch a name (such as Internal Network) and press OK. Select Internal and then Create the Virtual Switch. To create your switch, select Virtual Switch Manager from the Action pane. This virtual switch will let your Hyper-V machines talk with each other and their Hyper-V host (your Windows 8 machine). Your first step is to create a new Virtual Switch. If you are determined to use the command line, you can use DISM: Dism /online /enable-feature /featurename:Microsoft-Hyper-V -AllĪfter restarting, you’ll have two new Start Screen shortcuts: Hyper-V Virtual Machine Connection and Hyper-V Manager. Apparently, that cmdlet is coded for a Server OS. When running Install-WindowsFeature -Name Hyper-V on a client, you’ll get a nice error message. This will install the Hyper-V platform, Hyper-V Manager, the Hyper-V PowerShell module, and a few other tools.įor all of your PowerShell junkies out there, you will have to use the GUI method above. Once populated, scroll to the Hyper-V section and select it. If you haven’t removed it from your WINX menu, you can easily access it there. Even with a 64-bit OS, you’ll still be able to run VMs that are 32-bit. To run Hyper-V on the client, you must run either Windows 8 Professional or Windows 8 Enterprise and it must be the 64-bit version of that OS. For kicks, you could always see if a BIOS upgrade would make those features available to your system. If DEP or SLAT is set to NO, you are probably out of luck and will need a new CPU. If the Virtualization in Firmware or VM Monitor Mode is set to NO, check your BIOS. At the very bottom of the output, you should see a section named Hyper-V Requirements. The easiest way to check your CPU is to launch a command prompt and type systeminfo.
0 kommentar(er)
