I’m having an issue using Whonix on VirtualBox.
If you attach a Workstation/other VM to the Gateway and then use a multi-threaded TCP program with lots of network bandwidth it works at start, but after around 5-6 hours it hangs the Gateway.
When I use such a program Tor uses one whole core of the CPU in top always. There is always available RAM since less than 50% is actually used.
In the hanged state - the VM doesn’t respond to any input and you have to forcibly close it.
How can I fix this? It has been an issue for past Whonix versions and still hasn’t been fixed going into the new one.
My current Gateway specs:
2 GB of RAM
2 CPU cores
Hey, I’ve tried all of this - it seems like a separate issue connect to high performance applications running on VMs connected to the Gateway. I wouldn’t post otherwise 
It’s a really strange issue and I hope someone can help me find out what’s going on here. I could give someone the scenario by which they could test this out.
I might have skipped some information - my host system is using Windows 10 and newest version of VirtualBox. I’m 100% sure it’s a performance issue and nothing related to the environment/hardware/host OS.
-
There should be no issues here - every other VM works good. Last night I’ve tested with Whonix Gateway and another VM connected to it and it didn’t crash without a huge network load from the other VM.
-
Not needed - no connectivity issues - only issues regarding hanging.
-
Already using up to date Whonix.
-
Using latest VirtualBox.
-
Already did.
-
I did not use it.
-
N/A.
-
N/A.
-
N/A.
-
I would still want to run it from Windows if possible 
-
No other virtualizers installed other than VirtualBox.
-
No low RAM issues - on both the Gateway VM and the other host VM.
-
No hardware issues - haven’t had any issues with any other VM.
-
No RAM issues.
-
Already mentioned - any other Linux/Windows VM works fully without issues.
-
I’m not using Debian as host for the VM so it’s N/A.
-
Core isolation is disabled.
1 Like
Rare similar cases in the past reported that their issues were solved by using different hardware or a different host operating system. I cannot remember any Whonix bugs which caused such issues which could be resolved by fixing something in Whonix’s own source code.
Ideas for debugging:
-
Watch Tor Log
-
Watch Systemd Journal Log of Current Boot
-
Check Systemd Journal Log of Previous Boot
-
Generic Bug Reproduction or more specifically Tor Generic Bug Reproduction might be required.