Bug related to memory overcommit in KubeVirt 1.6.2
0 views
Skip to first unread message
Jed Lejosne
10:14 AM (5 hours ago) 10:14 AM
to kubevirt-dev
A breaking change related to memory overcommit was recently introduced in main [0] and unfortunately backported to 1.6 [1] and included in 1.6.2 [2].
So far it's only known to affect memory "undercommit", i.e. overcommit below 100, used with VMs that set a low memory limit, which shouldn't be a common use-case. What can happen then is a virt-launcher pod that requests more memory than its limit, preventing it from getting scheduled.
Anybody affected by this should either increase the memory limit on their VM or raise overcommit to 100 or higher. (As a side note, undercommitting doesn't make much sense and should be disabled in the near future)
The change has been reverted in the 1.6 release branch [3] and we are actively working on fixing the bug in main [4] [5]. Once fixed in main, we plan on (re-)backporting the code to 1.6.
An issue was opened [6] to track the resolution.
Sorry for the inconvenience,
Jed
Reply all
Reply to author
Forward
0 new messages