VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
1 Replies Last post: Sep 26, 2008 2:36 PM by sudarsan  

Controlling logging and tracing of VDDK? posted: Sep 26, 2008 8:08 AM

Click to view rcardona2k's profile Champion 5,197 posts since
Oct 20, 2005
I'm looking for any documentation that has examples for increasing the debug level of accessing VMDKs through the VDDK. In particular I'm getting strange file permissions problems:

Insufficient permission to access file (38)

But there is not enough verbose logging to find the source, i.e. the vmdk or the -flat.vmdk. Permissions look OK.

The operations being attempted are conversions and transferring to remote hosts. It could be useful to have exact information on which file part(s), directories, or if this a source or remote host permission problem. There is not enough information on failure and many files and directories are involved.

Also if anyone has information on increasing vmware-disklib logging in either ESX 3.x or Workstation using disklib.tracelevel that would be helpful.

Re: Controlling logging and tracing of VDDK?

1. Sep 26, 2008 2:36 PM in response to: rcardona2k
Click to view sudarsan's profile Expert 263 posts since
Sep 20, 2006
Can you tell me where you see this problem (i.e. which function returns you the eqvt. error code)?

VixDiskLib logging is thru the logging function you pass back.

ESX logs are available on host at /var/log/VMware/hostd.log.

-Sudarsan

Developer Social Media

Communities