today I want to share a challenge and step-by-step solution I had with one quite specific setup.
Following the scenario:
I have two Windows Server 2012 R2 Hyper-V Clusters, in different domains but connected to the same storage.
Now I needed to migrate 20 Virtual Machines from Cluster A to Cluster B.
Hyper-V has the “Copy Cluster Role” Wizard which is basically doing this kind of migration, but it’s not working cross-domain. Therefore I had so search another solution.
Here the process of moving the VMs:
- Using the Failover Cluster Manager, move all VMs which should be migrated to the same CSV and make sure no other VMs are on that disk.
- Shut down the Virtual Machines
- Take the CSV offline
- Unexport/Unpresent the VLUN from Cluster A
- Optional: Rename the VLUN in the storage system (my VLUNs are named according to the cluster they belong to)
- Export/Present the VLUN to Cluster B
- Take the disk online and add it as Cluster Shared Volume to the Failover Cluster
- Optional: Rename the disk in Disk Management / Failover Cluster Manager
- Import the VMs (register in-place) using the Hyper-V Manager
- Configure Cluster Role in Failover Cluster Manager.
This gives you the option to make all of the imported VMs HA in bulk
- Start your Virtual Machines and test the network connectivity and Live/Quick migration
Now comes the cleanup on the source cluster:
- Remove VMs from the Cluster
- Remove CSV from Cluster Shared Volumes
- Remove CSV from Cluster Disks
The migration time was around 30min for all of the above, whereas the most time was needed for the import of the VMs.
Sorry folks… I left my blog quite abandoned for the last year, now I promise to get it running again.
Next post in some minutes!
Recently one of our clustered Hyper-V Hosts (with Windows Server 2012 Datacenter installed) was throwing a BSOD in the moment we tried to delete an ISO file from a CSV Volume.
After investigation with Microsoft Support, we found out that Quest Change Auditor (like McAfee Antivirus) is installing a Filter Driver. This Filter Driver is being used in order to track File Access.
This Filter Driver in combination with the CSVFS (csvfs.sys) is causing the BlueScreen.
After we uninstalled ChangeAuditor, the problem was solved.
Yesterday, directly after the new OS Version was available, I started the download.
Unfortunately it took some time, as Microsoft Servers seemed to be a little bit overloaded.
Anyway, after half a day I had the update on ready for install on my Laptop and my Tablet.
First I have to say, my Laptop is was running Windows 8 Enterprise, so the update procedure was a little different:
- Download the ISO image from the Volume Licensing Portal
- Suspend Bitlocker Drive Encryption for Partition C:\
- Start the installation within Windows (I used a USB-Stick*, as I was not sure if it would work in case I just mounted the ISO)
- I was going through the Wizard, which told me that all my Apps will be lost (ok, so my Laptop would be faster)
- After pressing the finish button, it took like 30min to install Windows 8.1
- My settings and files (Domain Account, Windows Account, Personal Files and even installed security certificates) have been preserved.
- Now that the upgrade was done, I reinstalled Office, Antivirus, etc. and resumed the Bitlocker Drive Encryption.
- Easy and smooth :-)
* The Windows 7 USB DVD Download Tool is available for free and still working with Windows 8.1
With my Tablet (running the 32bit Version) the upgrade was a little easier:
- After opening the Store, I selected the Windows 8.1 update
- The installation started immediately after the download finished
- After 30min, I got the screens with the usual questions: Agree Terms of Service, Allow Location, etc.
- With this installation, all settings and files have been preserved (even Desktop Apps like iTunes)
- Did I say before easy and smooth? It was a lie… this installation was easy and smooth!
Enjoy upgrading folks!
… finally an easy way to migrate Virtual Machines accross different versions of Windows Server Hyper-V.
The first step towards this was done by Microsoft when giving us the possibility to do a Shared-Nothing Live Migration.
Introducing Windows Server 2012 R2, this feature can be used in order to migrate Virtual Machines from a Windows Server 2012 Hyper-V Host to a Host running Windows Server 2012 R2.
Of course this is not only possible for single Hosts, but also for migrations between Clusters.
Now you don’t have to worry about a maintenance window for migrating your Virtual Machines to a new system, you can do a Cross-Version Live Migration :-)
Note: It’s not supported to perform a migration from 2012 R2 to 2012.
Think about the installation of a Virtual Machine in one of your Windows Server 2008 R2 / 2012 Hosts. The mouse is not being captured, you could only copy and paste text from the Host to the Virtual machine (via the drop down of the vmconnect window, not directly).
To come around things like that, one option was to use a Remote Desktop Connection. But this only works after finishing the initial installation of the VM and not with all Client Operating Systems.
In Windows Server 2012 R2 and Windows 8.1 Hyper-V, Microsoft implemented something new:
Enhanced VM Interaction
Enhanced VM Interaction is based on the Remote Desktop Protocol and allows you to use a lot of features, even if the Client Operating System is not yet installed or if the Virtual Machine has no network connectivity:
- Smart Card, Folder, Disk and USB redirection
- Audio redirection
- Copy and Paste of files and folders (in both directions [VM<=>Host])
Note that the redirection is session based. Therefore it can’t be used for licensing dongles, etc..
Enhanced VM Interaction can be enabled for each Hyper-V Host in the Hyper-V Manager. By default it is disabled in Windows Server 2012 R2 and enabled in Windows 8.1.
I am running several virtual machines on my laptop using Client Hyper-V. I don’t use them so much, but a few weeks ago I had to recognize that after starting my computer they are always shown as “off-critical”.
My search in the web only gave me results regarding Virtual Machines located on USB-Storage, which was actually leading me to the solution of my problem:
If VMs are located on a USB-Drive which is not connected during computer start-up, they will be shown in Hyper-V Manager as “off-critical”, because the VM Config files cannot be loaded.
This can be resolved by simply connecting the USB and restarting the Virtual Machine Management Service.
My VMs are located on a local partition. Now you would maybe ask why I think that this is the same problem, I will tell you:
The partition with the Virtual Machines is BitLocker protected.
So if I start my computer, the C Drive is being unlocked after typing my PIN and the TPM verification. The D Drive instead, will only be unlocked after the system start-up.
Somewhere in between this, the Virtual Machine Management Service is starting and looking for the XML files. As the partition is still encrypted, it cannot access the VM Config Files.
How to resolve?
I changed the Hyper-V Virtual Machine Management Service Start-Up Type to Automatic (Delayed Start).
With this setting my Virtual Machines are off (like supposed to), but not off-critical after I start my Laptop :-)