Search results for query: affinity

My test environment is a stretched cluster like yours. The witness node is a full cluster member. I use a HA Node Affinity rule to prevent unwanted VMs from running on the witness node. The rule includes all the hosts except for the witness and is set in strict mode. The VMs are assigned to...

...Is there any way to automate this or bulk-add multiple VMs in WEB GUI? I’ve tried many times to bulk-add VMs to HA resources, but I still can’t. I’ve already read the section above, but “HA Node Affinity Rules” seem to only control where VMs restart, not provide a way to bulk-add VMs to HA.

...because it is known that there aren't any other viable nodes to migrate to. In fact, it is the same behavior as putting a strict node affinity rule on one of these HA resources on their current node, while the other HA resource does not have any node affinity constraint. In that situation...

...HA know to move them to a different node? Or is it currently trying "random other host"? For instance that would be an issue in a 2 node cluster with QDevice...both could keep moving to the other node. (hypothetically, and any cluster where "N" VMs are negative affinity, with the same "N"...

...resource is on the same node as a HA resource it must not be together with and schedules both to move to other nodes. Negative HA resource affinity rules are relatively strict at the moment, as in 'these HA resources have some hard constraint to never run on the same node' (for example, both...

For reference (bug #7464):

This is what I personally use: affinity: 0-11 agent: 1 args: -cpu Skylake-Client-v4,vmx,hv-passthrough,pdpe1gb bios: ovmf boot: order=scsi0;net0 cores: 12 efidisk0: local-zfs:vm-104-disk-0,efitype=4m,ms-cert=2023w,pre-enrolled-keys=1,size=1M hostpci0: 0000:03:00.2,pcie=1 hugepages: 1024...

...the same node that are usually and should probably be separate (though not critical). I thought that was a great use of the new HA negative affinity feature, so I created one for the two VMs. To my mild surprise both VMs moved to a new host. Is that expected? I would have thought only one...

...at the second site, you can surely turn this PVE instance into a glorified quorum voter. You can easily accomplish this by using simple node affinity HA rules to completely exclude it from running VMs, or restrict it to run only non-critical VMs if needed. Important to note here is that if...

This would work. Not an ideal solution but if you can ensure that no workloads ever gets distributed on it (in case you use something like prox-lb or the affinity rules of Proxmox VEs native ha-manager see https://pve.proxmox.com/pve-docs/chapter-ha-manager.html ) it should be "good enough".

...volumes - can't migrate VM - check log TASK ERROR: migration aborted The same thing happens when attempting to migrate vm-101 using affinity rules. Only then does the error message reappear every 10 seconds. As soon as the cloudinit image for vm-101 is rebuilt on node ve2, the migration of...

Guter Hinweis mit PVE 9.1, da hätt ich direkt auf die neuen Node Affinity Rules eingehen sollen statt auf die alten HA-Gruppen. Das Prinzip ist aber dasselbe, Prioritäten und Failback funktioniert mit den Rules genauso. Für die VMware-Migration viel Erfolg! Falls ihr da Unterstützung braucht...

...bereits mit PVE 9.1. hier sind die HA-Gruppen bereits von den HA-Regeln abgelöst. "HA Groups are deprecated and migrated to HA Node Affinity rules since Proxmox VE 9.0." @mkoeppl @Bu66as Danke für die Rückmeldungen! Dann funktioniert es also genau so wie ich es mir gedacht habe...

Thanks for your answer. Yes, you are right, there is an affinity rule to failback. I will disable it for now. Will there be a fix that will override cloudinit images in the near future?

Hi! Thanks for the report! I suppose there is a HA node affinity rule which makes the HA resource failback to the old node. As the node fails, the HA Manager will move the HA resource but not clean up the cloudinit image from the failed node as it would happen in normal circumstances... I...

...(cJSON 1.7.15) Linux inc2pve1 6.17.9-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.17.9-1 (2026-01-12T16:25Z) x86_64 Optional features available: CPU affinity setting, IPv6 flow label, SCTP, TCP congestion algorithm setting, sendfile / zerocopy, socket pacing, authentication, bind to device, support...

...Star citizen. Was working about 5 months, now it says can't run in virtual machine :( This is my conf, already had SMbios and -hypervisor. affinity: 0-13 agent: 1 args: -cpu host,kvm=off,-hypervisor balloon: 0 bios: ovmf boot: order=scsi0 cores: 14 cpu: host efidisk0...

I have a k=4 m=2 erasure code pool on a single host with 6 - 6 tb SAS drives in a Dell R730. I have a NVME drive (Intel DC P4510) split up into DB and WAL for each OSD. I am using this pool with CephFS. Using iostat, I am not seeing any reads going to the NVME drive even when running fio...

...oder per Skript). Beides gleichzeitig — automatisches Failback UND freie manuelle Verteilung ohne Regelanpassung — geht mit HA-Gruppen so nicht. Das ist ein grundlegender Unterschied zu VMware DRS, wo Affinity Rules und dynamische Verteilung unabhängig voneinander arbeiten. Doku: HA Groups

...@UdoB sei der Vollständigkeit halber noch ergänzt, dass Rules ebenfalls eine strict Option bieten. Siehe hier. Intern werden bei einer Node Affinity Rule, die nicht strict ist, Nodes, die nicht Teil der Node Affinity Rule sind, als "mögliche" Nodes behandelt, haben allerdings eine niedrigere...