If kvm migration command fails, how can you assume that the VM is still OK?
> -----Original Message----- > From: pve-user [mailto:[email protected]] On Behalf Of > Dhaussy Alexandre > Sent: Donnerstag, 24. Juli 2014 14:26 > To: [email protected] > Subject: Re: [PVE-User] HA migration behaviour vs. failures > > Typo, /usr/share/cluster/vm.sh, not /usr/share/vm.sh > > Le 24/07/2014 14:15, Dhaussy Alexandre a écrit : > > In broad outline. > > > > With RedHat cluster : > > 1/ @node1: clusvcadm -M vm:foo -m node2 2/ @node2: kill the kvm/foo > > process 3/ @node1: clusvcadm fails with non-critical error (OCF code > > 150, see > > /usr/share/vm.sh) > > > > => You are happy and your VM is still in a good health. > > > > With Proxmox : > > 1/ @node1: clusvcadm -M pvevm:foo -m node2 2/ @node2: kill the kvm/foo > > process 3/ @node1: clusvcadm fails with code 1 (OCF_ERR_GENERIC), > > which ends up doing "clusvcadm -d pvevm:foo" > > > > => Your VM is dead. > > > > Regards, > > -- > > > > Alexandre DHAUSSY > > > > Le 24/07/2014 12:49, Dietmar Maurer a écrit : > > > >>> Sorry for being a bit cheeky here, but why did you change the way > >>> RedHat cluster behaves with online migration > >> I am not aware that we changed that? > >> > >> > >> > _______________________________________________ > pve-user mailing list > [email protected] > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user _______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
