Auto-Start Container if specific VM is up

alexgoaga

Member
Mar 19, 2021
9
0
21
32
Hey guys,
Im running promox on an hp microserver gen 8 for a while now and works like a charm. Unfortunately on my specific setup i have multiple vms that mount some synologys on the network and some of them are going down / up quite often due to experiments. Some containers also mount some file from there

Is there any solution if i start a VM manual , others can auto join ?
Or better , if a ping gets response / heartbeat , atuo-start after 4-5 mins ?

# pveversion --verbose proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve) pve-manager: 6.3-6 (running version: 6.3-6/2184247e) pve-kernel-5.4: 6.3-8 pve-kernel-helper: 6.3-8 pve-kernel-5.4.106-1-pve: 5.4.106-1 pve-kernel-5.4.73-1-pve: 5.4.73-1 ceph: 15.2.10-pve1 ceph-fuse: 15.2.10-pve1 corosync: 3.1.2-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.20-pve1 libproxmox-acme-perl: 1.0.8 libproxmox-backup-qemu0: 1.0.3-1 libpve-access-control: 6.1-3 libpve-apiclient-perl: 3.1-3 libpve-common-perl: 6.3-5 libpve-guest-common-perl: 3.1-5 libpve-http-server-perl: 3.1-1 libpve-storage-perl: 6.3-9 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.6-2 lxcfs: 4.0.6-pve1 novnc-pve: 1.1.0-1 proxmox-backup-client: 1.1.1-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.5-1 pve-cluster: 6.2-1 pve-container: 3.3-4 pve-docs: 6.3-1 pve-edk2-firmware: 2.20200531-1 pve-firewall: 4.1-3 pve-firmware: 3.2-2 pve-ha-manager: 3.1-1 pve-i18n: 2.3-1 pve-qemu-kvm: 5.2.0-5 pve-xtermjs: 4.7.0-3 qemu-server: 6.3-10 smartmontools: 7.2-pve2 spiceterm: 3.1-1 vncterm: 1.6-2 zfsutils-linux: 2.0.4-pve1

Thank you for your time,
Alex
 
some solutions come to mind:

* you create a script that starts the first vm and then the others, and only start the vm with this script
* you make use of the 'hookscript' functionality of vm to start others in the 'post-start' hook
* you have a timer/cronjob that queries the vm status and starts the others if its up (don't forget to track the on/off state correctly)