Damaged File Error Message

[Chodos203]

I am new to Fusion and when I try to start it on my iMac it says -- Bundle "/Users/username/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm" is damaged and cannot be opened. I have not found any solutions to repair the file. Any help is appreciated.

[admin]

1. Go to /Application/Utilities

2. Open Terminal and run the following command

chmod 777 ~/Library/Preferences

After executing the above

command, run Boot camp partition from VMware Fusion Library and verify if

Bootcamp VM can be accessed.

Rick Blythe

Social Media Specialist

VMware Inc.

[admin]

If the problem still

persists, try the following steps in the order given below:

1. Go to /Application/Utilities

2. Open Disk Utility

3. Select Macintosh HD and click on “Repair Disk permissions”

4. Restart Mac system after the completion of Repair Disk process

5. Create a new folder in Mac HDD named “Boot camp”

6. Open the Terminal from /Application/Utilities

7. Run the following command shown below in Terminal

Rick Blythe

Social Media Specialist

VMware Inc.

[admin]

I'd like to add that you should check the permissions for your .vmwarevm itself also.

- Locate your .vmwarevm by it's directory listed in your error.

- Get info on it by Ctrl+Click on the file

- Expand sharing and permissions at the bottom of the Get Info window.

- Verify your user has read and write access

- Verify your use has read and write access to the files contained in the .vmwarevm by Ctrl+clicking on it and choosing show package contents

- You'll want to also check to verify your user and read and write access to the folder structure that virtual machine is in so you'll want to check your documents folder and virtual machines folder.

[Chodos203]

I ran the command. Not clear on how to confirm boot camp is accessible.

[Chodos203]

Thank you. I performed each step but don't see the command I am supposed to run.

I am trying my best to repair the file rather than overwrite or reinstall so I don't lose my information for the past month.

[Chodos203]

Thanks Andrew. All checked out with me having all permissions.

[WoodyZ]

1. Go to /Application/Utilities

2. Open Terminal and run the following command

chmod 777 ~/Library/Preferences

The correct permissions for "~/Library/Preferences" is 755 not 777 and from a Security Standpoint you shouldn't be giving "Everyone" write permissions in this situation nor is it necessary!

After executing the above

command, run Boot camp partition from VMware Fusion Library and verify if

Bootcamp VM can be accessed.

Not sure why your suggesting anything with Boot Camp since it's plainly obvious from the OP that the target Virtual Machine is at "/Users/username/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm" which makes this a normal file based Virtual Machine and nothing to do with Boot Camp.

[WoodyZ]

1. Create a new folder in Mac HDD named “Boot camp”

Not sure why your suggesting anything with Boot Camp since it's plainly obvious from the OP that the target Virtual Machine is at "/Users/username/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm" which makes this a normal file based Virtual Machine and nothing to do with Boot Camp.

[WoodyZ]

I am new to Fusion and when I try to start it on my iMac it says -- Bundle "/Users/username/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm" is damaged and cannot be opened. I have not found any solutions to repair the file. Any help is appreciated.

Have a look at and then provide a file listing as described in the document along with archiving the .log files and the .vmx file.

[Chodos203]

Hi Woody,

Thanks for the comments. As I review the guide I see that the files are not where they are supposed to be. I located the virtual machines folders (Places-User Name-Documents-Virtual Machines). I see a folder (Backup Win-XP) and a file Windows XP Professional.vmwarevm. When I request show package contents all that appears is one folder labelled applications (and contains the various Windows applications). I see no log files to create a log zip.

Attached are the vmware-vmfusion log zip.

In attempting to get a file list via the terminal (ls -lAF/Users/"username"/Documents/Virtual\ Machines.localized ~/Desktop/filelist.txt), error message advised "illegal option." Did I make a mistake with this command?

Best,

Adam

[WoodyZ]

As I review the guide I see that the files are not where they are supposed to be. I located the virtual machines folders (Places-User Name-Documents-Virtual Machines). I see a folder (Backup Win-XP) and a file Windows XP Professional.vmwarevm. When I request show package contents all that appears is one folder labelled applications (and contains the various Windows applications). I see no log files to create a log zip.

Attached are the vmware-vmfusion log zip.

To help figure out what is what the best way to provide comprehensive diagnostic information is to use the "Collect Support Information" command from the VMware Fusion (menu bar) > Help > Collect Support Information and then attach the .tgz file it created on your Desktop.

In attempting to get a file list via the terminal (ls -lAF/Users/"username"/Documents/Virtual\ Machines.localized ~/Desktop/filelist.txt), error message advised "illegal option." Did I make a mistake with this command?

You're not including ">" in the command... The syntax is as follows:

ls -lAF /Users/${USER}/Documents/Virtual\ Machines.localized/Virtual_Machine_Name.vmwarevm > ~/Desktop/filelist.txt

[Chodos203]

Hi Woody,

Attached please find the tgz zip and the filelist.

Thanks,

Adam

[WoodyZ]

Still not getting the information needed...

1. The file listing is not being made correctly as shown in the document.

2. For some reason the Collect Support Information command failed to include the needed files from within the Virtual Machine Document Package.

If the information in the /Users/$/Library/Preferences/com.vmware.fusion.plist file is correct then the Virtual Machine is located at the following location:

/Users/adamchodos/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm

So in a Terminal copy and paste the following command and then press enter.

ls -lAF /Users/adamchodos/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm  > ~/Desktop/filelist.txt

Next using the information in the document you need to archive and attach the following files that are within the Virtual Machine Document Package.

The following files should have been picked up using the Collect Support Information command but were not.

All files with a .log extension (vmware.log and vmware-n.log when -n is a number.)

The .vmx file.

The .vmsd file.

Without this information I do not have the information needed to effectively troubleshoot the issue.

[Chodos203]

Hi Woody,

I redid the filelist per the terminal, but it appears to be the same.

I redid the tgz file as well - is this more complete? Since I can't launch Fusion (the core problem) to reach the Collect Support Information tool, I went through finder (Mac HD/Library/Application Support/VMware Fusion/vm-support.tool) to generate the file.

Best,

Adam

[WoodyZ]

The .tgz doesn't contain the requested files from within the Virtual Machine Document Package and should although if you can't even open the Fusion application at this point then it sounds like the problem has progressed beyond not being able to run the Virtual Machine and if that is the case then I'd uninstall/reinstall Fusion however before you do that try to get the files I've requested by going directly through Finder and try the file listing again with the following command as I've added quotes when I left them off in the last reply, sorry.

ls -lAF "/Users/adamchodos/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm" > ~/Desktop/filelist.txt

[Chodos203]

The inability to open Fusion is the main issue and I hate to reinstall as I would lose all the outlook activity and work for past several weeks. I redid the file list with a simple cut and paste (attached) though it looks the same. I am no expert, but what seems odd is when I go into the vmwarevm package info all I see is a folder for applications and no other files. Possible the files are in a wrong location causing the software not to run? Not sure how this happened as Fusion was operating for a month without any issue. A few days prior to it not opening it would not suspend properly. I used a force quit to hopefully restart and eliminate the problem, but it hasn't opened since then.

[WoodyZ]

The inability to open Fusion is the main issue and I hate to reinstall as I would lose all the outlook activity and work for past several weeks.

Well first of all uninstalling/reinstalling VMware Fusion doesn't touch the Virtual Machines unless you've upgraded and then it's either upgrading hardware and or upgrading VMware Tools but in general uninstalling/reinstalling VMware Fusion doesn't touch the Virtual Machines in that it would not delete then just because you uninstalled Fusion. Franky I fail to see why anyone would think that uninstalling/reinstalling VMware Fusion would delete the Virtual Machines. No major application that I know of does such a thing and beside that a Virtual Machine is no different in it's relationship to Fusion as a Word Document is to Microsoft Office in that both are the work product of the application and uninstalling Office doesn't delete the documents created by it nor does uninstalling Fusion delete the Virtual Machine's it creates or runs from other sources.

Also if you can't actually start Fusion the application not the actual Virtual Machine, as these are two entirely separate things, then it doesn't matter because you will need to uninstall/reinstall Fusion to get Fusion working but the Virtual machine is a whole different story.

I redid the file list with a simple cut and paste (attached) though it looks the same.

They are not the same as it plainly obvious the ls command was reading two different directories.

I am no expert, but what seems odd is when I go into the vmwarevm package info all I see is a folder for applications and no other files. Possible the files are in a wrong location causing the software not to run? Not sure how this happened as Fusion was operating for a month without any issue. A few days prior to it not opening it would not suspend properly. I used a force quit to hopefully restart and eliminate the problem, but it hasn't opened since then.

Well I hate to tell you this and it explains why the expected files were not in the .tgz file but you do not have a Virtual Machine anymore as the actual files that comprise the Virtual Machine are gone as they are no longer in the Virtual Machine Document Package.

[jmcelroy]

I am new to Fusion and when I try to start it on my iMac it says -- Bundle "/Users/username/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm" is damaged and cannot be opened. I have not found any solutions to repair the file. Any help is appreciated.

Have a look at and then provide a file listing as described in the document along with archiving the .log files and the .vmx file.

Hi - I'm having same problem (damaged and cannot be opened).

In my case I appear to have an error with my permissions - in OSX my VM file is 0 kb (and when I view the package it appears empty) even though based on my available HD space the VM file is still there (it's around 40 GB, so if it had suddenly gone to 0, I'd have much more free HD space than I do have).

I have verified that my user account does have read/write permissions for the file as it appears in OSX.

When I tried doing a file listing as explained in DOC-8720, I get the following, suggesting that my virtual file is still intact, but I need to fix the permissions for it.

s: .dat0193.000: Permission denied

ls: .dat0193.001: Permission denied

ls: .dat0193.002: Permission denied

ls: .dat0193.003: Permission denied

ls: .dat4c91.000: Permission denied

ls: .dat4c91.001: Permission denied

ls: .dat4c91.002: Permission denied

ls: .dat4c91.003: Permission denied

ls: .dat6206.000: Permission denied

ls: .dat6206.001: Permission denied

ls: .dat6206.002: Permission denied

ls: .dat6206.003: Permission denied

ls: .dat6206.004: Permission denied

ls: .dat6206.005: Permission denied

ls: .dat6206.006: Permission denied

ls: .dat6206.007: Permission denied

ls: .dat6206.008: Permission denied

ls: .dat6206.009: Permission denied

ls: .vmBigFileTest0: Permission denied

ls: .vmBigFileTest1: Permission denied

ls: .vmBigFileTest10: Permission denied

ls: .vmBigFileTest100: Permission denied

ls: .vmBigFileTest101: Permission denied

ls: .vmBigFileTest102: Permission denied

ls: .vmBigFileTest103: Permission denied

ls: .vmBigFileTest104: Permission denied

ls: .vmBigFileTest105: Permission denied

ls: .vmBigFileTest106: Permission denied

ls: .vmBigFileTest107: Permission denied

ls: .vmBigFileTest108: Permission denied

ls: .vmBigFileTest109: Permission denied

ls: .vmBigFileTest11: Permission denied

ls: .vmBigFileTest110: Permission denied

ls: .vmBigFileTest111: Permission denied

ls: .vmBigFileTest112: Permission denied

ls: .vmBigFileTest113: Permission denied

ls: .vmBigFileTest114: Permission denied

ls: .vmBigFileTest115: Permission denied

ls: .vmBigFileTest116: Permission denied

ls: .vmBigFileTest117: Permission denied

ls: .vmBigFileTest118: Permission denied

ls: .vmBigFileTest119: Permission denied

ls: .vmBigFileTest12: Permission denied

ls: .vmBigFileTest120: Permission denied

ls: .vmBigFileTest121: Permission denied

ls: .vmBigFileTest122: Permission denied

ls: .vmBigFileTest123: Permission denied

ls: .vmBigFileTest124: Permission denied

ls: .vmBigFileTest125: Permission denied

ls: .vmBigFileTest126: Permission denied

ls: .vmBigFileTest127: Permission denied

ls: .vmBigFileTest128: Permission denied

