You’ve loaded SP1 on your Windows Server 2008 R2 Hyper-V virtualization host server and you’re ready to begin using Dynamic Memory for your virtualization guest machines (VM’s). Listed below is the minimum amount of changes required for your virtualization guest machines (VM’s) to be able to use dynamic memory: Set the VM to use Dynamic Memory by specifying a minimum and maximum amount of memory. The VM will need to be shutdown in order to change this setting and the settings will only show up if the computer running Hyper-V manager has SP1 installed.
Hyper-V Server 2008 R2
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.
I recently ran into an issue where I couldn’t start any additional virtual machines on a Hyper-V server that was running Windows Server 2008 R2 Enterprise Edition - Core Installation (no GUI). After a little research, I determined that the operating system had created a pagefile of over 100 gigabytes in size which was using up the majority of the DAS in the server. The server has 96GB of RAM which is the reason why the operating system automatically configured such a large pagefile.
There are multiple reasons why you might want to run the Dell System E-Support Tool (DSET) on your Dell PowerEdge server. It could be because Dell Support has requested it or you’re trying to diagnose a problem or you simply want to know what version of BIOS your server is running without having to reboot it. This tool is especially useful when it comes to Windows Server 2008 R2 core installation since many other utilities will not run on server core.
I recommend following the instructions in my Rename a Network Interface from the Command Line so you can easily distinguish the difference in the network interfaces. Once the network interfaces are renamed, they should look similar to the ones in this image: If you attempt to ping your SAN at this point with a 8972 byte ping (9000 bytes minus a 20 byte IP header and a 8 byte ICMP header), you’ll receive a message stating “Packet needs to be fragmented but DF set.
I’ve written a few other blogs about iSCSI and Multipath I/O on Windows Servers, but this one focuses on installing the EqualLogic Host Integration Tool (HIT) Kit on Windows Server 2008 R2 Core (no GUI). If you are using an EqualLogic SAN, I recommend installing the HIT kit before doing any of the iSCSI or Multipath I/O configuration. It will make your life a lot easier. It’s also not a problem to install the HIT kit after you’ve done some or all of the configuration, just keep in mind there will be a few dialog boxes in this blog that you won’t see such as the HIT kit wanting to install the Multipath I/O feature.
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.
To determine if the Multipath I/O feature has been installed, login to your core server and run oclist.exe: If you already know the name of the feature or role your looking for, you can save yourself some time by piping the output of the oclist.exe command to the find.exe command. The /I parameter makes the search case insensitive. To install the MultipathI/O feature, run “start/w ocsetup.exe MultipathIo”. The name of the feature is case sensitive.
One of my customers contacted me today with an issue where the time on all of their servers was off by about 8 minutes or so. My first thought was “which Active Directory domain controller is their authoritative time server?” and “I’ll update the time on it manually and then set it up to synchronize from an Internet time server”. By default, the authoritative time server for your organization is the server that holds the PDC Emulator FSMO role in the forest root domain.
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 the Hyper-V Server 2008 R2 Server Configuration menu and need to re-open it: Solution: The command to re-open this window has changed with the R2 release. The new command is sconfig.cmd, with the non-R2 version, the command was hvconfig.cmd. Start Windows Task Manager by pressing Ctrl & Shift & Esc. Click File>New Task: Type cmd.exe /k C:\Windows\system32\sconfig.cmd and click ok: You now have a new Server Configuration window:
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: µ