PVE 4.2: force migration of vm from a dead node to another alive node

baudinpr

Member
Feb 14, 2011
40
0
6
Hi all,

just installed 2 PVE 4.2 servers in 2 node cluster configuration.
VM data is shared via DRBD9. All is working well.

Now I'm trying to do some tests...

I have just tried to shutdown a node and force migration of a VM running on that node to the other node.
On the running node, I tried:
# mv /etc/pve/nodes/DOWN-NODE-NAME/qemu-server/VMID.conf /etc/pve/nodes/UP-NODE-NAME/qemu-server/
but the /etc/pve filesystem is read only...

What I have to do ?

Many Thanks
Piero
PS both nodes have PVE community subscription active
 
Your run a two node cluster, so you loose quorum if one node is down. As workaround, you can set
expected votes to 1 using:

# pvecm expected 1

Note: Only do that when the other node is really down!
 
Thanks Dietmar,

how to return to original config after forcing expected votes to 1 ?
Tried:
# pvecm expected 2
but:
Unable to set expected votes: CS_ERR_INVALID_PARAM

Piero
 
Last edited:
Ok, it worked!

So, I think I have to add all the VM to the HA Resources on datacenter, right ?
 

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!