-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
5
-
False
-
-
False
-
CLOSED
-
CNV-26011 - DevPrev: Memory and CPU Limits on VMs
-
---
-
---
-
-
-
CNV Virtualization Sprint 232, CNV Virtualization Sprint 233, CNV Virtualization Sprint 234
-
High
-
No
Description of problem:
Kubevirt computes [1] the estimation of total memory needed for the domain to operate properly. This includes the memory needed for the guest and memory for Qemu and OS overhead.
When running IO intensive workloads, the memory consumption by the management layer (e.g. libvirt, QEMU, and other processes in the compute container) is larger than calculated. The difference between the expected and actual consumption is between 700M and 1.3G approximately.
Version-Release number of selected component (if applicable):
4.10.1
How reproducible:
100%
Steps to Reproduce:
1. create a VM with either local or ceph disks (Manifests are attached)
2. create xfs filesystem
3. mount the disks
4. run vdbench test as per example (via "vdbench -f test_file")
Actual results:
Memory used by the virt-launcher pod is as or below what's calculated
Expected results:
The difference between the expected and actual consumption is between 700M and 1.3G approximately.
Additional info:
VM Manifest attached
- blocks
-
CNV-26600 [2176031] Overhead of management layer in virt-launcher is not calculated accurately
- Closed
-
CNV-26601 [2176032] Overhead of management layer in virt-launcher is not calculated accurately
- Closed
-
CNV-26602 [2176034] Overhead of management layer in virt-launcher is not calculated accurately
- Closed
- is duplicated by
-
CNV-23058 revisit our requests to ensure calculations are correct
- Closed
- external trackers
- links to