Contributor
Contributor

How to disable all logging in the new version 16

I am new here sorry if this has been asked before, I couldn't find results,

The old method described in https://kb.vmware.com/s/article/1028 is not working any more in the new version 16

Now a new excusable will be execute the command C:\Program Files (x86)\VMware\VMware Player\x64\mksSandbox.exe" --logFile x:\xxx\mksSandbox.log to load the VM

And if Is there any way to disable the UI logs as well please,

I hope some one can help,

thanks

0 Kudos
7 Replies
Contributor
Contributor

I hope that someone also help me how to disable logging in the guest as well for the vmware tools

in this link https://kb.vmware.com/s/article/1007873 it is stated that writing log = false will not disable logs,

I have no such file in windows so I created an empty file in I:\ProgramData\VMware\VMware Tools as tools.conf, and used tools.conf.example as a guide, and the logs are still on, I tried adding log = false and didn't work, I tried to change the log file to memory didn't work

I Linux, there is a file in /etc/vmware-tools and contain the log = true but marked as comment with # so I removed # and changed to false didn't work neither

I hope someone help me both in windows and Linux,

thanks,

0 Kudos
Contributor
Contributor

I found  a way to minimize the logging for the VMtools in the guest to one line, and nothing will be written after this line

Adding log = false will do nothing, but I kept it anyway, but changing the level to none will work, just creat tools.conf if not exist, or edit it to be like the following

TH first 3 lines are enough, but I added all of the logs just in case

[logging]
log = false
vmtoolsd.level = none
vmsvc.level = none
vmusr.level = none
vmresset.level = none
toolboxcmd.level = none
hgfsServer.level = none
vmbackup.level = none
vmvss.level = none

I hope some one can help me finding a way to disable logs for the UI and unity helper of course the new log file in the version mksSandbox.log

0 Kudos
Enthusiast
Enthusiast

My understanding is that you can modify the file 'tools.conf' inside the guest

to control debugging information that is written to a file on the host.   I am hoping

this is not true as it would present a security issue.   I am hoping that any

debugging / logging information is strictly controlled on the host and NOT

the guest.

Ideally the VMX file should have line options to manage this.

0 Kudos
Contributor
Contributor

Yes, it is not true!

Editing 'tools.conf' will only affect the guest, the log files are stored in temp folder in windows, and var/log in linux, it is well explained here Smiley Happy  https://kb.vmware.com/s/article/1007873

But these logs are the VMware tools only

0 Kudos
Contributor
Contributor

I guess there is no option, anyone can one ask for a new feature to disable all logging?

 

Thanks,

0 Kudos
Leadership
Leadership

Hi,

There's this post:

https://communities.vmware.com/t5/VMware-Workstation-Pro/VMWare-Workstation-16-mksSandbox-log/m-p/22...

Personally I do not really get why there recently have been several people asking for how-to disable the runtime logging of base functionality of the product.
Can you tell me the use case for this? (just curious)

Without logs it is difficult to help people when they have problems as they will not have log files available useful for troubleshooting. I don't really think they are useful for anything beyond that.

--
Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
0 Kudos
Contributor
Contributor

I never read the logs, it is just a waste of the resources and will only consume your hardware.

 

In case of need, one can enable them.

0 Kudos