ls: .vmBigFileTest129: Permission denied

ls: .vmBigFileTest13: Permission denied

ls: .vmBigFileTest130: Permission denied

ls: .vmBigFileTest131: Permission denied

ls: .vmBigFileTest132: Permission denied

ls: .vmBigFileTest133: Permission denied

ls: .vmBigFileTest134: Permission denied

ls: .vmBigFileTest135: Permission denied

ls: .vmBigFileTest136: Permission denied

ls: .vmBigFileTest137: Permission denied

ls: .vmBigFileTest138: Permission denied

ls: .vmBigFileTest139: Permission denied

ls: .vmBigFileTest14: Permission denied

ls: .vmBigFileTest140: Permission denied

ls: .vmBigFileTest141: Permission denied

ls: .vmBigFileTest142: Permission denied

ls: .vmBigFileTest143: Permission denied

ls: .vmBigFileTest144: Permission denied

ls: .vmBigFileTest145: Permission denied

ls: .vmBigFileTest146: Permission denied

ls: .vmBigFileTest147: Permission denied

ls: .vmBigFileTest148: Permission denied

ls: .vmBigFileTest149: Permission denied

ls: .vmBigFileTest15: Permission denied

ls: .vmBigFileTest150: Permission denied

ls: .vmBigFileTest151: Permission denied

ls: .vmBigFileTest152: Permission denied

ls: .vmBigFileTest153: Permission denied

ls: .vmBigFileTest154: Permission denied

ls: .vmBigFileTest155: Permission denied

ls: .vmBigFileTest156: Permission denied

ls: .vmBigFileTest157: Permission denied

ls: .vmBigFileTest158: Permission denied

ls: .vmBigFileTest159: Permission denied

ls: .vmBigFileTest16: Permission denied

ls: .vmBigFileTest160: Permission denied

ls: .vmBigFileTest161: Permission denied

ls: .vmBigFileTest162: Permission denied

ls: .vmBigFileTest163: Permission denied

ls: .vmBigFileTest164: Permission denied

ls: .vmBigFileTest165: Permission denied

ls: .vmBigFileTest166: Permission denied

ls: .vmBigFileTest167: Permission denied

ls: .vmBigFileTest168: Permission denied

ls: .vmBigFileTest169: Permission denied

ls: .vmBigFileTest17: Permission denied

ls: .vmBigFileTest170: Permission denied

ls: .vmBigFileTest171: Permission denied

ls: .vmBigFileTest172: Permission denied

ls: .vmBigFileTest173: Permission denied

ls: .vmBigFileTest174: Permission denied

ls: .vmBigFileTest175: Permission denied

ls: .vmBigFileTest176: Permission denied

ls: .vmBigFileTest177: Permission denied

ls: .vmBigFileTest178: Permission denied

ls: .vmBigFileTest179: Permission denied

ls: .vmBigFileTest18: Permission denied

ls: .vmBigFileTest180: Permission denied

ls: .vmBigFileTest181: Permission denied

ls: .vmBigFileTest182: Permission denied

ls: .vmBigFileTest183: Permission denied

ls: .vmBigFileTest184: Permission denied

ls: .vmBigFileTest185: Permission denied

ls: .vmBigFileTest186: Permission denied

ls: .vmBigFileTest187: Permission denied

ls: .vmBigFileTest188: Permission denied

ls: .vmBigFileTest189: Permission denied

ls: .vmBigFileTest19: Permission denied

ls: .vmBigFileTest190: Permission denied

ls: .vmBigFileTest191: Permission denied

ls: .vmBigFileTest192: Permission denied

ls: .vmBigFileTest193: Permission denied

ls: .vmBigFileTest194: Permission denied

ls: .vmBigFileTest195: Permission denied

ls: .vmBigFileTest196: Permission denied

ls: .vmBigFileTest197: Permission denied

ls: .vmBigFileTest198: Permission denied

ls: .vmBigFileTest199: Permission denied

ls: .vmBigFileTest2: Permission denied

ls: .vmBigFileTest20: Permission denied

ls: .vmBigFileTest200: Permission denied

