Hi!
We have set up a small Proxmox Cluster (3 Hosts, 2 for the VMs, 1 as a witness) with Replication and HA. We have even loadbalanced our VMs to be distributed between the 2 data hosts by setting 2 HA groups with different priorities. All is working well.
One small problem remains.
As we know, machines do not failover to another host if something is missing. I am talking here especially about:
a. an ISO file from a local storage that has been loaded into the virtual CD/DVD drive of a VM
b. a missing network device/bridge (because the other host has only 3 NICs instead of 4 - or maybe the NIC is faulty and we did not notice it).
Is there a way to force a VM to start after a failover on the other host, even though maybe an ISO or a NIC is missing? It would be preferably to at least have the machine run, even if it has only 2 NICs instead of 3 or the ISO in the CD-Drive is missing instead of, you know, not starting at all.
I get that these are corner cases. ISOs should be unmounted or put on a shared storage in the first place. Network Bridges should be configured exactly the same on both data hosts.
But it would be great if there were an option to force the machines to start as long as nothing is missing that's absolutely critical to start the machine.
Kind regards,
Christian
We have set up a small Proxmox Cluster (3 Hosts, 2 for the VMs, 1 as a witness) with Replication and HA. We have even loadbalanced our VMs to be distributed between the 2 data hosts by setting 2 HA groups with different priorities. All is working well.
One small problem remains.
As we know, machines do not failover to another host if something is missing. I am talking here especially about:
a. an ISO file from a local storage that has been loaded into the virtual CD/DVD drive of a VM
b. a missing network device/bridge (because the other host has only 3 NICs instead of 4 - or maybe the NIC is faulty and we did not notice it).
Is there a way to force a VM to start after a failover on the other host, even though maybe an ISO or a NIC is missing? It would be preferably to at least have the machine run, even if it has only 2 NICs instead of 3 or the ISO in the CD-Drive is missing instead of, you know, not starting at all.
I get that these are corner cases. ISOs should be unmounted or put on a shared storage in the first place. Network Bridges should be configured exactly the same on both data hosts.
But it would be great if there were an option to force the machines to start as long as nothing is missing that's absolutely critical to start the machine.
Kind regards,
Christian
Last edited: