Set configuration file “/etc/rads.d/50_desktop_default” with the following settings:
rads_autostart_decision_feature=0
rads_start_display_manager=0
rads_minium_ram=480
rads_skip_ram_test=1
rads_wait=0
rads_wait_seconds=0
rads_debug=0
rads_disable_rc_d_remove=0
x_default_dm_config_file="/etc/X11/default-display-manager"
rads_display_manager=""
Testing Whonix-Gateway ProxyVM:
With normal enabled RADS settings and dynamic memory, startup time was ~9-10 seconds.
With normal enabled RADS settings and fixed 128MB memory, startup time was ~10-12 seconds.
With modified disabled RADS settings and dynamic memory, startup time was ~9-10 seconds.
With modified disabled RADS settings and fixed 128MB memory, startup time was ~10-14 seconds.
If RADS wait time of 10 seconds is default set to on, then RADS doesn’t seem to be invoked in any case.
Whonix startup is similarly fast in Qubes for me under all tested conditions.
And I tested using HDD (non-SSD). So Qubes is fast at VM startup.
Maybe @nrgaway did something special regarding Whonix startup / RADS?
[hr]
[hr]
Don’t think so. Only reporting 113MB based on the tests, when I set to 128MB fixed RAM.
[hr]
[quote=“Patrick, post:3, topic:768”]Please post the output of.
echo "$(free -m | sed -n -e '/^Mem:/s/^[^0-9]*\([0-9]*\) .*/\1/p')"
Output with 128MB fixed RAM set:
echo "$(free -m | sed -n -e '/^Mem:/s/^[^0-9]*\([0-9]*\) .*/\1/p')"
113
[hr]
[quote=“Patrick, post:3, topic:768”]As well as the output of.
free -m
Output with 128MB fixed RAM set:
free -m
total used free shared buffers cached
Mem: 113 111 2 0 1 20
-/+ buffers/cache: 89 23
Swap: 1023 10 1013
[hr]
[quote=“Patrick, post:3, topic:768”]Another way to make sure KDM (X) isn’t running.
sudo service kdm stop
Not sure if this had any affect. Repeated command multiple times in a row, got same output each time:
sudo service kdm stop
[ ok ] Stopping kdm (via systemctl): kdm.service.
[hr]
I believe this is the case, based on memory of reading something like this. Also, I remember something like Joanna mentioning there was no X server trusted by Qubes (VMs?). I think GUI components are isolated to Dom0 and shared by VMs. I think Qubes R3 is supposed to be further isolating GUI components to their own domain.