Hyper-V : VHD size optimization #2

Time to revise an old post based on recent experiences with Hyper-V.
I posted on how to optimize the size of VHDs, but I'm revising that now to include step 2 below >

1) Defragment the VHD (Defraggler was better than the Windows tool)

2) Use Precompact.exe to a "zero out" i.e. overwrite with zeros available blank space. *

3) Shut down the VM and Shrink the VHD from Hyper-V.

* Precompact.exe is found in precompactor.ISO which in turn you get from the Virtual PC 2007 installation (in C:\Program Files (x86)\Microsoft Virtual PC\Virtual Machine Additions)

Link : Compacting Hyper-V files

Enabling VT (Virtualisation Technology) for Hyper-V hosts

If you forget to enable VT in the BIOS and try to install Hyper-V, this is what you get...

" Hyper-V cannot be installed

Server Manager has detected that the processor on this computer is not capable with Hyper-V. To install this role the processor must have a supported version of hardware assisted virtualization, and that feature must be turned on in the BIOS. "



The message is pretty self explanatory and I had indeed turned it on in the BIOS. What it doesnt tell you is that you need to cold boot after making BIOS changes i.e. physically turn off the server, wait a while and start the server back up!
Whlst in the BIOS, make sure 'Execute Disable' is 'Enabled' (confusing I felt).

Hyper-V VM : Removing Hidden Network Adapter!

"The IP address 10.0.20.31 you have entered for this network adapter is already assigned to another adapter 'Microsoft Virtual Machine Bus Network Adapter #2' 'Microsoft Virtual Machine Bus Network Adapter #2' is hidden from the Network Connections folder because it is not physically in the computer. If the same address is assigned to both adapters and they both become active, only one of them will use this address. This may result in incorrect system configuration. Do you want to enter a different IP address for this adapater in the list of IP addreses in the Advanced dialog box?"

By changing the virtual network on the Hyper-V host, I have managed to create a ghost network adapter in my hyper-v VM!

To see the hidden adapter >

1. launch command prompt - start > run > cmd [enter]
2. type set devmgr_show_nonpresent_devices=1 [enter]
3. type start devmgmt.msc [enter]
4. from menu bar select 'View' drop down and select 'Show hidden devices'

To remove the (now visible) adapter >

1. locate the adapter in device manager under 'network adapters'
2. right-click it and select 'uninstall device'
3. reboot

http://blog.mpecsinc.ca/2008/02/sbs-shadowprotect-some-hardware.html

Hyper-V Annoyances : Reactivation

When you move a VM across hosts, if it NICs are named differently then installing a new virtual nic in a VM is seen as a hardware change.

This in turn means that the virtual OS needs reactivation. :/

RDS - Remote Desktop Services

'Terminal Services' to be renamed to 'Remote Desktop Services' in Windows 2008 SP2.

Hyper-V to be used to deploy the VDI (Virtual Desktop Infrastructure) environment.

http://4sysops.com/archives/remote-desktop-services-windows-server-2008-r2-will-support-virtual-desktop-infrastructure-vdi/

Failed to add device Microsoft Synthetic Ethernet Port ...

Tried to start a VM from another server and got the following error.

" Failed to add device Microsoft Synthetic Ethernet Port ... "


The server has MS Forefront Client Security AV onto the server, hence need to set exclusions for the VM files

This chap found the solution...

http://joshrobi.blogspot.com/2008/06/how-to-fix-hyper-v-error-failed-to-add.html

Hyper-V : Language Setting

Note to self! : Remember to install Windows 2008 as default language (US) for Hyper-V to function.

http://www.servercare.nl/Lists/Posts/Post.aspx?ID=17

Originally blogged it here , when first playing....

Hyper-V : Installation on Windows 2008

Hyper-V : SQL Support

SQL Server 2005 is not fully supported on a virtual machine in a Windows Server 2008 Hyper-V environment. Microsoft is considering whether to provide support for SQL Server 2005 on Hyper-V virtual machines in future updates of SQL Server 2005 >

http://support.microsoft.com/kb/956893

( SQL Server 2008 is supported )

Decision time it is then, as currently building Hyper-V images...

Hyper-V : VHD size optimization

I previously blogged about compressing Hyper-V VHD images as they can 'bloat' and eat disk space. Unhappy with the results, I set about trying to squeeze one of my images more...

The following was performed with a VHD of Vista Ultimate with VS2008 & Office 2007 installed.

action	bytes
original image	40,212,793
set system restore to 1gb max, compressed vhd	14,006,618
ran windows defragmenter, compressed vhd	15,456,481
ran flexomiser defragmenter, compressed vhd	13,903,606

Well worth reviewing VHD file sizes periodically I think...
r

