Okay the "# Disk DescriptorFile" section of the monolithicSparse .vmdk file shows ddb.adapterType = "buslogic" and needs to be set to ddb.adapterType = "lsilogic" however if you want to maintain the .vmdk as a monolithicSparse vs. a twoGbMaxExtentSparse type disk then you will not be able to use the directions in the first reply in this thread. So if you want to maintain the .vmdk as a monolithicSparse let me know and I'll have to give to directions otherwise you can use the information in the linked KB.
I have only taken a cursory look at the support bundle and there may be other issues or additional steps needed for a complete resolution however lets correct this first and go from there.
Note: Before doing anything make sure you have a proper* backup of the Virtual Machine Package.
==========
* It is a known fact that Time Machine is not 100% reliable backing up/restoring Virtual Machines under all circumstances/conditions. Also backing up Virtual Machines via Time Machine is disk/time intensive and wastes a tremendous amount of space for something that may be corrupt and worthless come time to restore it. At a minimum I would exclude Virtual Machines from Time Machine and with the Virtual Machines shutdown, not suspended, and VMware Fusion closed then manually copy the Virtual Machines Package(s) to an alternate location, preferably on to a different physical hard disk. Then keep the User Data that is stored within the Virtual Machine backed up off of the Virtual Machine on a regular basis so as to always have a current User Data Backup. If you have to restore a properly backed up Virtual Machine that is not as current at least you'll have a working Virtual Machine and current User Data to go forward with when you find out your Time Machine Backup of the Virtual Machine fails.