Windows Server 2012 R2
we initially have 3 nodes of Hyper-V hosts and were moving VMs left and right (between nodes) without any difficulties. the other day, due to the availability of a blade (an Oracle blade) we made it into a Hyper-V host and added to the list of Hyper-V hosts available from the FailOver Cluster Manager.
so we created a new VM in that new host (let's call it hyper-4), installed Windows and stuff. the VM booted fine and is accessible on the network. now here comes the tricky part, existing VMs available in other hosts we cannot move into hyper-4. however, VMs created/started in hyper-4 we can move to any available hosts.
so what we do for the meantime if we want all VMs to be able to move effortlessly between hosts is we shutdown a VM, move it to hyper-4, bring it up in hyper-4, after that the VM can be move to any available hosts.
what i don't get is why the need to start a VM in hyper-4 first before said VM can be moved to any Hyper-V hosts?