ls: .vmBigFileTest201: Permission denied

ls: .vmBigFileTest202: Permission denied

ls: .vmBigFileTest203: Permission denied

ls: .vmBigFileTest204: Permission denied

ls: .vmBigFileTest205: Permission denied

ls: .vmBigFileTest206: Permission denied

ls: .vmBigFileTest207: Permission denied

ls: .vmBigFileTest208: Permission denied

ls: .vmBigFileTest209: Permission denied

ls: .vmBigFileTest21: Permission denied

ls: .vmBigFileTest210: Permission denied

ls: .vmBigFileTest211: Permission denied

ls: .vmBigFileTest212: Permission denied

ls: .vmBigFileTest213: Permission denied

ls: .vmBigFileTest214: Permission denied

ls: .vmBigFileTest215: Permission denied

ls: .vmBigFileTest216: Permission denied

ls: .vmBigFileTest217: Permission denied

ls: .vmBigFileTest218: Permission denied

ls: .vmBigFileTest219: Permission denied

ls: .vmBigFileTest22: Permission denied

ls: .vmBigFileTest220: Permission denied

ls: .vmBigFileTest221: Permission denied

ls: .vmBigFileTest222: Permission denied

ls: .vmBigFileTest223: Permission denied

ls: .vmBigFileTest224: Permission denied

ls: .vmBigFileTest225: Permission denied

ls: .vmBigFileTest226: Permission denied

ls: .vmBigFileTest227: Permission denied

ls: .vmBigFileTest228: Permission denied

ls: .vmBigFileTest229: Permission denied

ls: .vmBigFileTest23: Permission denied

ls: .vmBigFileTest230: Permission denied

ls: .vmBigFileTest231: Permission denied

ls: .vmBigFileTest232: Permission denied

ls: .vmBigFileTest233: Permission denied

ls: .vmBigFileTest234: Permission denied

ls: .vmBigFileTest235: Permission denied

ls: .vmBigFileTest236: Permission denied

ls: .vmBigFileTest237: Permission denied

ls: .vmBigFileTest238: Permission denied

ls: .vmBigFileTest239: Permission denied

ls: .vmBigFileTest24: Permission denied

ls: .vmBigFileTest240: Permission denied

ls: .vmBigFileTest241: Permission denied

ls: .vmBigFileTest242: Permission denied

ls: .vmBigFileTest243: Permission denied

ls: .vmBigFileTest244: Permission denied

ls: .vmBigFileTest245: Permission denied

ls: .vmBigFileTest246: Permission denied

ls: .vmBigFileTest247: Permission denied

ls: .vmBigFileTest248: Permission denied

ls: .vmBigFileTest249: Permission denied

ls: .vmBigFileTest25: Permission denied

ls: .vmBigFileTest250: Permission denied

ls: .vmBigFileTest251: Permission denied

ls: .vmBigFileTest252: Permission denied

ls: .vmBigFileTest253: Permission denied

ls: .vmBigFileTest254: Permission denied

ls: .vmBigFileTest255: Permission denied

ls: .vmBigFileTest256: Permission denied

ls: .vmBigFileTest257: Permission denied

ls: .vmBigFileTest258: Permission denied

ls: .vmBigFileTest259: Permission denied

ls: .vmBigFileTest26: Permission denied

ls: .vmBigFileTest260: Permission denied

ls: .vmBigFileTest261: Permission denied

ls: .vmBigFileTest262: Permission denied

ls: .vmBigFileTest263: Permission denied

ls: .vmBigFileTest264: Permission denied

ls: .vmBigFileTest265: Permission denied

ls: .vmBigFileTest266: Permission denied

ls: .vmBigFileTest267: Permission denied

ls: .vmBigFileTest268: Permission denied

ls: .vmBigFileTest269: Permission denied

ls: .vmBigFileTest27: Permission denied

ls: .vmBigFileTest270: Permission denied

ls: .vmBigFileTest271: Permission denied

ls: .vmBigFileTest272: Permission denied

ls: .vmBigFileTest273: Permission denied

ls: .vmBigFileTest274: Permission denied

