Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure that shadow_memory is large enough for stable execution #942

Open
psrok1 opened this issue Jul 30, 2024 · 0 comments
Open

Ensure that shadow_memory is large enough for stable execution #942

psrok1 opened this issue Jul 30, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@psrok1
Copy link
Member

psrok1 commented Jul 30, 2024

Very common problem is too low shadow memory limit that results in random crash of Xen VM (output from xl dmesg):

(XEN) d99v0 failed to set entry for 12119 -> 18f17f1 altp2m 0, rc -12
(XEN) domain_crash called from p2m.c:2252
(XEN) Domain 99 (vcpu#0) crashed on cpu#16:
(XEN) ----[ Xen-4.16.0  x86_64  debug=n  Not tainted ]----

The reason is -12 (ENOMEM) caused by too low shadow_memory value set in /etc/drakrun/scripts/cfg.template

Xen recommends By default this is 1MB per guest vCPU plus 8KB per MB of guest RAM. and I think that even the current default of 32MB (recommended by Drakvuf) may be too low for some setups (although I don't have any good tool to measure it). I think we should make a proper note in documentation or check in draksetup to adjust this value.

@psrok1 psrok1 added documentation Improvements or additions to documentation enhancement New feature or request labels Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant