Thanks to a reader of the blog and another friend of mine who is sticking closer to the pfsense topic than me, I got a hint about the latest snapshot of pfsense which now has the Hyper-V integration services built in.
You can get an overview of the BSD Integration Services (BIS) at the official FreeBSD wiki.
Now I have a better view and I can see that one other cluster have the described problem.
With VMM you can get the message if you try to move, start up a VM:
Error (12711) VMM cannot complete the WMI operation on the server (hyper-v-03.contoso.com) because of an error: [MSCluster_Resource.Name="SCVMM SOF-Prev-02"] […] The requested operation can not be completed because a resource has locked status (0x1748) […]
Failover Cluster Manager will say “The resource $VM is locked.”
From roughly around 70 VMs almost a third can’t be moved, started up or something else.
Really painful is the fact that you can’t do anything with the Hyper-V Host itself.
Trying to get ’em in paused mode for example.
Dynamic Optimizing is getting crazy as well. 😉
Applying the Hotfix seems to be working.
I struggled with a Live Backup issue on Ubuntu 2014 LTS a while ago as ralish from Stockholm DevOps describes here.
The problem was a broken installer meta package and ends up in a missing kvp deamon if you tried to install it on Ubuntu.
This daemon is used to interact between Host and VM to get a consistent backup state during snapshot creation on the Hyper-V Host.
So at the end, Backups without kvp can be risky due to a service interruption of the VM workload(s).
A screenshot from the DPM 2012 R2 Backup console shows the offline state.
In the meantime, the bug got fixed, Live Backups without service interruption can be taken, the sun is shining again and so it’s time to wrap some things up and give you a short overview about Hyper-V and common Linux Distributions.
In some cases it’s good to replicate a virtual machine in and outside a clustered system.
I tried this the very first time but after setting up the replication broker role in the failover cluster manager I got an error.
After researching a while whats going on I got a solution.
The Cluster Role couldn’t write a computer object.
Usually you set up an OU where the Hyper-V Servers belongs to and there is the Cluster Role (actually a computer account created during the installation) as well.
The Cluster (machine account) has to get writable access to this OU and after that… The Replica Broker is working. 🙂