You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently launch a container without CPU or memory limits, and trust libvirt and QEMU to do the right thing. We should instead set actual limits on the container.
One difficulty is that, since the limits specified by the user (using --cpu, --memory, etc.) apply to the VM and not the container, we must set a higher memory limit than requested on the container to account for QEMU memory requirements. The KubeVirt project has solved the same problem by estimating that overhead (see GetMemoryOverhead()). We could follow a similar approach.
The text was updated successfully, but these errors were encountered:
We currently launch a container without CPU or memory limits, and trust libvirt and QEMU to do the right thing. We should instead set actual limits on the container.
One difficulty is that, since the limits specified by the user (using
--cpu
,--memory
, etc.) apply to the VM and not the container, we must set a higher memory limit than requested on the container to account for QEMU memory requirements. The KubeVirt project has solved the same problem by estimating that overhead (seeGetMemoryOverhead()
). We could follow a similar approach.The text was updated successfully, but these errors were encountered: