A while back I changed our virtualization platform from VirtualIron to MS Hyper-V and that caused all network adapters to disappear on my VMs. Hyper-V installed its own. So when i tried to set fixed IP addresses to new adapters I got the following message: “The IP address XXX.XXX.XXX.XXX you have entered for this network adapter is already assigned…”
I thought the best way to resolve this issue was to remove the source of the problem (in this case these old VirtualIron network adapters), which is a bit hard to do if you can’t see these adapters. After digging around I found a nice MS KB article 269155, which helped me to reveal and remove those non present hidden devices.
Here’s what i did to reveal non present hidden devices.
- Click Start, click Run, type cmd.exe, and then press ENTER.
- Type set devmgr_show_nonpresent_devices=1, and then press ENTER.
- Type Start devmgmt.msc, and then press ENTER.
- Click View, and then click Show Hidden Devices.
- Expand the Network Adapters tree.
- Right-click the dimmed network adapter, and then click Uninstall.
Source: MS KB
Virtual Machine Reserve (percentage) – this value says how much CPU is kept aside for the running Virtual Machine.
Percent of total system resources – this is a precent of a Virtual Machine processor time, that is measured by how many processors are assigned to the virtual machine
Virtual Machine Limit (percentage) – this is a percent of CPU that the running Virtual Machine is not allowed to go over the top of
Percent of total system resources – this is percent of a VM processor time, that is measured by how many processors are assigned to the physical computer
Relative Weight – this is used to decide how CPU is distributed. (Basically a virtual machine with the higher weight (say 500) will get twice the CPU time as a virtual machine with a weight lower weight (say 400).
Basically on a 1 CPU and 4 Core computer you can run 40 1 CPU Virtual Machines if their reserve is 10%.
Source: MS TechNet Forums.
This is an interesting little Hyper-V utility. HVRemote helps you to reduce manual configuration, you can use HVRemote to diagnose common configuration errors and configure all combinations of workgroup and domain joined clients and servers.
- Windows Server 2008 SP1 with Hyper-V RTM update applied (KB950050), Core & Full installations
- Windows Server 2008 SP2, Core & Full installations
- Microsoft Hyper-V Server 2008 SP1 (already contains Hyper-V RTM update)
- Microsoft Hyper-V Server 2008 SP2
- Windows Server 2008 R2, Core & Full installations
- Microsoft Hyper-V Server 2008 R2
- Windows Vista Business, Enterprise and Ultimate x86 & x64, SP1 and SP2, with KB952627 applied
- Windows 7 Professional, Enterprise and Ultimate x86 & x64 with RSAT installed and Hyper-V tools feature enabled
- Windows Server 2008 SP1 with Hyper-V RTM update applied (KB950050), x86 and x64
- Windows Server 2008 SP2 x86 and x64
- Windows Server 2008 R2
You can download it from here, the same link will also give you an overview of commands you can use.
Yesterday I upgraded my MS Windows Server 2003 R2 with Virtual Server 2005 R2 (x64) machine to Windows Server 2008 Server Core /w Hyper-V (x64). Everything went smoothly, the installation, joining with domain and installing MS Firefront Client Security. The problems started when I was trying to create new machines to my Hyper-V server. I did not bother with migrating from old vmc files, so I just created a new machines and added the hard disks later. When I was trying to create my first machine, to my surprise I got an error. It should have been just follow the wizard and press finish thing. but instead I passed all the needed steps, name and location, the amount of memory, network settings, hard disk settings and finally the finish button but instead of getting a nice confirmation that virtual machine was created successfully I got this error:
The server encountered an error while configuring memory on the New Virtual Machine. Wizard Failed in rolling back the created virtual machine. Please delete it manually afterwards.
Failed to add device ‘Microsoft Synthetic Ethernet Port’
The Virtual Machines configuration GUID at ‘C:\Program Data\Microsoft\Windows\Hyper-V’ is no longer accessible: The requested operation cannot be performed on a file with a user-mapped section open. (0x800704C8)
I searched for this error on Google and it looks like this only happens when you have on your Windows Server 2008 Server Server Core /w Hyper-V installed Forefront Client Security. To fix it you need to download a patch. I suggest you to do it manually without using automatic windows update. You can get the patch from here. Just follow these instructions to download it:
1. Go to Microsoft Update Catalog Web site.
2. Type 952265 in the Search box, and then click Search.
3. Click Add to add the hotfix to the basket.
4. Near the search bar at the top, click the view basket link.
5. Click Download.
6. Click Browse, specify the folder to which you want to download the hotfix, and then click OK.
7. Click Continue, and then click I Accept to accept the Microsoft Software License Terms. The hotfix starts to download.
8. Wait until the hotfix is downloaded to the specified location, and then click Close.
9. Find the patch most suitable to your needs (from the catalogue you downloaded it), copy the patch to your Server Core and install it. After that everything should start working like a charm.
Few posts ago I wrote about Remote Server Administration Tools, but there was one thing missing from that package, remote management console for Hyper-V. Now Microsoft has released Hyper-V Remote Management console for Windows Vista here are the links:
PS! This should work under Windows 7 as well.
I would like to share my experiences installing Hyper-V on Windows Server 2008 Server Core. First you need a hardware that will support it. Then you should install the Windows Server 2008 Server Core on that hardware. When you are choosing server settings remember you have to install the OS using default language settings (EN-US). After the OS is installed take these steps:
* Change the computer name (before joining a domain):
netdom renamecomputer %computername% /NewName:newComputerName
* Check the IPv4 interface idx:
netsh interface ipv4 show interfaces
* Change the IPv4 address:
netsh interface ipv4 set address name=”IDx” source=static address=StaticIP mask=SubnetMask gateway=DefaultGateway
* Add the IPv4 DNS server address:
netsh interface ipv4 set dnsserver name=”IDx” source=static address=IPAddress
* Add the IPv4 WINS server address:
netsh interface ipv4 set winsserver name=”IDx” source=static address=IPAddress
* Join a domain:
netdom join %ComputerName% /domain:DomainName /userd:domain\user /passwordd:*
* Add a domain user to the local administrators group (if you need):
Net localgroup administrators /add Domain\UserName
* Enable Remote Desktop:
Cscript %WinDir%\System32\Scregedit.wsf /ar 0
Cscript %WinDir%\System32\Scregedit.wsf /cs 0
* Activate Windows:
Cscript %WinDir%\System32\slmgr.vbs –ato
* Change Windows Key (If activation failed, and then reactivate):
Cscript %WindDir%\System32\slmgr.vbs –ipk NewKey
* Reboot Windows:
Shutdown /r /t 0
When the server comes up you are ready to install the Hyper-V role. Use these commands:
* bcdedit /set hypervisorlaunchtype auto (so you don’t have to do 2 reboots)
* start /w ocsetup Microsoft-Hyper-V (after this is done reboot again)
After the server comes up verify that all hyper-v related services are up and running using net start to list running services. On my next post I’ll write down some general commands how to enable some general firewall rules in Windows Server 2008 Server Core.
Here is the link the the Microsoft Technet Step-by-Step guide about how to install Server Core.