ls: .vmBigFileTest275: Permission denied

ls: .vmBigFileTest276: Permission denied

ls: .vmBigFileTest277: Permission denied

ls: .vmBigFileTest278: Permission denied

ls: .vmBigFileTest279: Permission denied

ls: .vmBigFileTest28: Permission denied

ls: .vmBigFileTest280: Permission denied

ls: .vmBigFileTest281: Permission denied

ls: .vmBigFileTest282: Permission denied

ls: .vmBigFileTest283: Permission denied

ls: .vmBigFileTest284: Permission denied

ls: .vmBigFileTest285: Permission denied

ls: .vmBigFileTest286: Permission denied

ls: .vmBigFileTest287: Permission denied

ls: .vmBigFileTest288: Permission denied

ls: .vmBigFileTest289: Permission denied

ls: .vmBigFileTest29: Permission denied

ls: .vmBigFileTest290: Permission denied

ls: .vmBigFileTest291: Permission denied

ls: .vmBigFileTest292: Permission denied

ls: .vmBigFileTest293: Permission denied

ls: .vmBigFileTest294: Permission denied

ls: .vmBigFileTest295: Permission denied

ls: .vmBigFileTest296: Permission denied

ls: .vmBigFileTest297: Permission denied

ls: .vmBigFileTest298: Permission denied

ls: .vmBigFileTest299: Permission denied

ls: .vmBigFileTest3: Permission denied

ls: .vmBigFileTest30: Permission denied

ls: .vmBigFileTest300: Permission denied

ls: .vmBigFileTest301: Permission denied

ls: .vmBigFileTest302: Permission denied

ls: .vmBigFileTest303: Permission denied

ls: .vmBigFileTest304: Permission denied

ls: .vmBigFileTest305: Permission denied

ls: .vmBigFileTest306: Permission denied

ls: .vmBigFileTest307: Permission denied

ls: .vmBigFileTest308: Permission denied

ls: .vmBigFileTest309: Permission denied

ls: .vmBigFileTest31: Permission denied

ls: .vmBigFileTest310: Permission denied

ls: .vmBigFileTest311: Permission denied

ls: .vmBigFileTest312: Permission denied

ls: .vmBigFileTest313: Permission denied

ls: .vmBigFileTest314: Permission denied

ls: .vmBigFileTest315: Permission denied

ls: .vmBigFileTest316: Permission denied

ls: .vmBigFileTest317: Permission denied

ls: .vmBigFileTest318: Permission denied

ls: .vmBigFileTest319: Permission denied

ls: .vmBigFileTest32: Permission denied

ls: .vmBigFileTest320: Permission denied

ls: .vmBigFileTest321: Permission denied

ls: .vmBigFileTest322: Permission denied

ls: .vmBigFileTest323: Permission denied

ls: .vmBigFileTest324: Permission denied

ls: .vmBigFileTest325: Permission denied

ls: .vmBigFileTest326: Permission denied

ls: .vmBigFileTest327: Permission denied

ls: .vmBigFileTest328: Permission denied

ls: .vmBigFileTest329: Permission denied

ls: .vmBigFileTest33: Permission denied

ls: .vmBigFileTest330: Permission denied

ls: .vmBigFileTest331: Permission denied

ls: .vmBigFileTest332: Permission denied

ls: .vmBigFileTest333: Permission denied

ls: .vmBigFileTest334: Permission denied

ls: .vmBigFileTest335: Permission denied

ls: .vmBigFileTest336: Permission denied

ls: .vmBigFileTest337: Permission denied

ls: .vmBigFileTest338: Permission denied

ls: .vmBigFileTest339: Permission denied

ls: .vmBigFileTest34: Permission denied

ls: .vmBigFileTest340: Permission denied

ls: .vmBigFileTest341: Permission denied

ls: .vmBigFileTest342: Permission denied

ls: .vmBigFileTest343: Permission denied

ls: .vmBigFileTest344: Permission denied

ls: .vmBigFileTest345: Permission denied

ls: .vmBigFileTest346: Permission denied

ls: .vmBigFileTest347: Permission denied

ls: .vmBigFileTest348: Permission denied

