Fusion 6.0.2 VM startup fails: VmdbPipeStreamsOvlError

[safrank]

Using Fusion 6.0.2, OS X 10.9.2, trying to start VM returns "Internal Error". Other recent posts with that issue don't help. I repaired permissions, rebooted, reinstalled Fusion, and created a fresh fedora VM, same error.

All support files attached.

The key may be line with VmdbPipeStreamsOvlError Couldn't read: OVL_STATUS_EOF, (3) No such process.:

2014-03-02T10:40:47.975-08:00| VMware Fusion| I120: /Volumes/Extra/Fusion/fedora64.vmwarevm/fedora64.vmx: VMHS: VM /Volumes/Extra/Fusion/fedora64.vmwarevm/fedora64.vmx in directory /Volumes/Extra/Fusion/fedora64.vmwarevm

2014-03-02T10:40:47.975-08:00| VMware Fusion| I120: /Volumes/Extra/Fusion/fedora64.vmwarevm/fedora64.vmx: VMHS: Exec()'ing /Applications/VMware Fusion.app/Contents/Library/vmware-vmx-debug.

2014-03-02T10:40:47.985-08:00| VMware Fusion| I120: VmdbAddConnection: cnxPath=/db/connection/#8a/, cnxIx=1

2014-03-02T10:40:47.985-08:00| VMware Fusion| I120: Vmdb_AddConnectionAsync_Secure: registered VERSION completion callback, cnx = /db/connection/#8a/

2014-03-02T10:40:48.001-08:00| VMware Fusion| I120: OnVMStateChanged: alive = 1

2014-03-02T10:40:48.001-08:00| VMware Fusion| I120: SetAttached: detach

2014-03-02T10:40:48.001-08:00| VMware Fusion| I120: OnSetAttachedCompleted

2014-03-02T10:40:48.007-08:00| VMware Fusion| I120: VmdbPipeStreamsOvlError Couldn't read: OVL_STATUS_EOF, (3) No such process.

2014-03-02T10:40:48.007-08:00| VMware Fusion| I120: VmdbCnxDisconnect: Disconnect: closed pipe for sub cnx '/db/connection/#8a/' (-32)

2014-03-02T10:40:48.007-08:00| VMware Fusion| I120: /Volumes/Extra/Fusion/fedora64.vmwarevm/fedora64.vmx: VMX did not report err via stderr

2014-03-02T10:40:48.007-08:00| VMware Fusion| I120: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#8a/'

2014-03-02T10:40:48.008-08:00| VMware Fusion| I120: /Volumes/Extra/Fusion/fedora64.vmwarevm/fedora64.vmx: Pending power op found, completing.

2014-03-02T10:40:48.008-08:00| VMware Fusion| I120: /Volumes/Extra/Fusion/fedora64.vmwarevm/fedora64.vmx: Clearing execReqPath

2014-03-02T10:40:48.008-08:00| VMware Fusion| I120: /Volumes/Extra/Fusion/fedora64.vmwarevm/fedora64.vmx: Reloading config state.

2014-03-02T10:40:48.019-08:00| VMware Fusion| I120: VMHS: Transitioned vmx/execState/val to poweredOff

2014-03-02T10:40:48.021-08:00| VMware Fusion| I120: /Volumes/Extra/Fusion/fedora64.vmwarevm/fedora64.vmx: VMHSStartVmxVigorCb: vmPath=/vm/#9956b7a83b145622/ status=error

2014-03-02T10:40:48.021-08:00| VMware Fusion| I120: /Volumes/Extra/Fusion/fedora64.vmwarevm/fedora64.vmx: Reloading config state.

2014-03-02T10:40:48.030-08:00| VMware Fusion| I120: VMHS: Transitioned vmx/execState/val to poweredOff

2014-03-02T10:40:48.032-08:00| VMware Fusion| I120: Internal VMDB error: VMDB failure (-1)

[safrank]

Solved. I reset permissions on directories containing VMs. I think it was an ownership issue on a directory containing the VMs. I previously had rw permission, but was not the directory owner. Previously that was not a problem, but seemed to cause a problem after 109.2 update.