Error: 209 (type: 1, code: 13)'ĭigging around all over the internet for vmware-related converter failures, I find a TON of threads referencing bad blocks on the source side as being the cause of those. Things are cruising along for a few minutes until I hit 5% and then I get this ugly error: FAILED: An error occurred during the conversion: 'BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=. Okay, the moment of truth, I fire up the vCenter Converter, select convert online machine, select local machine, accept the default options, hit Go. I drag and drop about 20 gigs worth of files on the PC to the Mac since I wanted them native on the Mac anyway and I don’t plan to use Fusion’s folder sharing features those came over nice and fast, no issues. I map a drive to it from the Windows 7 box. I set up an SMB file share on my Mac mapped to my Fusion Virtual Machines folder on my RAID array. This meant using the VMware vCenter Converter to P2V it instead of the Fusion PC Migration thing. I want a true byte by byte image of my old Windows 7 system so all my metadata (drive perms, ownership, etc) is preserved. I buy a nice copy of VMware Fusion Pro 7 for Mac with the intent of virtualizing my old desktop since it still has some apps on it that I need, like Visio (WTF, can someone please develop a true Visio equivalent for Mac?). This is a very kick ass Thunderbolt-based disk array by the way $2200 on Amazon currently: I added a G-Technology G-Speed Studio 12TB (9 usable under RAID 5) external storage array to store all my crap from the Dell. I recently switched from a big honkin’ Dell XPS ‘gaming’ desktop computer to an iMac with additional Thunderbolt monitor as my home rig.
0 kommentar(er)
