I'am using Proxmox on 2-nodes cluster with /dev/pve/data on both nodes glued in one mirror (RAID1) with glusterfs (so "local" storage on both nodes are the same and always in sync). All works as expected, live migration is very fast, thanks for your great product, i am really happy to find it as a usefull and near-comprehensive replacement for VMware ESX!
But now i want to have some HA Cluster benefits with my very robust two-heads virtual environment. So when one of the "heads" is going down it will be nice if all of virtual machines was running on it will appeare on the head that still alive in a "shutdowned" state. So i am understand that on-line synchronisation of VM's memory is impossible, but i still need to be able to restart all VM's which crashed on one head (node), on another head.
I am experienced in shell and perl programming, so if this functionality is not realized soon, i can do it, but for this i need to understand the logic of how Proxmox works better...
For example, who can tell me, how Proxmox node knows what VMs running on the local node and what - on the remote one(s)?
Thanks!
Andrey Konovalov,
Russia
But now i want to have some HA Cluster benefits with my very robust two-heads virtual environment. So when one of the "heads" is going down it will be nice if all of virtual machines was running on it will appeare on the head that still alive in a "shutdowned" state. So i am understand that on-line synchronisation of VM's memory is impossible, but i still need to be able to restart all VM's which crashed on one head (node), on another head.
I am experienced in shell and perl programming, so if this functionality is not realized soon, i can do it, but for this i need to understand the logic of how Proxmox works better...
For example, who can tell me, how Proxmox node knows what VMs running on the local node and what - on the remote one(s)?
Thanks!
Andrey Konovalov,
Russia
Last edited: