I've done some experimenting to get my Debian VMs to boot faster. So far I've reduced the start time significantly by disabling these services in the template:


Disabling the last two may have consequences, e.g. if you use VMs to access LVM storage. But that lvm2-monitor does consume a whopping 4+ seconds according to systemd-analyze. YMMV.

And note that my criteria for picking these is just a cursory glance at unit start times.

Ultimately, a good solution may be getting some of these units to start 10-20 seconds later. I think that makes sense in the case of lvm2-monitor. Some other time-consuming services like qubes-update-check already start later and don't seem to impact VM start times and responsiveness.

FWIW, Ubuntu has announced that boot times have worsened a lot and they'll make an effort to reduce them (again). Not sure to what extent that reflects on Debian.


Chris Laprise, tas...@posteo.net
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to