@corny
There are times when it’s performing it’s regular updates check that things can get slow, but there are ways to prevent some slowness.
I often have RAM set as static, because they always use the maximum if you have them set to 4 GB anyway. I have some set to 1 and 2 GB of RAM.
They often take a few moments to boot up since I’m running SATA SSD on 6 Gbps SATA ports and I’m normally running multiple guests at once.
NetVM and FWVM I have with only 512 MB of RAM, and I have no issues on them.
Once the guests start, they then have the login and script execution times, this is where you may be seeing it be slow because of the script delay using all the CPU power for that guest before the terminal process starts and displays.
So for low RAM usage guests, just have it static. I think 95% of my guests are set as static because they all use 4GB for Fedora or Debian or Whonix anyway.
If they are a gateway or firewall, then 512 MB is enough. 1 GB if you feel you need to. I also trimmed down those guests as well, so they are small enough to not use much anyway, since all they do is route traffic.
I have the following pools…
CPU 0-1 (Domain-0) Scheduler 1
CPU 2-3 (Networking guests) Scheduler 1
CPU 4-6 (Web browsers and unimportant things) Scheduler 1
CPU 7-11 (Development/work/important guests) Scheduler 2
I generally run 8+ guests at any time.
512MB - NetVM (with NIC).
512MB - FW connected to NetVM.
512MB - InterVM guest connected to firewall for inter-guest communications.
512MB - Work Office VPN
1GB - Storage guest.
2GB - Dom0 (Sometimes I have it set to 1GB when I’m not going much on Domain-0)
Then I have the browsers…
2GB - Qubes Forum Guest
2GB - Temporary 1
2GB - Temporary 2
2GB - LinkedIN
2GB - Searcher
And others…
8GB - AI Development
2GB - Email Guest
2GB - Work Remote Connection
2GB - Work Office Storage
Generally on any guest the terminal takes about 3 seconds after the “started” message.
UNLESS they are installing packages after startup like my Viber guest. After it starts, the script installs Viber and dependencies from the local storage. I give it about 30 seconds to finish the DPKG runs for the installation.
Some others do other software as well. So the timing is extended because of the CPU utilisation from those guests. TOP normally shows that they hit 5 or 6 in a delay while they are doing the installs.
@juju42
I have a 4th generation PC here, I’ll install onto it and see where things go on that.
I still have no idea why you are having these issues though.
I’ll check it out and let you know what happens.