Search results for query: affinity

...vector databases with embedding models and pytorch) Due to ~460GB/s memory Bandwith and AVX512 im getting on Kimi-K2 15-20 token/s. (Zentorch) This is not possible in VM's!!! Numa doesnt work properly in VM's on Proxmox, L3 Cache affinity is not possible either. Cheers Ping @t.lamprecht @fabian

...not even that is needed: You can configure a shutdown policy: There are some caveats regarding fencing in case of quorum loss and the affinity rules though, you find the details in the remainder of the HA chapter. IMHO the shutdown-policy together with fitting configured affinity rules and...

...QEMU processes for the VMs. This should be possible (I think) by modifying some scripts in systemd and adding an entry such as [Service] CPUAffinity=Nstart-Nend Do you think this approach makes sense, or is it just a waste of time, because the physical host's OS already has an optimized...

...Setup: I have a Ryzen 9 9950x3d, 5090, x870e crosshair hero on my Pve 9.0.11 on all the latest updates. Host( slow performance) affinity: 0-7,16-23,8-15,24-31 args: -cpu host,-hypervisor,kvm=off, -smbios type=0,vendor="American Megatrends Inc.",version=1715,date="09/19/2025" balloon: 0...

Hi, When removing a VM via the GUI or API, the VM is not removed from HA Node Affinity Rules. Later, when I try to modify HA Node Affinity Rules via the API by retrieving the current resource list and adding a new resource, I get an error: cannot use unmanaged resource(s) vm:138, vm:169. This...

...to the group "mygroup" with the following body: With Proxmox 9.x this doesn't work because HA groups no longer exist, but rather HA Affinity Rules. As far as I can see, you first need to register a VM as an HA resource. This requires an HTTP POST to "cluster/ha/resources" with the...

...│ ha-group-preferred_proxmox1-4 │ └───────────────────────────────┘ api2/json/cluster/ha/rules [ { "type": "node-affinity", "resources": "vm:101,vm:111,vm:119,vm:129,vm:130,vm:132,vm:135,vm:144,vm:163,vm:166", "order": 2, "comment": "Generated...

..."{{api_prevention_token}}" body_format: json body: rule: "{{ha_rule.rule}}" type: "node-affinity" resources: "{{ ha_rule.resources.split(',') | reject('equalto', 'vm:'+sub_vm.vmid|string) | list | join(',') }}"...

...for the memory allocation for that VM node, I assume. But does it also implicitly pin the VM node0 CPUs to host node0 CPUs? I can use cpuaffinity to pin the VM to a set of host cores, but AFAICT it's just pinning the qemu process as a whole, so I assume there is no guarantee that qemu CPU...

...connected to a SAN, and I recently added a third host to serve as a quorum-only node for HA. I created an HA for a test VM and set up an affinity rule with the following priorities: Host1: priority 100 Host2: priority 90 However, when I reboot host1, the VM does not automatically migrate...

...Xeon(R) CPU E5-2697 v4 @ 2.30GHz GPU: Nvidia RTX 4060 Ti (PCI IDs: 02:00.0 and 02:00.1) VM Configuration (/etc/pve/qemu-server/100.conf): affinity: 0-15 agent: 1 balloon: 0 bios: ovmf boot: order=scsi0;ide2;ide0;net0 cores: 16 cpu: x86-64-v3 efidisk0...

...with the controlplane. But I guess, handling the issue via backupfleecing is much easier to configure, so you can try that first. :) BR, Lucas 1: For the same reason it might be helpful to disable HA handling via the PVE-Cluster, or at least configure anti-affinity for the vms hosting the...

...┌──────┬───────────────┐ │ key │ value │ ╞══════╪═══════════════╡ │ rule │ ha-group-all │ ├──────┼───────────────┤ │ type │ node-affinity │ └──────┴───────────────┘ but how do I get the actual rule contents like enabled, state, strict, HA resources, nodes and comment? And how about...

...threads to physical CPU threads. I mean when you defice CPU affinities in VM / Hardware / Processor / CPU affinitiy: n-m. E.g If I set CPU affinity to 2,5,9-11, I would like to have option that instead of current functionality that VM vCPU threads uses above mentioned pCores based on OS...

Thank It's all clear now. Thanks.

...dass das LRM dieser Node 'idle' ist, da es keine aktiven HA-Gäste gibt und dadurch auch kein Fencing benötigt. Eine Möglichkeit dies zu umgehen ist es die Nicht-HA-Gäste auf einer eigenen Node laufen zu lassen und die HA-Gäste von dieser Node auszuschließen, z.B. durch HA Node Affinity-Regeln.

Hi, in numa0/numa1, the cpus= list refers to guest vCPU indexes (0…vCPUs-1), not host CPU IDs. Affinity is the host cpuset for the whole VM process (all vCPU threads), not per-vCPU. Proxmox VE (QEMU) doesn’t expose per-vCPU pinning in the VM config, so you can’t directly “tie” guest vNUMA 0...

...nodes for the guest system and is not directly linked to the NUMA nodes and CPU cores on the host. In the PVE documentation, I found the 'affinity' option and changed the VM config to: cores: 8 sockets: 2 memory: 65536 numa: 1 numa0: cpus=0-7,hostnodes=0,memory=32768,policy=bind numa1...

Thank you!

Hi, yes, it's indeed on our roadmap here: https://pve.proxmox.com/wiki/Roadmap The new affinity/anti-affinity rules introduced with Proxmox VE 9.0 were a first step into that direction.