ls: .vmBigFileTest349: Permission denied

ls: .vmBigFileTest35: Permission denied

ls: .vmBigFileTest350: Permission denied

ls: .vmBigFileTest351: Permission denied

ls: .vmBigFileTest352: Permission denied

ls: .vmBigFileTest353: Permission denied

ls: .vmBigFileTest354: Permission denied

ls: .vmBigFileTest355: Permission denied

ls: .vmBigFileTest356: Permission denied

ls: .vmBigFileTest357: Permission denied

ls: .vmBigFileTest358: Permission denied

ls: .vmBigFileTest359: Permission denied

ls: .vmBigFileTest36: Permission denied

ls: .vmBigFileTest360: Permission denied

ls: .vmBigFileTest361: Permission denied

ls: .vmBigFileTest362: Permission denied

ls: .vmBigFileTest363: Permission denied

ls: .vmBigFileTest364: Permission denied

ls: .vmBigFileTest365: Permission denied

ls: .vmBigFileTest366: Permission denied

ls: .vmBigFileTest367: Permission denied

ls: .vmBigFileTest368: Permission denied

ls: .vmBigFileTest369: Permission denied

ls: .vmBigFileTest37: Permission denied

ls: .vmBigFileTest370: Permission denied

ls: .vmBigFileTest371: Permission denied

ls: .vmBigFileTest372: Permission denied

ls: .vmBigFileTest373: Permission denied

ls: .vmBigFileTest374: Permission denied

ls: .vmBigFileTest375: Permission denied

ls: .vmBigFileTest376: Permission denied

ls: .vmBigFileTest377: Permission denied

ls: .vmBigFileTest378: Permission denied

ls: .vmBigFileTest379: Permission denied

ls: .vmBigFileTest38: Permission denied

ls: .vmBigFileTest380: Permission denied

ls: .vmBigFileTest381: Permission denied

ls: .vmBigFileTest382: Permission denied

ls: .vmBigFileTest383: Permission denied

ls: .vmBigFileTest384: Permission denied

ls: .vmBigFileTest385: Permission denied

ls: .vmBigFileTest386: Permission denied

ls: .vmBigFileTest387: Permission denied

ls: .vmBigFileTest388: Permission denied

ls: .vmBigFileTest389: Permission denied

ls: .vmBigFileTest39: Permission denied

ls: .vmBigFileTest390: Permission denied

ls: .vmBigFileTest391: Permission denied

ls: .vmBigFileTest392: Permission denied

ls: .vmBigFileTest393: Permission denied

ls: .vmBigFileTest394: Permission denied

ls: .vmBigFileTest4: Permission denied

ls: .vmBigFileTest40: Permission denied

ls: .vmBigFileTest41: Permission denied

ls: .vmBigFileTest42: Permission denied

ls: .vmBigFileTest43: Permission denied

ls: .vmBigFileTest44: Permission denied

ls: .vmBigFileTest45: Permission denied

ls: .vmBigFileTest46: Permission denied

ls: .vmBigFileTest47: Permission denied

ls: .vmBigFileTest48: Permission denied

ls: .vmBigFileTest49: Permission denied

ls: .vmBigFileTest5: Permission denied

ls: .vmBigFileTest50: Permission denied

ls: .vmBigFileTest51: Permission denied

ls: .vmBigFileTest52: Permission denied

ls: .vmBigFileTest53: Permission denied

ls: .vmBigFileTest54: Permission denied

ls: .vmBigFileTest55: Permission denied

ls: .vmBigFileTest56: Permission denied

ls: .vmBigFileTest57: Permission denied

ls: .vmBigFileTest58: Permission denied

ls: .vmBigFileTest59: Permission denied

ls: .vmBigFileTest6: Permission denied

ls: .vmBigFileTest60: Permission denied

ls: .vmBigFileTest61: Permission denied

ls: .vmBigFileTest62: Permission denied

ls: .vmBigFileTest63: Permission denied

ls: .vmBigFileTest64: Permission denied

ls: .vmBigFileTest65: Permission denied

ls: .vmBigFileTest66: Permission denied

