Hi Guys,
Need help setting up VM to start at boot but after quorum is reached.
I often find VM does not start at boot due to quorum is not reached yet. I run 3 PVE 4.3 nodes in cluster with HA enabled for some VMs on top of GlusterFS, and non-HA VMs on top of ZFS RAID10, and 4x 10GbE LACP bonding. Perhaps the LACP bonding needs more time to connect to other nodes and thus the quota is not reached yet when Proxmox starts all VMs at boot.
Will setting up VM start up delay suffice? Or should I use the CT hack to sacrifice the first start when quorum isn't reached yet. This is frustrating as it is. Haha
Also out of the blue this week, all the three nodes restarted itself at the same time wreaking havoc though the overall system resources usage across all nodes are light to medium only. No caused of error was found in syslog and daemon.log.
---
# pveversion -v
proxmox-ve: 4.2-56 (running kernel: 4.4.13-1-pve)
pve-manager: 4.2-15 (running version: 4.2-15/6669ad2c)
pve-kernel-4.4.13-1-pve: 4.4.13-56
pve-kernel-4.4.10-1-pve: 4.4.10-54
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-42
qemu-server: 4.0-83
pve-firmware: 1.1-8
libpve-common-perl: 4.0-70
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-55
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-19
pve-container: 1.0-70
pve-firewall: 2.0-29
pve-ha-manager: 1.0-32
ksm-control-daemon: 1.2-1
glusterfs-client: 3.8.1-1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5.7-pve10~bpo80
Need help setting up VM to start at boot but after quorum is reached.
I often find VM does not start at boot due to quorum is not reached yet. I run 3 PVE 4.3 nodes in cluster with HA enabled for some VMs on top of GlusterFS, and non-HA VMs on top of ZFS RAID10, and 4x 10GbE LACP bonding. Perhaps the LACP bonding needs more time to connect to other nodes and thus the quota is not reached yet when Proxmox starts all VMs at boot.
Will setting up VM start up delay suffice? Or should I use the CT hack to sacrifice the first start when quorum isn't reached yet. This is frustrating as it is. Haha
Also out of the blue this week, all the three nodes restarted itself at the same time wreaking havoc though the overall system resources usage across all nodes are light to medium only. No caused of error was found in syslog and daemon.log.
---
# pveversion -v
proxmox-ve: 4.2-56 (running kernel: 4.4.13-1-pve)
pve-manager: 4.2-15 (running version: 4.2-15/6669ad2c)
pve-kernel-4.4.13-1-pve: 4.4.13-56
pve-kernel-4.4.10-1-pve: 4.4.10-54
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-42
qemu-server: 4.0-83
pve-firmware: 1.1-8
libpve-common-perl: 4.0-70
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-55
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-19
pve-container: 1.0-70
pve-firewall: 2.0-29
pve-ha-manager: 1.0-32
ksm-control-daemon: 1.2-1
glusterfs-client: 3.8.1-1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5.7-pve10~bpo80