Beware of Server 2012 R2 installation on VMM (error 0xE000100)

I just wasted a couple of hours troubleshooting this error 0xE000100 while installing Windows 2012 R2 on VMM 2012 SP1 (older version). At first I thought there was some data corruption, ended up downloading the ISO again, to no avail. Then I thought maybe you cannot install R2 on older VMM. I started googling the requirements for 2012 R2. After much googling I found out the problem. I created the VM with dynamic RAM, using the default 512MB startup and 10GB max. THAT is the problem. Check this out:

Under setup for virtual machines section, they say:

If you create a virtual machine with the minimum supported hardware parameters (1 processor core and 512 MB RAM) and then attempt to install this release on the virtual machine, Setup will fail.

Cowbanga!! Note to myself, never use dynamic RAM to install a VM’s OS!

I have used dynamic RAM on all older OSes from Windows, works fine…but with 2012 R2 it does not. I think it is best to make the switch to dynamic RAM later.

List VMs on your SC VMM 2012

Wanna find out what VM is running on which server in your SCVMM cluster? This PowerShell script does it for you! (run it on the VMM server’s Virtual machine manager Command Shell)

Get-SCVirtualMachine | Select-Object -property HostName, Name, Description | Sort-Object -Property HostName | Export-Csv .\vm-list.csv

Here is another one which you can run to find which VMs are currently running. This is useful in case you want to shut all of them down using some script.

Get-SCVirtualMachine | where {$_.StatusString -eq “Running”} | Select Name | Sort-Object -Property Name | Export-Csv .\vm-list.csv

Behavior of CSVs in Hyper-V 2012

I have a few observations about CSVs in a Hyper-V 2012 cluster:

1. Online/Offline status in Disk Management.

Take a look at the screenshot below. I was troubled by seeing the CSV offline. I thought there was a problem (not really).


Here is how the cluster works:

The CSV shows up as an online disk only on the cluster node which is managing is (or is the owner of that CSV). If you change the owner of that CSV to another node, the CSV disk will go offline on this node. However both nodes can still access the CSV via C:\ClusterStorage\vol2

2. Cannot map a drive to view CSV contents:

You cannot map a drive to C$ and try to view the contents of C:\ClusterStorage\VolX. There will NOT be any error but the contents of that directory will be blank. You can RDC to the hyper-V machine and view the contents of that directory successfully.

3. No drive letter is assigned to a CSV

The moment you add a disk to cluster storage volume, it will lose its drive letter. This is by design (normal). A CSV is supposed to be accessed via its map point under C:\ClusterStorage\VolX. This is noticeable in the screenshot above.

Hyper-V 2012 cluster installation troubleshooting

While installing a Hyper-V 2012 cluster I ran into some trouble. The cluster got installed successfully but a few things did not work properly.

Live migration problems:

Live migration does not work…well…sometimes. Sometimes it does work. So it behaves intermittently. I started a thread about it here.

CSV not visible on all nodes.

When using VMM console, the 2 CSVs I created are not available for placement of new or migrated VMs on all 3 nodes clusters in the cluster. Interestingly the CSV mount point under c:\ClusterStorage\VolumeX is visible on all nodes.

Witness disk is visible on all nodes.

Here are the steps I took towards solving the problem:

Continue reading “Hyper-V 2012 cluster installation troubleshooting”