[PVE-User] HA behavior with VMs (PVE 2.2 pre-release)
martin at proxmox.com
Thu Oct 11 14:25:25 CEST 2012
If you enable HA for a VM or CT, make sure that the VM/CT is off. As soon as you enable HA, the resource manager (rgmanager) takes control and starts the VM/CT. you can still live migrate manually. If you click “Stop” the VM/CT will be stopped and not started again by rgmanager.
If you need to reboot a host, live migrate all VM/CT´s to other node or stop the VM/CT.
If your system does not work like this, it’s a bug or configuration issues. (stopping rgmanager is not a suitable testcase to simulate a failed node)
martin at proxmox.com<mailto:martin at proxmox.com>
From: pve-user-bounces at pve.proxmox.com [mailto:pve-user-bounces at pve.proxmox.com] On Behalf Of David Black
Sent: Donnerstag, 11. Oktober 2012 13:39
To: Dietmar Maurer
Cc: proxmoxve (pve-user at pve.proxmox.com)
Subject: Re: [PVE-User] HA behavior with VMs (PVE 2.2 pre-release)
If you mean disabling HA allows me to regain full control of the VM, I do understand that, and at the moment consider it a workaround.
Or do you mean by design, HA enabled = VM unconditionally runs and can't be powered off, regardless of the autostart parameter setting?
That seems unlikely to me, isn't mentioned in the wiki HA section, and is why I emailed. If that's not how you intend it to work, I'd be happy to open a bug.
Simply remove the VM from HA if you do not want that behavior.
Note: HA = High Availability
Because of #3, it seems I can't have a powered-off VM sitting there, that will be moved to another host in the event whichever host it's on goes down. Seems like a bug to me. Maybe the behavior of #3 and 4 are related. I want to make all my VMs "protected" by HA whether they're running or not, so they always remain accessible regardless of their powered off/on status. Also, why can't I have an HA-protected VM stay powered off? :-)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pve-user