Hyper-V : Error after removing VM

On browsing the Hyper-V Server Manager, I noticed some errors that I had not spotted before >

The Virtual Machines configuration (guid) at 'C:\hyper-V-Path\' is no longer accessible.

For some reason, my attempts at tidying up and moving the vm image files to a new location had not been 100% successful, leaving HyperV to periodically look for the image in the old location (despite the VM working fine from it's new location).

To rectify the situation, this technet post came in rather useful.

Basically >

1 ) Navigate to C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines (if you don't see anything, unhide files and folders via tools > folder options > view > 'show hidden files & folders')

2) Locate the link file that matches the GUID number in your original message.

3) In Hyper-V, click 'Stop Service' (turns off VMMS)

4) Delete the file

5) In Hyper-V, click 'Start Service' to restart the VMMS.

Errors should no longer appear every 2 minutes now.

Note : VMMS is the 'Virtual Machine Management service' and just controls your ability to manage VMs, they continue running even when VMMS has been shut down.

Compressing Hyper-V disk images (.vhd files)

How to compress Hyper-V disk images (.vhd files) >

1) Go to Server Manager.

2) Shutdown the Virtual Machine in Hyper-V Manager.

3) Select the VM and click Settings in the right hand pane.


4) Click the hard drive and select 'Edit'.


5) Select 'Compact' (default action) and click 'finish'.

Hyper-V : Display support

I have a WSXGA (1650 x 1080) display and during my initial explorations of Hyper-V was getting quite annoyed that i couldnt install drivers for it inside my various VMs.

The maximum resolution from the MS VM drivers is 1600x1200 (UGA) but I could obviously only get to 1280x1024 (SXGA) due to the vertical pitch.

To get round this, connect via RDP. RDP seemingly lets the host handle the video hence providing full resolution.

Another reason to connect to Hyper-V Virtual Machines via RDP is USB support.

Hyper-V : USB Support

If (like me) your use of Hyper-V is for multiple environments on a development box (i.e. not production) you can RDP to your virtual machines to get round the (current) non support for external USB devices on the host.



To do so, edit the properties of your .RDP connection file.

Go to the 'Local Resources' tab.

In 'Local devices & resources' box, click 'more'.

The pop-up that then appears will allow you to select which drives/resources you want to be able to connect to remotely.

Yes, using RDP is not ideal as it takes up more resources, but if you're hardware is fast enough. you really won't notice a difference.



Update: Hyper-V via RDP also helps reach display resolutions not yet supported by Hyper-V.

Hyper-V : Networking

A great explanation - Understanding Networking with Hyper-V
http://blogs.msdn.com/virtual_pc_guy/archive/2008/01/08/understanding-networking-with-hyper-v.aspx

Hyper-V : Virtual Machine Connection

Here is the Virtual Machine Connection window, i.e. Windows 2008 Standard running virtualised on Windows 2008 Datacenter.

Hyper-V : Server Manager

A screenshot of Hyper-V Server Manager. I have created 1 virtual machine named 'HyperV-1' and have installed Windows 2008 Standard on it so far.

Hyper-V : Installation on Windows 2008

Keen to try Microsoft's new virtual server offering, Hyper-V is the first port of call on my new server. A small hiccup occurred after adding the Hyper-V role to windows 2008.

The 'Virtual Machine Management' service (aka Hyper V) failed to start and manually attempting to start it, I was greeted with 'Error 87 : The parameter is incorrect'.

Fortunately it is an easy one to get round and is fixed by changing language settings to 'English (United States)'. Go to 'Regional and Language Options' (control panel). On the 'Formats' tab select 'English (United States)' and click apply. Then go to the 'Administrative' tab (new to 2008)and use the 'Change system locale' and 'Copy to reserved accounts' buttons here to ensure the setting is applied to all profiles. I restarted the server to let it take effect and all is fine.

Given Hyper-V is still in a 'pre-release' state, i suppose I can't complain.

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2557702&SiteID=17

Hyper-V : Storage Options

Post on exposing storage to Hyper-V instances
http://blogs.technet.com/josebda/archive/2008/02/06/storage-options-for-windows-server-2008-s-hyper-v.aspx

VM Performance

You might think it is stating the bleeding obvious, but...

"Have your virus scanner exclude .vhd files in the virtual machine folder on your host."

http://www.hanselman.com/blog/VMPerformanceChecklistBeforeYouComplainThatYourVirtualMachineIsSlow.aspx

Exposing Storage to a Hyper-V VM

The various methods are explained here , on Jose Barreto's Blog >

http://blogs.technet.com/josebda/archive/2008/02/14/storage-options-for-windows-server-2008-s-hyper-v.aspx