Howard Chen wrote:
The problem lies within your computer processing speed and the numbers of
qubes you has opened and active in one minute; This will significantly
increases the opening time. As a result, it doubles the time of opening and
activating the qubes to be online.
I didn't spell that out down to the letter but to make matters worse
when i tested the creation time of the dvm on 4.0 the system was in fact
far more busy compared to my test on 4.1. on 4.1 only the bare minimum
was booted, sys-net, sys-firewall, sys-usb, sys-whonix, and that is it.
On any regular day there are about 18 VMs running at any given time. So
definitely the measured time was not influenced by how busy, or lack of,
my system was.
On Thursday, July 21, 2022 at 2:02:12 PM UTC-7 Qubes wrote:
Howard Chen wrote:
I have the similar as yours, but the time of one of my qubes cannot be
because of light VM error that I got, which is error 135. The time
effect is just to place for the computer took way too long on some
occasional reasons to go for it. Anyways, it's just the distro issue from
How can it be a distro problem from Debian? Or Fedora? The same version
of either on either 4.0 or 4.1 should be the same. Or not?
On Thursday, July 21, 2022 at 1:53:56 PM UTC-7 Qubes wrote:
Has the 4.1 as well as 4.1.1, because I did test on both, release added
additional overhead to the creation of a dvm?
I have identical dvm's for Firefox on 4.0 and 4.1 and on 4.1 it takes
almost, in the region of 0.5 - 0.75 seconds almost, **double** the time
for a new dvm to be ready for usage, 18 seconds vs 36 (both rounded for
That is quite a hefty difference. Is there any explanation for this
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit