Proxmox 3.4 migrate all vm-s (HA)

elderone

New Member
Dec 5, 2014
2
0
1
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
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 can confirm this behavior: "Migrate all VMs" only migrates NON-HA VMs and Templates.
Furthermore the "Stop all" and "Start all" ignores any HA enabled VMs.

Caspar
 
It's a bug.

(I have done this feature, but don't have tested it with HA)

Hi Spirit,

Thank you for implementing this great feature! Hopefully you will be able to test this with HA and submit a patch to be able to migrate all HA enabled VM's too. Thanks again!
 
It would also be very nice if this feature worked with a pve user (non root@pam). For now this only works as root@pam
 
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.

Hi there,
I've installed for testings a v4.0 cluster, and it seems that this bug still exists : "Migrate all" only migrate non-HA VM (just register a task "migrate all", and nothing appends). Removing a VM from HA ressources is enough to see it migrating with this feature.
Have you found any solution ? Thanks.
 
Hi Spirit,
a little UP to know if you know how, and when, this can be resolved ?
Thanks in advance.
 
If you use a private network for your PVE traffic, you can add "migration_unsecure: 1" to /etc/pve/datacenter.cfg to solve this issue (only works for PVE 4.2 and above).
 
Last edited:
Ah, not sure to see the link between migration_unsecure and the "migrate all", but I'll try. I reinstall with fresh 4.2 and tell if it works.
Thanks !
 
Okay :) 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).
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!