Antti Kervinen

e2e: enable running commands in Qemu monitor and hotpluggin memory

1

Launch Qemu always with monitor server listening to a unix socket file in the VM directory. Add test script functions vm-monitor, vm-mem-hw, vm-mem-hotplug, and vm-mem-hotremove.

### Description Under some scenarios the balloon type in the annotation can be only a preference rather than a strict requirement. If a preferred balloon type does not exist, he...

### Description 1. Deploy balloons policy with config that allocates "cpu0" from both packages of a two-socket system to the reserved balloon, and creates four balloons (13-14 CPUs each) on...

RFC WIP: experimenting with building debug binaries and images

2

Builds debug versions of binaries and images with make DEBUG=1. When a debug version of an NRI resource policy image is running, you can attach debugger to it with `kubectl...

e2e: test topology-aware NUMA node change by AvailableResources

1

Test that a running container gets reassigned into new CPUs when the CPUs where it used to run are not included in AvailableResources anymore. Tests issue #92.

Assume that a container runs on CPUs of NUMA node 0. An admin wants to reorganize server resources so that containers will not use CPUs on NUMA/die/socket 0 anymore by...

[Bug] chatqna: xeon pipeline fails (serious performance drop) when CPU affinity of tei and teirerank containers is managed

7

### Priority P2-High ### OS type Ubuntu ### Hardware type Xeon-SPR ### Installation method - [X] Pull docker images from hub.docker.com - [ ] Build docker images from source ###...

Fix CPU and memory affinity under external resource management

1

- Fixes CPU affinity when running inference on CPU, and when CPUs are externally managed using taskset, numactl, cgroups, Kubernetes CPU manager, NRI resource policy plugins, for instance. - Detect...

Resource underutilization, thread thrashing: CPU affinity ignores allowed CPUs and cannot be switched off

4

### System Info CPU affinity implementation (introduced in commit 59922f9bc16afee9efcc7ee1c5f9d753ef314ffa, first released in v2.3.0, until current HEAD (4b8cda684b45b799de01a65e3fe3422a34a621d3) ignores already existing CPU pinning for the process. ### Information - [x]...