Speed or Packet Loss Issues with Whonix on KVM/VirtualBox

Support
1

Hello everyone,

I’m experiencing significant connection problem probably packet loss and slow speeds when using Whonix on both KVM and VirtualBox. However, my connection is stable and fast when I use Whonix via Qubes OS and the Tor Browser that make no sense but that my reality…

Has anyone else encountered this issue? What could be causing the difference in performance between these setups? I’ve tried multiple configurations, but the disparity remains clear.

Thanks for your help!

2

The only chance to debug this is to follow the connectivity troubleshooting checklist to be found here:

Please post the troubleshooting steps and their results.

3

i have follow all the Troubleshooting process but it’s look normal to me…

i would like to precise i use the same hardware the following

  • Kicksecure + whonix KVM

  • Ubuntu + Whonix Virtualbox
    = same , Bad connection , work few mins then connection become awful , change circuit in NYX doesn’t change nothing only “fix” is to fully shutdown and re run the gateway and its not always work

  • Kicksecure or any OS + Tor browser

  • QubesOS + Whonix
    = Work perfectly…

That make no sense , do QubesOS whonix gateway have any difference with the Whonix gateway kvm for example ?

i would like to post logs file but look like i am forbidden to post link and that probably really to much text to be pasted here could you allow me link please ?

4

Done.

(Posting Links for New Users)

5

Thanks

in Gateway logs :

sudo journalctl -b

systemcheck --ip-test

in Workstation logs :

systemcheck --ip-test (an error show there but not sure that it’s related)

tell me if you need any other logs

look like i have same problem as this person : Connection breakups and slowness - #6 by w0on1xfan

6

__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2025-07-17 15:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.

Check host clock.
Check VM clock.
Fix if necessary.
Instructions:

7

done , put all clock at UTC time at the exact second , host , gateway and workstation but dosent change the problem unfortunately…

8

__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2025-07-17 15:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.

Still happening?