Search results for query: affinity

I ran into a somehow similar issue when migrating a VM, albeit not with the affinity setting but with a very special set of low level qemu args. I guess it boils down to the same privilege issue? 2025-05-29 11:00:32 ERROR: error - tunnel command...

Not yet, but maybe the ProxLB project might be a look worth in the meantime: https://github.com/gyptazy/ProxLB This also features the support of affinity and anti-affinity rules, ignore options on guest and nodes level and several other features.

...see two potential workarounds. Throttle the HDD VMs by limiting IOPS and bandwidth to a level that prevents noticeable IO delay. Or use CPU affinity to isolate SSD-only and HDD-using VMs, hoping that separating their CPU resources reduces contention. That said, I’m not happy with either...

affinity: 14-17 agent: 1 args: -set device.hostpci0.addr=02.0 -set device.hostpci0.x-igd-gms=0x2 -set device.hostpci0.x-igd-opregion=on bios: ovmf boot: order=scsi0;ide0 cores: 4 cpu: host efidisk0: local-zfs:vm-101-disk-0,efitype=4m,size=1M hostpci0: 0000:00:02,romfile=gen12_igd.rom hostpci1...

...preemption model). Enabling and integrating real-time system configurations, such as: Integrated workflows for CPU isolation, IRQ affinity, and low-latency tuning vCPU pinning, and using real-time scheduling policies (e.g., SCHED_FIFO, SCHED_RR) Integration or support for tools like tuned...

...have KVM configured. @promo2100 @fiona I maybe found a "stable" workaround. Currently everything is running fine since ~15h. I have set cpuaffinity on all my QEMU-Machines. Every machine now only has P-Cores (0-13) or E-Cores (14-20) assigned (on 13th Gen Intel(R) Core(TM) i9-13900H). So...

Maybe this? Add a newly named Storage backend to only nodes 1 & 2, then add a disk (dummy) to that VM from that storage - migration will then be unsuccessful to other nodes that do not have that Storage backend.

Need to cover: - HA: it should not jump to an unlicensed host. What you shared should be good enough. - Manual operator mistake: Would require a mandatory VM to host affinity.

the linked bug report is about allowing affinity to be set by non-root users, if that is your issue, then yes.

...with all the changes to the AMD P-State Driver? Sadly, I don't know how to get to the bottom of the problem. Edit: Manually pinning the CPU Affinity of the 8 cores/16 threads of the VM to CCD0 (0-7,16-23) in 6.14 brings back the performance of 6.11 - at least in X-Plane (61 fps). However, in...

Hello, everyone, I'm integrating the PVE with one application using the API, however, when I try to define an affinity on the VM, the API returns error 500 with the message "only root can set 'affinity' config". Is there anything I can do to solve this issue? API Endpoint used: Create...

...noisy neighbor problems ... There are services which have a benefit to being on the same hardware .... Not all components have the same affinity factors... Setting an affinity within an HA group to bias slightly to server A vs server B will often result in all of the services of that...

Welcome to the Proxmox forum, Walder! As far as I know, there are no global configurations to limit either the physical core affinity and/or number of physical cores usable by an operating system type of VM guests. But one option is that you can set the physical core affinity [0] for each...

Werd ich mal versuchen. Hatte das gleiche mit einem i9 mit 32 Kernen aber auch., Aber werde es versuchen.

...also von einen Quad-Core-Xeon 8 Kerne der VM zugewiesen? Dann muss ja Windows abgehen... Lass mal die Cores auf 4 und stelle zurück auf nur einen Socket. Ich würde noch CPU-Affinity auf "0-3" einstellen. Dann hat die VM auf jeden Fall die "richtigen" Cores und die 4 HT-Cores bleiben für den Host.

...allocate these loads on different physical cores? edit: Well, I tested this myself. Doing a stress test inside a VM and changing the core affinity, while monitoring the core CPU usage on the host. Sometimes it does put the load on the "correct" physical core, but sometimes it doesn't. So I...

Yes but there is also the affinity setting. The virtual VM cores are scheduled by the Linux kernel scheduler. I cannot tell you how that works in any detail, but you investigate the Linux scheduler implementations on your own. Proxmox leaves this to the Linux kernel and QEMU/KVM...

...the memory comes from one NUMA domain and the other half comes from the other (with two virtual and physical sockets). You can set specific affinity for each virtual core (with 1 thread per core) if you want. See affinity in the manual...

...0 osd fsid 0e6815a1-c56c-4525-871a-3b005f2eefc2 osd id 3 osdspec affinity type block vdo 0 devices /dev/sdc ====== osd.5 ======= [block]...

Damn I really showed my age. Maybe my proxmox obsession is all some kind of midlife crisis? …then again always been tinkering with computers it etc :D