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 upCorrectly calculate free memory in the system #3
Comments
marmarek
assigned
rootkovska
Mar 8, 2015
marmarek
added this to the Release 1 Alpha 2 milestone
Mar 8, 2015
marmarek
added
bug
C: core
P: major
labels
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Modified by joanna on 9 Apr 2010 23:40 UTC |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Comment by joanna on 10 Apr 2010 12:52 UTC |
marmarek
closed this
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Mar 8, 2015
Member
Comment by joanna on 10 Apr 2010 13:02 UTC
The changes are applied to qubes-code-dom0-1.0.1-1.rpm. User can update by doing (in Dom0):
yum update qubes-core-dom0
|
Comment by joanna on 10 Apr 2010 13:02 UTC yum update qubes-core-dom0 |
This was referenced Mar 8, 2015
TNTBOMBOM
referenced this issue
Dec 12, 2015
Closed
dom0 , OSError: [Errno 2] No such file or directory: '/var/lib/qubes/servicevms/dom0/apps.templates' #1491
TNTBOMBOM
referenced this issue
Jan 16, 2016
Open
qubes "VM didnt give resources back.." (Whonix appVM) #1643
HardenedArray
referenced this issue
Jan 27, 2016
Closed
[{Self}-SOLVED]: Following Successful Qubes (R3.1-rc2) Installation, Operation, and Initial Rebooting, Qubes CANNOT Boot from an USB HDD, Once the USB HDD Cable Has Been Disconnected #1658
andrewdavidwong
referenced this issue
Mar 18, 2016
Closed
Improve qvm-backup key derivation/management #971
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
marmarek commentedMar 8, 2015
Reported by wikimaster on 6 Apr 2010 16:59 UTC
Currently
qubes.pyprevents starting a VM if the memory available for Dom0 was to go below a defined limit (700MB). On some systems, when Dom0 becomes short on memory (<500MB), and Dom0 starts using the swap file, the overall system performance drops down dramatically. This is most likely caused by the reduced filesystem caching, and is very apparent on systems with fast SSD drives, enabled full disk encryption, and _without_ the AES instruction in the CPU (in which case CPU is heavily loaded doing the crypto).The
QubesVM.start()method calculates the memory that will be left to Dom0 after the start of a new VM using this simple method:... and if
dom0_mem_newis too small it raises an exception, whichqvm-runhandles and displays a message to the user that she should stop some running VMs before continuing.However when the users stops a VM, Xen doesn't return the memory back to Dom0. This, in turn, makes it impossible for the user to start any new VM, without rebooting the system.
The proper solution should account for this "hidden" memory that has been freed when a user stopped a VM, and is available to other domains, but has not be returned to Dom0.
Migrated-From: https://wiki.qubes-os.org/ticket/3