Disable Qube updates for a specific qube

[qubist]

It’s more bandwidth because every time you do this you run updater on every single template whether it needs it or not. Whereas the usual route only checks for updates on templates whose appvms are run. If you have very few templates there’s little difference, but I have dozens of them.

The question is what checks means and how frequently that happens in each scenario (manual/automatic). If the automatic updater checks 5 min after each reboot (when you also run AppVMs), that will surely use more traffic as it is more frequent than doing it manually, e.g, once a week. Additionally, I don’t think it is necessary to notify remote hosts each time I reboot.

Yes, in my setup, they will all be updated, if updates are available. If there are no updates, only the “check” will use traffic, once a week. It seems the most traffic consuming check is that of dom0. One can skip it and/or update manually individual templates.

Hence my conclusions about the benefits of manual updates. I don’t insist that I am right though. It is just something that works for me.

Related:

How much traffic will update use?

Hi, I am on a limited traffic plan, so for me it is important to know in advance how much traffic will an update use (like ‘zypper up’ in openSUSE shows). Unfortunately, the default Qubes Update tool does not seem to show that info even when clicking “Details”. In section “Command-line interface” of the docs How to update there is a warning which strongly recommends using the Qubes Update tool for security reasons. While still learning about Qubes OS, I am careful not to risk the security of t…

Might be useful too (still not tested personally):

unman/notes/blob/master/apt-cacher-ng.md