Closed wenlxie closed 4 years ago
We install the packages via get the 1.5.0 release tar and then install it via binary.
If I enable the console log, then from the console, I can see the error:
[ 61.832516] acpi PNP0C80:01: add_memory failed
[ 61.834407] acpi PNP0C80:01: acpi_memory_enable_device() error
[ 61.838092] Out of memory: Kill process 133 (kata-agent) score 4 or sacrifice child
[ 61.841639] Killed process 204 (pause) total-vm:3824kB, anon-rss:1000kB, file-rss:4kB, shmem-rss:0kB
time="2019-02-15T05:42:36.692647012Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=133 sandbox=66168c006afb63ba156a51f496607dff06e0560ade0d1d1e30f78bff92486b45 signal="child exited" source=agent
[ 61.887771] Out of memory: Kill process 133 (kata-agent) score 4 or sacrifice child
[ 61.890555] Killed process 133 (kata-agent) total-vm:463460kB, anon-rss:8760kB, file-rss:4kB, shmem-rss:0kB
[ 61.937938] systemd-udevd[92]: worker [1189] did not accept message -111 (Connection refused), kill it
[ 61.941428] systemd-udevd[92]: worker [1194] did not accept message -111 (Connection refused), kill it
[ 61.944994] systemd-udevd[92]: worker [1196] did not accept message -111 (Connection refused), kill it
[ 61.948558] systemd-udevd[92]: worker [1197] did not accept message -111 (Connection refused), kill it
[ 61.994515] reboot: Power down
The image [Image] Path = "/var/usrlocal/kata/opt/kata/share/kata-containers/kata-containers-centos.img"
is the image we build via osbuilder with debug log enabled. If we change to the default image, the issue still exists.
The console log:
SeaBIOS (version rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org)
Machine UUID 5487246d-5c9a-4cb7-a1e7-7e685743d05a
Booting from ROM..
bash-4.2# time="2019-02-15T08:00:33.765152406Z" level=info msg=announce device-handlers="mmioblk,blk,scsi,nvdimm" name=kata-agent pid=132 source=agent storage-handlers="9p,blk,mmioblk,sc3
time="2019-02-15T08:00:33.771298882Z" level=info msg="Started listening for uevents" name=kata-agent pid=132 source=agent subsystem=udevlistener
time="2019-02-15T08:00:33.775000008Z" level=info msg="agent grpc server starts" name=kata-agent pid=132 source=agent
time="2019-02-15T08:00:33.781045952Z" level=info msg="Getting interface from MAC address" interface-name=eth0 mac-address="ba:9a:da:d5:35:2b" name=kata-agent pci-address= pid=132 source=t
time="2019-02-15T08:00:33.78471215Z" level=info msg="Link found" interface-name=eth0 link="&{LinkAttrs:{Index:2 MTU:1500 TxQLen:1000 Name:eth0 HardwareAddr:ba:9a:da:d5:35:2b Flags:broadct
time="2019-02-15T08:00:33.799826234Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/di
time="2019-02-15T08:00:33.874638155Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=132 sandbox=bd351b19f7fb770d9cdc6fafce913842e461259a10f9728089052326a14d4044 signal=t
time="2019-02-15T08:00:33.877933761Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=132 sandbox=bd351b19f7fb770d9cdc6fafce913842e461259a10f9728089052326a14d4044 signal=t
time="2019-02-15T08:00:34.166432874Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:34.212933357Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:34.245957149Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:34.257942384Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:34.271811607Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:34.283766778Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:34.296702003Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:34.308916502Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:34.32091496Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/deu
time="2019-02-15T08:00:34.332937527Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:34.34592971Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/deu
time="2019-02-15T08:00:34.357923155Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:34.369918853Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:34.382504483Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:34.394920612Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:34.40691389Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/deu
time="2019-02-15T08:00:34.418923452Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:34.43182574Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/deu
time="2019-02-15T08:00:34.443916412Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:34.456540331Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/du
time="2019-02-15T08:00:36.662756147Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname=cpu/1/msr uevent-dr
time="2019-02-15T08:00:36.670462073Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname=cpu/1/cpuid ueventd
time="2019-02-15T08:00:36.670545353Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/dl
time="2019-02-15T08:00:36.670901527Z" level=info msg="Received add uevent" name=kata-agent pid=132 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/dy
[ 184.754738] Out of memory: Kill process 132 (kata-agent) score 4 or sacrifice child
[ 184.758297] Killed process 197 (pause) total-vm:3824kB, anon-rss:996kB, file-rss:4kB, shmem-rss:0kB
[ 184.771424] Out of memory: Kill process 132 (kata-agent) score 4 or sacrifice child
[ 184.775237] Killed process 132 (kata-agent) total-vm:529060kB, anon-rss:8732kB, file-rss:4kB, shmem-rss:0kB
[ 184.869191] Out of memory: Kill process 1431 (systemd-udevd) score 1 or sacrifice child
[ 184.872790] Killed process 1431 (systemd-udevd) total-vm:43516kB, anon-rss:2292kB, file-rss:0kB, shmem-rss:0kB
[ 194.877789] reboot: Power down
-m 2048M,slots=20,maxmem=387630M
2. From the kata runtime log, both object-add
and device-add
has no errors during memory hotplugIs there any memory hotplug limitation per dimm? All of the memory will be add in the same dimm no matter how big the memory size is.
@grahamwhaley @egernst @jcvenegas @gnawux @caoruidong Please help to have a check.
Sometimes at the boot log, there are some trace, but not exist everytime:
time="2019-02-18T05:36:28.552089315Z" level=info msg="Received add uevent" name=kata-agent pid=138 source=agent subsystem=udevlistener uevent-action=add uevent-devname= uevent-devpath=/devices/system/memory/memory36 uevent-seqnum=1593 uev
ent-subsystem=memory
[ 7.172271] kworker/u128:2: page allocation failure: order:9, mode:0x14084c0(GFP_KERNEL|__GFP_RETRY_MAYFAIL|__GFP_ZERO), nodemask=(null)
[ 7.177327] kworker/u128:2 cpuset=/ mems_allowed=0
[ 7.179504] CPU: 0 PID: 95 Comm: kworker/u128:2 Not tainted 4.14.67 #1
[ 7.182229] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
[ 7.184455] Call Trace:
[ 7.185465] dump_stack+0x5c/0x78
[ 7.186821] warn_alloc.cold.32+0x93/0x125
[ 7.188785] ? compaction_zonelist_suitable+0xc2/0x130
[ 7.190984] __alloc_pages_nodemask+0xcc5/0xda0
[ 7.192983] vmemmap_alloc_block+0x35/0x73
[ 7.194810] __vmemmap_alloc_block_buf+0xfc/0x108
[ 7.196758] vmemmap_populate+0xee/0x227
[ 7.198453] sparse_mem_map_populate+0x22/0x32
[ 7.200538] sparse_add_one_section+0x4a/0x157
[ 7.202417] __add_pages+0x82/0x1b0
[ 7.203842] add_pages+0x10/0x60
[ 7.205262] add_memory_resource+0xe5/0x150
[ 7.206981] add_memory+0x7b/0xc0
[ 7.208471] ? acpi_memory_get_resource+0xe0/0xe0
[ 7.210582] acpi_memory_device_add+0x120/0x290
[ 7.212459] acpi_bus_attach+0xc5/0x1c0
[ 7.214084] acpi_bus_scan+0x2e/0x60
[ 7.215469] acpi_device_hotplug+0x248/0x420
[ 7.217354] acpi_hotplug_work_fn+0x15/0x20
[ 7.219175] process_one_work+0x1a1/0x300
[ 7.220838] worker_thread+0x26/0x3d0
[ 7.222366] ? process_one_work+0x300/0x300
[ 7.224266] kthread+0x10f/0x130
[ 7.225734] ? kthread_create_on_node+0x40/0x40
[ 7.227670] ret_from_fork+0x35/0x40
[ 7.229298] Mem-Info:
[ 7.230355] active_anon:4983 inactive_anon:2102 isolated_anon:0
[ 7.230355] active_file:23 inactive_file:22 isolated_file:0
[ 7.230355] unevictable:0 dirty:18 writeback:0 unstable:0
[ 7.230355] slab_reclaimable:589 slab_unreclaimable:3504
[ 7.230355] mapped:677 shmem:2110 pagetables:381 bounce:0
[ 7.230355] free:4288 free_pcp:232 free_cma:0
[ 7.244002] Node 0 active_anon:19932kB inactive_anon:8408kB active_file:92kB inactive_file:88kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:2708kB dirty:72kB writeback:0kB shmem:8440kB writeback_tmp:0kB unstable:0kB al
l_unreclaimable? no
[ 7.253727] DMA free:9420kB min:44kB low:56kB high:68kB active_anon:8kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB kernel_stack:0kB pagetables:0kB bo
unce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
[ 7.263882] lowmem_reserve[]: 0 1964 1964 1964
[ 7.265738] DMA32 free:7628kB min:5648kB low:7656kB high:9664kB active_anon:19932kB inactive_anon:8408kB active_file:92kB inactive_file:88kB unevictable:0kB writepending:0kB present:2080636kB managed:2016036kB mlocked:0kB kernel_stack:
2192kB pagetables:1524kB bounce:0kB free_pcp:928kB local_pcp:732kB free_cma:0kB
then there will be errors:
fatal error: runtime: cannot allocate memory
I experienced the exact same issue on our system today. Has any progress been made since this issue was opened?
@mrlhansen looks like this bug was fixed here https://github.com/kata-containers/packaging/pull/335 what version of kata containers are you using?
@devimc I am using 1.11.0-rc0, specifically the packages from this repository. I checked that our kernel (v5.2.20) is compiled with the flag mentioned in the other issue.
[root@host ~]# grep CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE /boot/config-$(uname -r)
CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=y
I checked that our kernel (v5.2.20) is compiled with the flag mentioned in the other issue. [root@host ~]# grep CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE /boot/config-$(uname -r) CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=y
v5.2.20? this is the host kernel, right? CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE is required in the guest, not in the host, if you are using a custom guest kernel, make sure it includes this feature.
@devimc This is the host kernel yes. I did not realize the flag should be in the guest kernel - but that actually makes a lot more sense. Thanks a lot, I will try it out.
closing issue, since it was fixed here kata-containers/packaging#335, feel free to reopen if needed
I updated to the latest version of Kata Containers (v1.11.1) and I am using the default kernel and configuration that ships with the packages - and I am still experiencing the same problem. When I specify 120Gi it works, but anything above that fails. According to the kernel config file in the kata-linux-container-debug
package, this kernel does have the CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE variable correctly set.
@mrlhansen please run sudo kata-collect-data.sh
and paste it here please
@devimc The output is below. I am running everything via Kubernetes using the CRI plugin. For completeness, this is the yaml file I use to deploy the container.
apiVersion: apps/v1
kind: Deployment
metadata:
name: alpine-kata
namespace: default
annotations:
io.kubernetes.cri.untrusted-workload: "true"
spec:
selector:
matchLabels:
workload.user.cattle.io/workloadselector: deployment-default-alpine-kata
template:
metadata:
annotations:
io.kubernetes.cri.untrusted-workload: "true"
labels:
workload.user.cattle.io/workloadselector: deployment-default-alpine-kata
spec:
containers:
- args:
- tail
- -f
- /dev/null
image: alpine:latest
imagePullPolicy: Always
name: alpine-kata
resources:
limits:
cpu: "32"
memory: 120Gi
requests:
cpu: "32"
memory: 120Gi
securityContext:
allowPrivilegeEscalation: false
capabilities: {}
privileged: false
readOnlyRootFilesystem: false
runAsNonRoot: false
# Meta details
Running `kata-collect-data.sh` version `1.11.1 (commit 7b6f3b64873bbeed63f2f7937d83f1ed6ccd258a)` at `2020-06-18.08:21:58.538117677+0200`.
---
Runtime is `/bin/kata-runtime`.
# `kata-env`
Output of "`/bin/kata-runtime kata-env`":
```toml
[Meta]
Version = "1.0.24"
[Runtime]
Debug = false
Trace = false
DisableGuestSeccomp = true
DisableNewNetNs = false
SandboxCgroupOnly = false
Path = "/usr/bin/kata-runtime"
[Runtime.Version]
OCI = "1.0.1-dev"
[Runtime.Version.Version]
Semver = "1.11.1"
Major = 1
Minor = 11
Patch = 1
Commit = "7b6f3b64873bbeed63f2f7937d83f1ed6ccd258a"
[Runtime.Config]
Path = "/usr/share/defaults/kata-containers/configuration.toml"
[Hypervisor]
MachineType = "pc"
Version = "QEMU emulator version 4.1.1\nCopyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers"
Path = "/usr/bin/qemu-vanilla-system-x86_64"
BlockDeviceDriver = "virtio-scsi"
EntropySource = "/dev/urandom"
SharedFS = "virtio-9p"
VirtioFSDaemon = "/usr/bin/virtiofsd"
Msize9p = 8192
MemorySlots = 10
PCIeRootPort = 0
HotplugVFIOOnRootBus = false
Debug = false
UseVSock = false
[Image]
Path = "/usr/share/kata-containers/kata-containers-image_clearlinux_1.11.1_agent_34a000d0cf.img"
[Kernel]
Path = "/usr/share/kata-containers/vmlinuz-5.4.32.73-62.2.container"
Parameters = "systemd.unit=kata-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket scsi_mod.scan=none"
[Initrd]
Path = ""
[Proxy]
Type = "kataProxy"
Path = "/usr/libexec/kata-containers/kata-proxy"
Debug = false
[Proxy.Version]
Semver = "1.11.1-f61beff"
Major = 1
Minor = 11
Patch = 1
Commit = "<
@mrlhansen thanks, unfortunately logs section is empty, would you mind enabling full debug and try again ? thanks
@devimc For some reason, even after enabling debugging, the collect script did not have any information in the log files section. Instead I manually extracted some information from the system log on the machine. If you look in the attached file, starting on line 1085, you see that the guest kernel crashes.
thanks @mrlhansen - could you apply the following patch to the runtime and try again?
diff --git a/virtcontainers/sandbox.go b/virtcontainers/sandbox.go
index 4db46657..29b043b0 100644
--- a/virtcontainers/sandbox.go
+++ b/virtcontainers/sandbox.go
@@ -1824,6 +1824,21 @@ func (s *Sandbox) updateResources() error {
// Add default / rsvd memory for sandbox.
sandboxMemoryByte += int64(s.hypervisor.hypervisorConfig().MemorySize) << utils.MibToBytesShift
+ // Update Memory
+ s.Logger().WithField("memory-sandbox-size-byte", sandboxMemoryByte).Debugf("Request to hypervisor to update memory")
+ newMemory, updatedMemoryDevice, err := s.hypervisor.resizeMemory(uint32(sandboxMemoryByte>>utils.MibToBytesShift), s.state.GuestMemoryBlockSizeMB, s.state.GuestMemoryHotplugProbe)
+ if err != nil {
+ return err
+ }
+ s.Logger().Debugf("Sandbox memory size: %d MB", newMemory)
+ if s.state.GuestMemoryHotplugProbe && updatedMemoryDevice.addr != 0 {
+ // notify the guest kernel about memory hot-add event, before onlining them
+ s.Logger().Debugf("notify guest kernel memory hot-add event via probe interface, memory device located at 0x%x", updatedMemoryDevice.addr)
+ if err := s.agent.memHotplugByProbe(updatedMemoryDevice.addr, uint32(updatedMemoryDevice.sizeMB), s.state.GuestMemoryBlockSizeMB); err != nil {
+ return err
+ }
+ }
+
// Update VCPUs
s.Logger().WithField("cpus-sandbox", sandboxVCPUs).Debugf("Request to hypervisor to update vCPUs")
oldCPUs, newCPUs, err := s.hypervisor.resizeVCPUs(sandboxVCPUs)
@@ -1840,20 +1855,6 @@ func (s *Sandbox) updateResources() error {
}
s.Logger().Debugf("Sandbox CPUs: %d", newCPUs)
- // Update Memory
- s.Logger().WithField("memory-sandbox-size-byte", sandboxMemoryByte).Debugf("Request to hypervisor to update memory")
- newMemory, updatedMemoryDevice, err := s.hypervisor.resizeMemory(uint32(sandboxMemoryByte>>utils.MibToBytesShift), s.state.GuestMemoryBlockSizeMB, s.state.GuestMemoryHotplugProbe)
- if err != nil {
- return err
- }
- s.Logger().Debugf("Sandbox memory size: %d MB", newMemory)
- if s.state.GuestMemoryHotplugProbe && updatedMemoryDevice.addr != 0 {
- // notify the guest kernel about memory hot-add event, before onlining them
- s.Logger().Debugf("notify guest kernel memory hot-add event via probe interface, memory device located at 0x%x", updatedMemoryDevice.addr)
- if err := s.agent.memHotplugByProbe(updatedMemoryDevice.addr, uint32(updatedMemoryDevice.sizeMB), s.state.GuestMemoryBlockSizeMB); err != nil {
- return err
- }
- }
if err := s.agent.onlineCPUMem(0, false); err != nil {
return err
}
@devimc Thanks a lot for looking into this. I tried recompiling the runtime and replacing the kata-runtime
executable. However, the error is still the same. In the system log it now looks like the memory is enabled before the cores, so I believe the patch is correctly included. In the new log file attached here, the kernel starts crashing on line 740.
@mrlhansen thanks for testing this patch. I thinking that this bug is in QEMU 4.1, could you try with QEMU 5?
cc @stefanha @dagrh
@devimc I can try with QEMU 5. Do you have a fork I should use, or just the vanilla version from the QEMU website? Do I need some special configure options?
@mrlhansen please use the vanilla version, but use the following script to configure it https://raw.githubusercontent.com/kata-containers/packaging/master/scripts/configure-hypervisor.sh
bash -f configure-hypervisor.sh qemu | xargs ./configure
I don't think there's anything magic in qemu at the 128 G line (128G=37bits); upstream normally hits some fun at 1T and on desktop CPUs you hit problems at 512G (39b phys address) - but you're on an E5 so that shouldn't be a problem. That page allocation failure is fun - you're running out of memory trying to hot add memory :-)
So, one theoretical issue is, if you're hotplugging fairly huge DIMMs, you might not have enough free memory to even hotplug the first DIMM properly.
E.g., the memmap needs 1.56% of memory. In addition to that, you need pagetables. Assume you have 1G of free memory, the biggest DIMM you can plug is in the range of <65G. So if you have <2G you can never hotplug a single DIMM bigger than 130G. I guess this is what you see here.
To workaround that, you can hotplug smaller, individual DIMMs (which you should online immediately automatically within the guest), or increase the initial memory size.
Also note, the bigger your first DIMM, the more DMA memory you might lose ...
@davidhildenbrand @dagrh @devimc
Increasing the initial memory from 2G to 4G solved the problem. Thanks you all so much! Now that I know the reason and solution, it's so simple and obvious.
Just for future reference. Is is possible to configure kata to hotplug memory in smaller chunks spread over more DIMMs? Keeping in mind that this is running via Kubernetes.
@mrlhansen great! good to hear you found a solution
Just for future reference. Is is possible to configure kata to hotplug memory in smaller chunks spread over more DIMMs? Keeping in mind that this is running via Kubernetes.
yes, that's possible, the problem is that there is a limit in the number of memory slots, so if you have 10 slots and want to hot-add 120G, then the size for the chucks could be 12G, but this means you cannot hot-add more memory later because there are no more slots free.
@mrlhansen great! good to hear you found a solution
Just for future reference. Is is possible to configure kata to hotplug memory in smaller chunks spread over more DIMMs? Keeping in mind that this is running via Kubernetes.
yes, that's possible, the problem is that there is a limit in the number of memory slots, so if you have 10 slots and want to hot-add 120G, then the size for the chucks could be 12G, but this means you cannot hot-add more memory later because there are no more slots free.
Just a note (especially, because what I'll be mentioning is still under heavy, early development), the problems you are running/mentioning in here (DIMM too big for initial memory, limited number of slots, not onlining memory can result in issues in the guest) are some of the things virtio-mem tries to solve.
Thanks again for the help. Feel free to close the issue again.
closing issue.. thanks @mrlhansen
Description of problem
I am now integrating kata runtime with k8s. In the test environment, I found that my pod can't become
running
because sandbox can't be launched. When the container's request memory is 120Gi +, then we can see this issue. But when the memory is lower than 120Gi, then it works fine.Expected result
The sandbox can launched
Actual result
It fails.
(replace this text with the output of the
kata-collect-data.sh
script, after you have reviewed its content to ensure it does not contain any private information).Meta details
Running
kata-collect-data.sh
version1.5.0 (commit 5f7fcd773089a615b776862f92217e987f06df0a)
at2019-02-15.19:36:43.520404111-0700
.Runtime is
/usr/local/bin/kata-runtime
.kata-env
Output of "
/usr/local/bin/kata-runtime kata-env
":Runtime config files
Runtime default config files
Runtime config file contents
Output of "
cat "/etc/kata-containers/configuration.toml"
":Output of "
cat "/opt/kata/share/defaults/kata-containers/configuration.toml"
":Config file
/usr/share/defaults/kata-containers/configuration.toml
not foundKSM throttler
version
Output of "
--version
":systemd service
Image details
Initrd details
No initrd
Logfiles
Runtime logs
Recent runtime problems found in system journal:
Proxy logs
Recent proxy problems found in system journal:
Shim logs
Recent shim problems found in system journal:
Throttler logs
No recent throttler problems found in system journal.
Container manager details
Have
docker
Docker
Output of "
docker version
":Output of "
docker info
":Output of "
systemctl show docker
":Have
kubectl
Kubernetes
Output of "
kubectl version
":Output of "
kubectl config view
":Output of "
systemctl show kubelet
":No
crio
Packages
No
dpkg
Haverpm
Output of "rpm -qa|egrep "(cc-oci-runtimecc-runtimerunv|kata-proxy|kata-runtime|kata-shim|kata-ksm-throttler|kata-containers-image|linux-container|qemu-)"
":