Hi,
seems to me that new feature on Proxmox 3.4 "Migrate all VMs" does not work on HA enabled virtual machines.
All VMs without HA migrate nicely witout any error, but migrating task on GUI does not even list HA enabled VMs.
I can still migrate HA enabled hosts one by one, so no error there.
Any sugestions?
Package versions
	
	
	
		
				
			seems to me that new feature on Proxmox 3.4 "Migrate all VMs" does not work on HA enabled virtual machines.
All VMs without HA migrate nicely witout any error, but migrating task on GUI does not even list HA enabled VMs.
I can still migrate HA enabled hosts one by one, so no error there.
Any sugestions?
Package versions
		Code:
	
	proxmox-ve-2.6.32: 3.3-147 (running kernel: 3.10.0-5-pve) 
pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e) 
pve-kernel-2.6.32-32-pve: 2.6.32-136 
pve-kernel-3.10.0-5-pve: 3.10.0-19 
pve-kernel-2.6.32-33-pve: 2.6.32-138 
pve-kernel-2.6.32-37-pve: 2.6.32-147 
pve-kernel-2.6.32-34-pve: 2.6.32-140 
lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 
corosync-pve: 1.4.7-1 
openais-pve: 1.1.4-3 
libqb0: 0.11.1-2 
redhat-cluster-pve: 3.2.0-2 
resource-agents-pve: 3.9.2-4 
fence-agents-pve: 4.0.10-2 
pve-cluster: 3.0-16 
qemu-server: 3.3-20 
pve-firmware: 1.1-3 
libpve-common-perl: 3.0-24 
libpve-access-control: 3.0-16 
libpve-storage-perl: 3.0-31 
pve-libspice-server1: 0.12.4-3 
vncterm: 1.1-8 vzctl: 4.0-1pve6 
vzprocps: 2.0.11-2 
vzquota: 3.1-2 
pve-qemu-kvm: 2.1-12 
ksm-control-daemon: 1.1-1 
glusterfs-client: 3.5.2-1 
	 
	 
 
		 I know for 100% sure it works with 4.2 when you change to migration unsecure. Also I know for sure it doesn't work with 4.1 and older (tested it this morning with a 4.1-22 cluster, didn't work, upgraded to 4.2-5 and it did work).
 I know for 100% sure it works with 4.2 when you change to migration unsecure. Also I know for sure it doesn't work with 4.1 and older (tested it this morning with a 4.1-22 cluster, didn't work, upgraded to 4.2-5 and it did work).