Search results for query: affinity

...be together on a node) and the HA Manager should not select the origin node as the node where the HA resource is located for positive resource affinity rules, but the target node, while migrating. I've opened a Bugzilla entry [0] to track this. [0]...

Hello, we've upgraded our cluster from 8 to 9 and created a few resource affinity rules (no node affinity rules present). For example there is one positive affinity rule for VMs 910 and 911. Both are simple Linux VMs with backing ceph storage (ssd pool). No PCI devices or anything else is...

Hi! Thanks for the feedback! Correct, HA resource affinity rules are currently strict only as one of the initial main use cases was to provide strict separation in case of a resource limitation, e.g. a specific PCIe device is only available once on each node and so guests must not be on the...

In HA node affinity rules, we have a "Strict" checkbox, which will not allow a VM/CT to be powered on outside of the selected nodes. With it unchecked, guests can, but they will always prefer a selected resource. In the HA resource affinity rules, we do not: And it behaves as if there is...

I'm using Proxmox VE 9.0.6 and had two affinity rules which I temporarily disabled. Today I tried to enable them again by clicking on the "enable" mark. This change won't propagate so I had to enter the rules again and deleted the original rules.

Thanks for the report! This is fixed with pve-manager >= 9.0.7 [0], which should be packaged soon for pve-no-subscription. [0] https://git.proxmox.com/?p=pve-manager.git;a=commit;h=4008a6472ada2bbd0f21c15fd7f5b047d71fcbd3

...that commonly causes exactly this symptom (fast one way, collapse the other way)? Any Proxmox-specific tunables (bridge offload, qdisc, IRQ affinity, netdev_backlog) that Proxmox users have found helpful for IPsec + Intel NICs? UPDATE 03-09-2025 After more digging, this doesn’t look like a...

...memory-wise. We have tested 2 vGPUs using a single physical GPU, and it seems everything goes through the CPU: GPU0 GPU1 CPU Affinity NUMA Affinity GPU NUMA ID GPU0 X PHB 0-7 0 N/A GPU1 PHB X 0-7 0 N/A Legend...

I had this same issue after upgrading to pve 9 and i needed the new HA Groups. I removed a bunch of old nodes but for some reason one stuck around in the HA status just like yours. Thanks for the fix.

...the HA rule ends in the "Freeze" state. I have configured the HA resources for the test CT i'm using for this test. And also crested a affinity rule for this CT. When I try to simulate a failover by stopping the CT (HA rule in stopped state). Nothing seems to happen. Is this behaviour...

I was testing the affinity rules, and they worked correctly. I only noticed that in the "node affinity rules" rules, if a rule is disabled, then when trying to "reactivate" it, it doesn't update the status. I was only able to reactivate it by editing the "/etc/pve/ha/rules.cfg" file and removing...

...already been updated. I've checked each one with the "pve8to9" script, and it tells me everything is OK. However, when I try to edit or add affinity rules, it gives me an error indicating that the HA groups have not yet been migrated: Is there a way to update the groups manually? Or would...

Got this message just today for ONE OSD with PVE 8.4 and Ceph 19.2.2 on a 3-node cluster with each 3 NVMe Disks. Faulty disk or should i just adjust the thresholds? Also i get this message on one host with the osd.8: On this host i can find these messages for all devices fc00000, fc00001 and...

Thx for the (smooth) update! I encountered two minor issues with the new HA affinity rules in PVE Web UI, can someone confirm? - Selecting an existing HA rule, the Edit-Button stays disabled, although I can edit the rule by double clicking it. I expected the edit-Button to be enabled. - Editing...

Hi, thank you for the report! Proposed fix: https://lore.proxmox.com/pve-devel/20250814143425.357868-1-f.ebner@proxmox.com/T/

...as well! In v9 of Proxmox I noticed the following: Datacenter --> HA: I add all VM resources I need and then go to the new HA --> Affinity rules --> HA Resources Affinity rules. There I can define a rule and it works as expected (Proxmox re-schedules VMs according to the rule defined)...

There was a thread a while back about using specific pools and a 1 GB disk to prevent VMs moving to (off of) certain nodes. I can find it later if you can’t. PVE 9 has a new affinity feature which sounds similar but I haven’t looked at it yet.

Ah, thx. Thought there is a new entry in the overview table in the beginning of the storage pages and was loiking for the word "affinity" in the index.

...5.5.0-2 qemu-server: 9.0.16 smartmontools: 7.4-pve1 spiceterm: 3.4.0 swtpm: 0.8.0+pve2 vncterm: 1.9.0 zfsutils-linux: 2.3.3-pve1 affinity: 0,2,4,6,8,10 agent: 1 bios: ovmf boot: order=virtio0 cores: 6 cpu: host,flags=+ibpb;+virt-ssbd;+amd-ssbd;+hv-tlbflush efidisk0...

...project. The roadmap entry mentioned there is for a native solution within Proxmox VE. For the Proxmox VE 9 release, the focus for HA was on affinity rules. But the release also includes changes to the RRD data, making pressure stall information readily available which is an important...