Question: How many virtual processors (virtual CPU’s) are officially supported by Microsoft for a guest virtual machine (VM) running on Hyper-V? Answer: You may be thinking the answer to this question is four since that is the number you can assign to any guest VM, but the answer like many others in IT is that it depends. It depends on what guest operating system you’re running. Windows Server 2003, Windows Vista, and Windows XP SP3 all officially support a maximum of two virtualized processors when installed as a guest VM running on Hyper-V.
Hyper-V Server 2008
While building a Hyper-V server this week, I decided to rename the network interfaces to something that would make identifying the iSCSI connections a little easier. Since the server was installed with only the core (no GUI) installation of Windows Server 2008 R2, the process had to be performed from the command line. The network interface is also commonly referred to by other names such as network adapter or network connection.
Problem: You receive an error Virtual Disk Manager “The RPC server is unavailable” when attempting to remotely manage Hyper-V Server 2008 or Windows Server 2008 Core Installation: Solution: Run the following command on the client and on the server: netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes You have the option of using the Server Configuration menu on the server side if your using Hyper-V Server 2008. Select option 4, Configure Remote Management:
Problem: You’ve closed your command prompt window on Hyper-V Server 2008 or Windows Server 2008 Core Installation and need to re-open it: Solution: Start Windows Task Manager by pressing Ctrl & Shift & Esc. Click File>New Task: Type cmd.exe and click ok: You now have a new command prompt window: µ