I have noticed recently with most all of my clusters that when adding a fresh VM to HA there seem to be some issues. Once I hit activate within a few seconds the VM get's started on the 2nd node, it also is still left running on the 1st node. This is obviously not a good thing at all, what could be causing this? I figured there was things in place to prevent something like this from happening. I have found to get around this I have to do a live migration of the VM before adding it to HA. If I do this, it won't get started on the other node when adding to HA.
Issues when adding VM to HA
- Thread starter adamb
- Start date
Make sure you stop the VM before adding it to HA.
see: http://pve.proxmox.com/wiki/High_Availability_Cluster
see: http://pve.proxmox.com/wiki/High_Availability_Cluster