There is no issue with rads.
If there is “not enough RAM”, rads does not attempt to start gdm3.
There could have been a bug in theory if rads supported only gdm but not gdm3. Then with “not enough RAM”, gdm3 would have still been started, because rads might have missed to inhibit autostart of gdm3. But that’s not happening here.
The root cause is that Virtual Console
tty1 is missing by default which is a systemd issue:
For first boot into Whonix CLI:
The workaround until virtual console
tty1 is automatically started is to use a different virtual console such as
tty2 as per documentation.
I didn’t test this for Whonix KVM but switching virtual console from
tty3, … is fully functional with Whonix VirtualBox. Just now tested, confirmed.
tty1 functional by default seems non-trivial and requires further troubleshooting. Help welcome.