When using “Kill qube” in Manager on whonix qube (AppVM), qube immediately starts up again. Why?
Thank you.
I had this problem more than a year ago with both gateways (WhoNix) and workstations (WhoNix).
Check in Qubes Manager -> System -> Global Settings or some other Whonix is calling on SysWhonix. If this is not true try reinstalling the Whonix Templates. When everything else fails including restoring from backup it is time to clean completely your machine including BIOS.
Yes I know the pain!
1 Like
other than the usual whonix warning about security TWO appvm-ws I’m doubting would cause that, I would manually check dom0 and/or -gw -ws templates for any apt-get upgrade
i had the restart problem few weeks back don’t recall if it was whonix though
I have a similar problem also with a whonix-based AppVM. But I haven’t had the chance to look more into it yet. From the security perspectives, the possibility of a bug like this does sound some alarms.
Maybe worth checking on the whonix forum for similar problems?
(@abc I’ve made the title a bit more specific. Feel free to edit it back if you feel it doesn’t apply)
1 Like
Thanks. Might be because two Whonix qubes connected to sys-whonix.
I’m still having this issue. Anyone else?
2 Likes
Yes, me.
@Registeron, please make sure you’re running a fully updated version of the operating system and then, maybe to try to bring it up on the whonix forum (as I stated here), so the whonix developers have a chance of being aware of it 
Recently (could be that it happened since my last template update) I am having the problem that my VMs are restarting for no reason as soon after I shut them down. They are succesfully shut down but then just restart even if I do nothing. Why is this?
I could just wait for the next update and hope it will go away but I am afraid it could be something dangerous (a compromise).
- all VMs or only specific one (e.g. sys-net, sys-firewall)?
- how long did those VM run before you try to shutdown?
- how do you shut them down?
- what template are they based on?
- how do you know they restart / are running?
- are you using any testing repositories?
- which Qubes OS release are you using (R4.0 or R4.1)?
1 Like
After clicking on Shutdown, the cube turns off, and then turns on itself again. It looks like a restart. The problem appeared on 4.1
@Userif I moved your post into this thread as it seems to be about the same issue. Please answer the questions I posted above. You originally posted under “R4.1” so we know which release you are using.
@Registeron are you on R4.0 or R4.1?
I just discovered that I’m having the same issue with at least one of my qubes:
- all VMs or only specific one (e.g. sys-net, sys-firewall)? Whonix AppVM (non-disposable)
- how long did those VM run before you try to shutdown? various lengths of time
- how do you shut them down? shutdown command from both the Qube Manager and from the tray
- what template are they based on? whonix-ws-16
- how do you know they restart / are running? Qube Manager
- are you using any testing repositories? no
- which Qubes OS release are you using (R4.0 or R4.1)? R4.0
Notably, if I kill the qube from the Qube Manager it does not restart.
I had a similar issue with sys-whonix starting automatically. I was using an alternate Tor gateway VM that was somehow triggering sys-whonix to start. This fixed it. ymmv
@Sven ephile’s answer does also apply to my case.
@necker I have created my Whonix VMs with sys-firewall as ‘Networking’. The link you’ve posted says I should use sys-whonix. Could this be the problem here? Why should I use sys-whonix?
Principle: if a qube is a dependency for another (netvm) or some system functionality (clockvm, updatevm) it will be started by the system on-demand.
Any chance you have set this qube to be e.g. the clockvm?
I tried another Whonix appVM, which I never use, and it had the same problem. Both appVMs have sys-whonix as their appVM. I fiddled around and managed to resolve the issue, so shutdown is working as normal again. I’m not sure if it was a template update, or poking around in the template root terminal and then restarting, but something appeared to reset…
@Registeron I’d be concerned about using sys-firewall as the netVM, since Whonix appVMs are designed to work only with a Tor gateway as the netVM. Seems like a recipe for trouble.
dom0$ qubes-prefs shows sys-net as the clockvm
It was worth checking, but I’m pretty sure none of my appVMs in question would need to be started by the system on-demand.
I don’t think a Whonix workstation would even work (have connectivity) when connected to any netvm that is not a Whonix gateway.