087a02c7f4
Migrate meminfo-writer=False service setting to maxmem=0 as a method to disable dynamic memory management. Remove the service from vm.features dict in the process. Additionally, translate any attempt to set the service.meminfo-writer feature to either setting maxmem=0 or resetting it to the default (which is memory balancing enabled if supported by given domain). This is to at least partially not break existing tools using service.meminfo-writer as a way to control dynamic memory management. This code does _not_ support reading service.meminfo-writer feature state to get the current state of dynamic memory management, as it would require synchronizing with all the factors affecting its value. One of main reasons for migrating to maxmem=0 approach is to avoid the need of such synchronization. QubesOS/qubes-issues#4480 |
||
|---|---|---|
| .. | ||
| api | ||
| ext | ||
| qmemman | ||
| storage | ||
| tests | ||
| tools | ||
| vm | ||
| __init__.py | ||
| app.py | ||
| backup.py | ||
| config.py | ||
| core2migration.py | ||
| devices.py | ||
| dochelpers.py | ||
| events.py | ||
| exc.py | ||
| firewall.py | ||
| log.py | ||
| rngdoc.py | ||
| tarwriter.py | ||
| utils.py | ||