Marek Marczykowski-Górecki 86026e364f Fix starting PCI-having HVMs on early system boot and later ... 1. Make sure VMs are started after dom0 actual memory usage is reported to qmemman, otherwise dom0 will hold 4GB, even if just a little over 1GB is needed at that time. 2. Request only vm.memory MB from qmemman, instead of vm.maxmem. While HVM with PCI devices indeed do not support populate-on-demand, this is already handled in libvirt XML. The later may often cause VM startup fail on systems with 8GB of memory, because maxmem is 4GB there and with dom0 keeping the other 4GB (see point 1) there is not enough memory to start any sych VM. Fixes QubesOS/qubes-issues#3462		2018-01-29 22:57:32 +01:00
..
lvm2-pvscan@.service.d_30_qubes.conf	Order qubesd.service after lvm2-pvscan@.service	2017-08-12 19:50:50 +02:00
Makefile	Order qubesd.service after lvm2-pvscan@.service	2017-08-12 19:50:50 +02:00
qubes-core.service	Fix qubes-core.service ordering	2017-11-07 02:59:20 +01:00
qubes-qmemman.service	qmemman: remove cyclic service ordering	2017-11-21 13:01:51 +01:00
qubes-reload-firewall@.service	Remove qubes-netvm.service	2017-07-07 20:35:13 +02:00
qubes-reload-firewall@.timer	proxyvm: add support for rules with expire time (#760)	2014-03-28 02:54:59 +01:00
qubes-vm@.service	Fix starting PCI-having HVMs on early system boot and later	2018-01-29 22:57:32 +01:00
qubesd.service	Automatically restart qubesd when it crashes	2017-08-12 15:51:28 +02:00