I cannot say if its a known issue in fusion but its a known issue in parallels running on mac book air. And the recommendation made is to either shut down the vm or suspend the vm .
If you suspend the fusion I belive you wont be able to replicate the issue on mac book air.
This issue is not reported by Mac book pro users though.
