The "Debugging Info" field controls whether you're running our fully-optimized hypervisor, or the less-optimized one that has extra debugging checks and logging. If you check our installed Workstation folder, we actually ship multiple separate "vmx" binaries, one for each mode. We similarly ship multiple "mksSandbox" binaries, and the "Debugging" option controls which one of those gets launched the same way.
So there should be a much reduced rate of logging to the disk when the "None" option is set in both the "vmware.log" and the "mksSandbox.log". For the most part though, the entries in the mksSandbox.log are all things that used to be printed into the vmware.log that are just now being printed into a different file, so the overall amount of logging (as far as the total bytes that hit the disk) shouldn't be substantially different from prior versions.
But if your concern is the actual presence of the file itself and not the amount of logging, I'm not aware of a way to just turn off the creation of that file. It should get created and rotated just like the vmware.log files no matter what "Debugging" options are selected.
