Accessing VMRC Log Files

Some components in the VMRC SDK automatically produce log files. You can use these log files for tracing VMRC behavior for debugging and optimization. When reporting bugs or other issues with VMRC, as a best practice, include the locations of the directories containing the relevant log files.

The VMRC components automatically generate log files.

■	VMRC Application Log. The application log is a log file produced by the client VMRC binary that processes VMRC API calls.

■	VMRC Plug-In Log. The plug-in log file produced by the VMRC browser plug-in library that client Web applications use to call API methods.

■	Remote MKS Log. The MKS log is produced by the an MKS binary on the local client machine. The MKS binary provides display data and metadata used to show the target virtual machine console.

■	USB Arbitrator Log. The USB arbitrator log is produced by the privileged USB service that provides the data and functionality used to connect local client USB devices to remote virtual machines.

Windows Log File Locations

Windows Log File Locations shows the location of each log file on the Windows operating system.

Windows Log File Locations

Log File	Location
VMRC Application Log	%TEMP%\vmware-%USERNAME%\
VMRC Plug-In Log	%TEMP%\vmrc-plugin\
Remote MKS Log	%TEMP%\vmware-%USERNAME%\
USB Arbitrator Log	%SYSTEMROOT%\Temp\vmware-SYSTEM\

Linux Log File Locations

The VMRC browser plug-in does not generate a log file on the Linux operating system. You can access plug-in log information by running your Web browser from the command line. The VMRC browser plug-in generates logging information on stdout.

You can find logs generated by the VMRC native application process, as well as a Remote MKS process log, at the following location.

/tmp/vmware-$USER/

You can find the USB arbitrator log file at the following location.

/tmp/vmware-root/