ls: .vmBigFileTest67: Permission denied

ls: .vmBigFileTest68: Permission denied

ls: .vmBigFileTest69: Permission denied

ls: .vmBigFileTest7: Permission denied

ls: .vmBigFileTest70: Permission denied

ls: .vmBigFileTest71: Permission denied

ls: .vmBigFileTest72: Permission denied

ls: .vmBigFileTest73: Permission denied

ls: .vmBigFileTest74: Permission denied

ls: .vmBigFileTest75: Permission denied

ls: .vmBigFileTest76: Permission denied

ls: .vmBigFileTest77: Permission denied

ls: .vmBigFileTest78: Permission denied

ls: .vmBigFileTest79: Permission denied

ls: .vmBigFileTest8: Permission denied

ls: .vmBigFileTest80: Permission denied

ls: .vmBigFileTest81: Permission denied

ls: .vmBigFileTest82: Permission denied

ls: .vmBigFileTest83: Permission denied

ls: .vmBigFileTest84: Permission denied

ls: .vmBigFileTest85: Permission denied

ls: .vmBigFileTest86: Permission denied

ls: .vmBigFileTest87: Permission denied

ls: .vmBigFileTest88: Permission denied

ls: .vmBigFileTest89: Permission denied

ls: .vmBigFileTest9: Permission denied

ls: .vmBigFileTest90: Permission denied

ls: .vmBigFileTest91: Permission denied

ls: .vmBigFileTest92: Permission denied

ls: .vmBigFileTest93: Permission denied

ls: .vmBigFileTest94: Permission denied

ls: .vmBigFileTest95: Permission denied

ls: .vmBigFileTest96: Permission denied

ls: .vmBigFileTest97: Permission denied

ls: .vmBigFileTest98: Permission denied

ls: .vmBigFileTest99: Permission denied

ls: 564d69a5-d342-b896-6549-08b061ab499c.vmem: Permission denied

ls: 564d69a5-d342-b896-6549-08b061ab499c.vmem.lck: Permission denied

ls: Applications: Permission denied

ls: XP Professional-s001.vmdk: Permission denied

ls: XP Professional-s002.vmdk: Permission denied

ls: XP Professional-s003.vmdk: Permission denied

ls: XP Professional-s004.vmdk: Permission denied

ls: XP Professional-s005.vmdk: Permission denied

ls: XP Professional-s006.vmdk: Permission denied

ls: XP Professional-s007.vmdk: Permission denied

ls: XP Professional-s008.vmdk: Permission denied

ls: XP Professional-s009.vmdk: Permission denied

ls: XP Professional-s010.vmdk: Permission denied

ls: XP Professional-s011.vmdk: Permission denied

ls: XP Professional-s012.vmdk: Permission denied

ls: XP Professional-s013.vmdk: Permission denied

ls: XP Professional-s014.vmdk: Permission denied

ls: XP Professional-s015.vmdk: Permission denied

ls: XP Professional-s016.vmdk: Permission denied

ls: XP Professional-s017.vmdk: Permission denied

ls: XP Professional-s018.vmdk: Permission denied

ls: XP Professional-s019.vmdk: Permission denied

ls: XP Professional-s020.vmdk: Permission denied

ls: XP Professional-s021.vmdk: Permission denied

ls: XP Professional.nvram: Permission denied

ls: XP Professional.vmdk: Permission denied

ls: XP Professional.vmdk.lck: Permission denied

ls: XP Professional.vmem: Permission denied

ls: XP Professional.vmem.lck: Permission denied

ls: XP Professional.vmsd: Permission denied

ls: XP Professional.vmsd.lck: Permission denied

ls: XP Professional.vmss: Permission denied

ls: XP Professional.vmx: Permission denied

ls: XP Professional.vmx.lck: Permission denied

ls: XP Professional.vmxf: Permission denied

ls: quicklook-cache.png: Permission denied

ls: vmware-0.log: Permission denied

ls: vmware-1.log: Permission denied

ls: vmware-2.log: Permission denied

ls: vmware.log: Permission denied

[jmcelroy]

logfiles attached