Search results for query: affinity

Well :) this line - is the online line in Proxmox to set task affinity. https://github.com/proxmox/qemu-server/blob/e781d9713fb3d45a523fe14db6cd99ac60bbfbb5/src/PVE/QemuServer.pm#L3202 Even with Numa (where you have multiple CPUs that have direkt and not direct memory) the user (that's you!)...

...in having the system autobalancing the load, especially for a high amount of vms should be considered aswell. Personally, i would not set affinity for each and every VM because i'd lose lots of dynamic behaviour and loadbalancing and rather decide on a case-by-case basis if the VM requires a...

We now have an SVG exporter. VMs are automatically assigned. proxmox-cpu-affiny tries to avoid bad combos. root@proxmox:~# proxmox-cpu-affinity status svg --affinity -o heatmap-affinity.svg This is still not production ready but it runs now on all of my servers.

Hello Proxmoxer, I created a tool to automatically set the CPU affinity (at runtime) for VMs. https://github.com/egandro/proxmox-cpu-affinity This picks the best combination of cores. As mentioned by this project: https://github.com/nviennot/core-to-core-latency. Here an example. CPU 1...

Right, that could definitely be improved by using "Keep Together (positive)" and "Keep Separate (negative)" in the web interface or using only the "positive" and "negative" names there too. I'm not sure about including the rule name/description here, because the former isn't shown in the web...

From the old resources.cfg from Nov 12 it seems that the HA groups were never fully migrated. Was the ` at the end an artifact of embedding it as code int he forum or was that part of the file? Either way, great to hear that your problem has been solved!

Daniel, l removed the "resources.cfg" and reconfigure HA (no rules change) Now no affinity problem the VMs with affinity "positive" are on the same node pve3. Thank you for your help/time Best regards. Francis

Hello Daniel, Normally the file resources.cfg is updated (Nov 12)? The file resources.cfg is and old file ??? with the 9.x I do not have pve*, server1 and server2 groups The package "pve-ha-manager" reinstalled on all nodes same problem and no resources.cfg updates for all nodes same...

Daniel, The command "Ha status" after the test sorry.

...next-fit fashion with the basic scheduler), and as vm:110 will follow suit with vm:104 to pve3 as these are in a positive resource affinity rule. As the node affinity rule is non-strict, it will fallback to {pve2, pve3} as the possible nodes for all three. If it were strict, all HA resources...

Hi Marcus, Probably you have the "chance" that vm101+102 migrate on node3 ??? Is there a way to debug HA "affinity" ? Best regards. Francis

qm config 107 affinity: 0-7,16-23 agent: 1 args: -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=NV43FIX,kvm=off' balloon: 0 bios: ovmf boot: order=scsi0;net0 cores: 16 cpu: EPYC-Milan-v2,hidden=1 cpuunits: 2000 efidisk0: b-zssd-disks:vm-107-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M...

Hi Francis, it is still working as expected with 3 guests here on my side. I have node affinity rule "node1" for id 100, 101, 102 and 2 of them with positive affinity rule id 101,102. Config looks like yours but different ids and hostnames. All 3 guests running on node1 node1 maintenance...

Hello Marcus, Thank you l have this Best regards. Francis

...are migrated together to node2 when node1 is set to maintenance. Here are my rules: root@node1:~# cat /etc/pve/ha/rules.cfg resource-affinity: ha-rule-91edaaa7-807b affinity positive resources vm:100,vm:102 node-affinity: ha-rule-e9b7994a-ecf1 nodes node1...

Hello, I have a problem with the HA affinity with PVE 9.1.2, I have two VMs with the resource affinity "Keep Together" and the node affinity "pve1". When I put the "pve1" in maintenance, one VM migrate to "pve2" and the other to "pve3", not on the same node. Best regards. Francis

...state to "started" and the VM starts. To avoid the problem, this preparation before host reboot does the trick: Change "Datacenter -> HA -> Affinity rules" to force the migration of the VMs to another host. When migration has completed, shutdown/restart of the host works fine. I hope this...

I manually assigned my LXCs to certain CCDs. Gemini wrote this code. (Have a 4 CCD TR now, upgraded from when I originally posted this)

For future reference, probably better/easier to enable maintenance mode: ha-manager crm-command node-maintenance enable pve1 (wait, then update+reboot) ha-manager crm-command node-maintenance disable pve1

...map it, I thought that maybe the IOMMU stuff was interfering with something, no idea that is happening, here is my VM configuration file: affinity: 0-7,16-23 agent: 1 balloon: 0 bios: ovmf boot: order=scsi0 cores: 16 cpu: host efidisk0...