Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upVM require more memory #2853
Comments
marmarek
added
bug
C: templates
P: minor
labels
Jun 8, 2017
marmarek
added this to the Release 4.0 milestone
Jun 8, 2017
marmarek
self-assigned this
Jun 8, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jun 8, 2017
Member
One thing is that SWIOTLB is enabled, even when no PCI device is assigned (this is Linux default when there is more than 3GB of RAM). This by default use 64MB of physical memory, which cannot be used for anything else. Reducing it to 16MB (default setting on Qubes 3.2) by swiotlb=8192 kernel option improve situation:
- sys-net use less swap (I'd say it is usable)
- other VM manage to reach the point where swap is enabled; after full startup about 50MB of swap is used
The results depends on maxmem setting because Linux kernel allocate metadata for all the memory, not only this really usable.
|
One thing is that SWIOTLB is enabled, even when no PCI device is assigned (this is Linux default when there is more than 3GB of RAM). This by default use 64MB of physical memory, which cannot be used for anything else. Reducing it to 16MB (default setting on Qubes 3.2) by
The results depends on maxmem setting because Linux kernel allocate metadata for all the memory, not only this really usable. |
marmarek commentedJun 8, 2017
Qubes OS version (e.g.,
R3.2): R4.0Affected TemplateVMs (e.g.,
fedora-23, if applicable): fedora-25When VM is booted as HVM, it very quickly get out of memory in default settings:
fork: Cannot allocate memoryon most services, including udev), this happens even before swap is enabledIncreasing memory setting do improve the situation, but also limit number of possible VMs.