This repository has been archived by the owner on Jun 28, 2024. It is now read-only.
Memory Hotplug is not available on arm64 #879
Comments
|
That also means that |
Pennyzct
added a commit
to Pennyzct/tests
that referenced
this issue
Nov 2, 2018
Since the new feature: memory hotplug, which uses the " (qemu) device_add pc-dimm,id=dimm1,memdev=mem1 " to limit memory on runtime, is not availble on arm platform, for now we just have to resort to skip relevant tests in aarch64. Fixes: kata-containers#879 Signed-off-by: Penny Zheng [email protected]
It would probably be worth capturing that in: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description of problem
Looking into the implementation of new feature: memory hotplug, runtime/#400, it uses the (
qemu) device_add pc-dimm,id=dimm1,memdev=mem1to limit memory on runtime. However, this feature is not availble for arm64 for now.Actual result
Nov 01 10:53:19 entos-thunderx2-desktop kata-runtime[184060]: time="2018-11-01T10:53:19.183208764+08:00" level=info msg="{\"error\": {\"class\": \"GenericError\", \"desc\": \"'pc-dimm' is not a valid device model name\"}}" arch=arm64 command=create container=aee45652f4df987389e82774b94a2da9fd702356e37559761a7dedc7bb60ff79 name=kata-runtime pid=184060 source=virtcontainers subsystem=qmpThis will lead to a large portion of mem_test.go failed. I will configure the filter configuration to skip these tests asap.
@Weichen81
The text was updated successfully, but these errors were encountered: