News Feed
  • DrugHub has agreed to fully refund all users who lost money in the SuperMarket exit scam.  
  • Retro Market has gone offline. Circumstances of the closure unknown.  
  • SuperMarket has closed following an exit scam by one of the admins.  
  • The admin of Incognito Market, Pharoah, has been arrested by the FBI several months after exit scamming.  
  • Silk RoadTorhoo mini logo
  • darknet markets list
  • Popular P2P exchange LocalMonero has announced it is closing.  

VirtualBox nolog setup writeup : privacy | Torhoo darknet markets

As we all probably know Virtual-Chastity-Cage-Box being Type 2 Hypervisor is subpar compared to bare metal Type 1 hypervisors yet it still has a large user base.
If you are annoyed by its tendency to keep logs fat and dripping with OpSec damaging details do read on.
I hereby present you a small guide on how to disable its logging for good.

VirtualBox keeps logs in several different places:
The current user home: ~/.config/VirtualBox/
Also for each individual VM you create it also erects a directory corresponding to it named Logs.

First make sure you stop all running VirtualBox processes, go to these folders and delete every log file - *.log
Now you should set some environment variables to disable logging - pretty stupid I know :)
I've tried many different ways to set them but the only ways that worked for me are:

1. Manual execution by setting them directly before executable(just an example, feel free to do it another way):
export VBOX_RELEASE_LOG_DEST=nofile && export VBOX_LOG_DEST=nofile && export VBOXSVC_RELEASE_LOG_DEST=nofile && export VBOX_GUI_SELECTORWINDOW_RELEASE_LOG_DEST=nofile && virtualbox
This method is pretty clunky and inconvenient, sometimes still created some logs. Setting them globally for all users on the machine(better):
cat >> /etc/environment <<\EOF
VBOX_RELEASE_LOG_DEST=nofile
VBOX_LOG_DEST=nofile
VBOXSVC_RELEASE_LOG_DEST=nofile
VBOX_GUI_SELECTORWINDOW_RELEASE_LOG_DEST=nofile
EOF

Do keep in mind that you would have to logout/login to have these put in motion and effect.

The end result should be no log files created at the two destinations mentioned at the beginning.
Note that it in each individual VM directory it still creates directory named Logs but it now should remain empty.
/u/MrBacon420 P
1 points
2 weeks ago
Thank you for the write up.
I had some time to get KVM up and running. Took a couple of hours. No crashes either. I'll be nuking VirtualBox in the next week after I'm 100% confident I can. /post/c32ab31604fbf1d85eac
/u/DaSnake 📢
1 points
2 weeks ago*
That is the proper way.
As /u/datarape pointed out /post/b990c52345f79522b4d8/#c-46d1671c2106cd9f87
and I backed him /post/b990c52345f79522b4d8/#c-c3917264d74818d761
Using and relying on VirtualBox for anything critical is at the very least one being naive and delusional.
It still has some use cases and it posesses some quality of life conveniences that are hard to obtain on KVM setups.