Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 219257

Re: Locked Fusion 8.5 .vmdk file running virtual Windows 7 on MacOS Sierra

$
0
0

Thanks a.p.!!

 

Your solution is spot on.

 

Here is a detailed account that others might find useful (and perhaps you find amusing).

 

Although I lacked a backup before getting into the suspended state, I backed up the troubled VM and after spending quite a bit of time mulling over your posted solution (Unable to open .vmdk file. One of the disks in this virtual machine is already in use by a virtual machine or by a snapshot ) and fiddling, I got it working again this morning after a bit of sleep.   Without that thread, I definitely would have need to ask for more help from your solution on my thread. The stalling point for me was my lack of command line experience in Mac OS.  I couldn't locate the files analogous to those you mentioned in that prior post.  I wasn't working from command line and I didn't realize the Windows 7.vmwarevm file is really a directory with all the files hidden.  I was unfamiliar with the term VMBundle and I had never noticed (let alone used) "Show Package Contents" on a Mac.  (A bit mind boggling since I have used Macs regularly; albeit mostly  mindlessly, since the early 1990's.) 

Since I am more comfortablish in the Windows environment, I finally decided to try using remote access  (GoToMyPC) to transfer the Windows 7.vmwarevm 'file' onto a native Windows box to give it a closer look.  It was good fortune that the GoToMyPC file transfer tool by default showed the hidden files that make up the VMBundle.  I immediately noticed these were the files your prior post referred to, which got me trying to figure out how to see them on the Mac and I found the hidden in plain sight "Show Package Contents".  It took a few attempts to get the correct files since my VM was actually split into multiple .vmdk files, so keeping just the biggest was insufficient.  Thankfully the backed up files allowed me to re-add the critical ones I had mistakenly deleted.

Once I got the bundle down to the correct critical files (in my case:

Windows 7-000005.vmdk

Windows 7-000006.vmdk

Windows 7.vmdk

Windows 7.vmx

Windows 7.vmxf

) the VM was again working nicely.

 

Thanks again!


Viewing all articles
Browse latest Browse all 219257

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>