1 2 Previous Next 18 Replies Latest reply on Mar 15, 2017 11:12 AM by dwc Branched to a new discussion.

    Internal Error While Starting Virtual Machine After Crash

    unit1346 Novice

      I'm running Yosemite and while running a virtual machine of Windows 7 it suddenly stopped working. The beach ball cursor spun for half an hour and I had force quit Fusion 7. While trying to run the virtual machine again I get a generic "Internal Error" message.

       

      Already tried: restarting my Mac, repairing the permissions, uninstalling/reinstalling Fusion 7, even trying repairing the main VMDK file (it is split and returned with no errors).

       

      Any suggestions?

        • 2. Re: Internal Error While Starting Virtual Machine After Crash
          dariusd Virtuoso
          User ModeratorsVMware Employees

          Have you tried updating Fusion to the latest version?  Your log is from Fusion 7.0.0, and we're currently up to 7.1.1.  The latest version in particular addresses a nasty problem with Shared Folders and OS X 10.10.2.

           

          Cheers,

          --

          Darius

          • 3. Re: Internal Error While Starting Virtual Machine After Crash
            unit1346 Novice

            I don't know why the log says I'm using Fusion 7.0.0 but I'm running 7.1.1. The problem occurred quite some time after upgrading.

            • 4. Re: Internal Error While Starting Virtual Machine After Crash
              dariusd Virtuoso
              VMware EmployeesUser Moderators

              The log (from February 23) is most definitely from Fusion 7.0.0, so if you are sure you have upgraded to 7.1.1 before that date, something has gone very wrong with the upgrade that has left your machine still running the old version.  The "Internal Error" could very well be a result of a incomplete upgrade.

               

              My recommendation would be to install a completely fresh copy of Fusion, as follows:

               

              • Quit out of VMware Fusion entirely, then use Finder to drag the VMware Fusion application to the trash.
              • Reboot your Mac.  (An inconsistent installation could leave some components running, which would interfere with a later attempt to run Fusion.)
              • Use Disk Utility to verify (and if necessary repair) your Mac's disk(s).
              • Download a fresh copy of VMware Fusion 7 (that link should currently give you Fusion 7.1.1, the latest available).
              • Launch Fusion from the downloaded disk image and let it install itself to your Applications folder.
              • Try to power on your virtual machine again.

               

              Let us know if that resolves the problem there!

               

              Cheers,

              --

              Darius

              • 5. Re: Internal Error While Starting Virtual Machine After Crash
                unit1346 Novice

                I tried those steps before and had no success. I tried them again exactly as you listed, in order, and had the same issue. Repaired the permissions and verified the disk while in OS X recovery system. Had even tried to run the VM on a different computer running latest Fusion and it gave same error.

                • 6. Re: Internal Error While Starting Virtual Machine After Crash
                  dariusd Virtuoso
                  VMware EmployeesUser Moderators

                  Interesting.  Is there a newer vmware.log generated inside the virtual machine bundle?  Are there any interesting-looking logs in your home directory's Library/Logs/VMware at the time it fails to power on?

                  --

                  Darius

                  • 7. Re: Internal Error While Starting Virtual Machine After Crash
                    unit1346 Novice

                    Hmm.. That log generated in the VM is the most recent. The logs directory in my home directory (~/Library/Logs/VMware) was blank..

                    • 8. Re: Internal Error While Starting Virtual Machine After Crash
                      dariusd Virtuoso
                      User ModeratorsVMware Employees

                      I think the easiest way to figure this out would be if you could provide a support information bundle.  From Fusion's Help menu, choose Collect Support Information, and it'll prompt for your password and will create a file on your Desktop with a collection of useful logfiles and diagnostic information.  Attach that file to a post here and I'll dig into it.

                       

                      Thanks,

                      --

                      Darius

                      • 9. Re: Internal Error While Starting Virtual Machine After Crash
                        unit1346 Novice

                        Support Information is attached. Thanks for all your help Darius.

                        • 10. Re: Internal Error While Starting Virtual Machine After Crash
                          dariusd Virtuoso
                          VMware EmployeesUser Moderators

                          It looks like you're running your VMs from an NTFS-formatted drive using the Paragon NTFS driver.  Have you tried using Disk Utility to verify the integrity of that NTFS partition?  The error messages suggest strongly that the NTFS filesystem might be corrupt or there may be a problem with the NTFS driver.  (I expect that the NTFS driver wasn't available when you used the Recovery Environment to check the disks.)

                           

                          If that volume also checks out OK through Disk Utility's First Aid option, you might either need to upgrade your Paragon NTFS driver from version 11 to version 12 (which their website claims is the first version with Yosemite support), or you might need to attach the drive to a Windows machine and have Windows perform its own native filesystem check on the volume in case Paragon's filesystem check is missing something.

                           

                          Cheers,

                          --

                          Darius

                          • 11. Re: Internal Error While Starting Virtual Machine After Crash
                            unit1346 Novice

                            After running it through the Disk Utility it repaired some errors. Tried running the virtual machine and now it says "File note found: Windows 7-Snapshot2.vmsn. This file is required to power on this virtual machine. If this file was moved, specify the new location." Couldn't find it within the virtual machine.

                            • 12. Re: Internal Error While Starting Virtual Machine After Crash
                              dariusd Virtuoso
                              VMware EmployeesUser Moderators

                              You may have lost some data in the crash.  Launch Terminal and provide the output of the following command:

                               

                                 ls -al /Volumes/Oceanus/Windows\ 7.vmwarevm/

                               

                              and we'll see if things are recoverable.

                               

                              Cheers,

                              --

                              Darius

                              • 13. Re: Internal Error While Starting Virtual Machine After Crash
                                unit1346 Novice

                                total 57505536

                                drwxrwxrwx@ 1 Mark  staff        3087 Mar  1 12:55 .

                                drwxrwxrwx@ 1 Mark  staff        1575 Feb 28 20:27 ..

                                -rw-rw-rw-@ 1 Mark  staff     9699328 Feb 23 22:20 Virtual Disk-000001-s001.vmdk

                                -rw-rw-rw-@ 1 Mark  staff     2949120 Feb 23 22:20 Virtual Disk-000001-s002.vmdk

                                -rw-rw-rw-@ 1 Mark  staff    55377920 Feb 23 22:20 Virtual Disk-000001-s003.vmdk

                                -rw-rw-rw-@ 1 Mark  staff    16908288 Feb 23 22:20 Virtual Disk-000001-s004.vmdk

                                -rw-rw-rw-@ 1 Mark  staff    12189696 Feb 23 22:20 Virtual Disk-000001-s005.vmdk

                                -rw-rw-rw-@ 1 Mark  staff    23265280 Feb 23 22:20 Virtual Disk-000001-s006.vmdk

                                -rw-rw-rw-@ 1 Mark  staff      524288 Feb 23 22:18 Virtual Disk-000001-s007.vmdk

                                -rw-rw-rw-@ 1 Mark  staff    44630016 Feb 23 22:20 Virtual Disk-000001-s008.vmdk

                                -rw-rw-rw-@ 1 Mark  staff      524288 Feb 23 22:18 Virtual Disk-000001-s009.vmdk

                                -rw-rw-rw-@ 1 Mark  staff      524288 Feb 23 22:18 Virtual Disk-000001-s010.vmdk

                                -rw-rw-rw-@ 1 Mark  staff      524288 Feb 23 22:18 Virtual Disk-000001-s011.vmdk

                                -rw-rw-rw-@ 1 Mark  staff      524288 Feb 23 22:18 Virtual Disk-000001-s012.vmdk

                                -rw-rw-rw-@ 1 Mark  staff      524288 Feb 23 22:18 Virtual Disk-000001-s013.vmdk

                                -rw-rw-rw-@ 1 Mark  staff      524288 Feb 23 22:18 Virtual Disk-000001-s014.vmdk

                                -rw-rw-rw-@ 1 Mark  staff      524288 Feb 23 22:18 Virtual Disk-000001-s015.vmdk

                                -rw-rw-rw-@ 1 Mark  staff      131072 Feb 23 22:18 Virtual Disk-000001-s016.vmdk

                                -rw-rw-rw-@ 1 Mark  staff        1081 Feb 23 22:18 Virtual Disk-000001.vmdk

                                -rwxrwxrwx@ 1 Mark  staff  4174118912 Feb 23 22:18 Virtual Disk-s001.vmdk

                                -rwxrwxrwx@ 1 Mark  staff  4248829952 Feb 23 22:18 Virtual Disk-s002.vmdk

                                -rwxrwxrwx@ 1 Mark  staff  4217765888 Feb 23 22:18 Virtual Disk-s003.vmdk

                                -rwxrwxrwx@ 1 Mark  staff  4252499968 Feb 23 22:18 Virtual Disk-s004.vmdk

                                -rwxrwxrwx@ 1 Mark  staff  2636709888 Feb 23 22:18 Virtual Disk-s005.vmdk

                                -rwxrwxrwx@ 1 Mark  staff  3703832576 Feb 23 22:18 Virtual Disk-s006.vmdk

                                -rwxrwxrwx@ 1 Mark  staff   684851200 Feb 23 22:18 Virtual Disk-s007.vmdk

                                -rwxrwxrwx@ 1 Mark  staff  1728184320 Feb 23 22:18 Virtual Disk-s008.vmdk

                                -rwxrwxrwx@ 1 Mark  staff  3620274176 Feb 23 22:18 Virtual Disk-s009.vmdk

                                -rwxrwxrwx@ 1 Mark  staff      524288 Feb 23 22:18 Virtual Disk-s010.vmdk

                                -rwxrwxrwx@ 1 Mark  staff      524288 Feb 23 22:18 Virtual Disk-s011.vmdk

                                -rwxrwxrwx@ 1 Mark  staff      524288 Feb 23 22:18 Virtual Disk-s012.vmdk

                                -rwxrwxrwx@ 1 Mark  staff      524288 Feb 23 22:18 Virtual Disk-s013.vmdk

                                -rwxrwxrwx@ 1 Mark  staff      524288 Feb 23 22:18 Virtual Disk-s014.vmdk

                                -rwxrwxrwx@ 1 Mark  staff      524288 Feb 23 22:18 Virtual Disk-s015.vmdk

                                -rwxrwxrwx@ 1 Mark  staff      196608 Feb 23 22:18 Virtual Disk-s016.vmdk

                                -rwxrwxrwx@ 1 Mark  staff        1162 Feb 23 22:08 Virtual Disk.vmdk

                                -rwxrwxrwx@ 1 Mark  staff        8684 Feb 23 22:18 Windows 7.nvram

                                -rw-rw-rw-@ 1 Mark  staff         988 Feb 23 22:08 Windows 7.plist

                                -rw-rw-rw-@ 1 Mark  staff         422 Feb 23 22:18 Windows 7.vmsd

                                -rwxrwxrwx@ 1 Mark  staff        3885 Feb 23 22:19 Windows 7.vmx

                                -rwxrwxrwx@ 1 Mark  staff        3226 Jan 27 14:25 Windows 7.vmxf

                                drwxrwxrwx@ 1 Mark  staff         441 Feb  4 22:24 appListCache

                                drwxrwxrwx@ 1 Mark  staff         189 Feb  9 21:30 caches

                                -rw-rw-rw-@ 1 Mark  staff           0 Feb 23 23:15 quicklook-cache.png

                                -rwxrwxrwx@ 1 Mark  staff      814320 Jan 31 22:31 startMenu.plist

                                -rw-r--r--@ 1 Mark  staff      343126 Feb  9 21:52 vmware-0.log

                                -rwxrwxrwx@ 1 Mark  staff      634157 Feb  8 20:54 vmware-1.log

                                -rwxrwxrwx@ 1 Mark  staff      684953 Feb  4 22:15 vmware-2.log

                                -rw-r--r--@ 1 Mark  staff      543767 Feb 23 22:20 vmware.log

                                 

                                At first quick glance I don't see it listed.. Seems it's listing all the files already present?

                                • 14. Re: Internal Error While Starting Virtual Machine After Crash
                                  dariusd Virtuoso
                                  User ModeratorsVMware Employees

                                  Yeah, part of the VM's snapshot state was lost in the crash.  I'm not an expert in the reconstruction/recovery of the state of a VM with snapshots... it's just not something I've done, although I'm sure I could figure it out given a bit of time.  If I'm understanding correctly, you'll need to change your snapshot from a "powered on" snapshot (which would have been stored in the missing files) to a "powered off" snapshot, so the VM will boot up afresh next time it's powered on, just like a physical machine that's abruptly lost power.

                                   

                                  If any of our forum regulars who've got more experience with this could help out, I'd appreciate it.

                                   

                                  Otherwise, I'll try to dig into this some more tomorrow and see if I can figure out how to get you going again.

                                   

                                  Cheers,

                                  --

                                  Darius

                                  1 2 Previous Next