4b44f977db
HVM should have meminfo-writer disabled by default (and now have). But existing VMs have it already enabled so it must be fixed now. Generic HVM isn't capable of dynamic memory management. Previously it was forced to always have maxmem=memory but it wasn't fully correct because someone could install Qubes agents/PV drivers including meminfo-writer and xen-balloon even in HVM so it should be possible to turn it. |
||
---|---|---|
.. | ||
core-dom0-vaio-fixes.spec | ||
core-dom0.spec | ||
core-libs.spec | ||
core-vm-kernel-placeholder.spec | ||
core-vm.spec |