Vmware fusion internal error mac os

Internal Error #3

Comments

Sir-Cumference commented Jun 20, 2017

I’m sorry, but when I try to open the Boot Camp VM, it just tells me «Internal Error». Any ideas?

The text was updated successfully, but these errors were encountered:

mikew commented Jun 20, 2017

That’s not a whole lot to go on.

• Is your boot camp partition on your main drive?
• Anything in the log files (they should be in your Boot Camp.vmwarevm folder on your desktop)
• If nothing there, is there anything in the Console app in macOS?

Sir-Cumference commented Jun 20, 2017 •

Sorry for being a bit inept, but I see no Boot Camp.vmwarevm folder. All that was created is Boot Camp.krqVv2.vmwarevm , which is what gives me the error if I open it.

Opening it also damages my partition (i.e. the «Boot Camp» disk disappears from Finder and when I restart and switch to Windows, it has to repair itself).

When I open it, this is what comes up in the Console app: https://pastebin.com/raw/fjwxUneY

mikew commented Jun 20, 2017

Boot Camp.krqVv2.vmwarevm is what I was referring to, if you right-click on that there will be an option in the menu to «Show Package Contents». Click that and a finder window will open. In there you may find some log files.

The disk disappearing from finder is normal, that’s Fusion unmounting it before it tries to boot your VM.

And a couple of more questions:

• What version of macOS are you running?
• What version of VMWare Fusion are you running?

Sir-Cumference commented Jun 20, 2017

Hmm, all I see are these:

Also, I’m using Sierra 10.12.5, and VMWare Fusion Pro’s trial 8.5.7.

Sir-Cumference commented Jun 30, 2017

@mikew So, um. any update?

jguittard commented Oct 17, 2017

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Vmware fusion internal error mac os

• VMware Technology Network
• :
• Desktop Hypervisor
• :
• VMware Fusion
• :
• VMware Fusion Discussions
• :
• Internal Error on new 2018 MacBook Pro and Fusion .

• Subscribe to RSS Feed
• Mark Topic as New
• Mark Topic as Read
• Float this Topic for Current User
• Bookmark
• Subscribe
• Mute
• Printer Friendly Page

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

When I take a VM from a working High Sierra installation (on a 2013 Mac Pro) and copy it to my new 2018 13″ MacBook Pro with the new macOS Mojave, I get an Internal Error when I try to start the VM. Not a very descriptive error. Any idea how to fix this?

I had the same error on Fusion 10.x on the same machine. I’ve tried the various troubleshooting tips such as moving the application out of the Applications folder and then back again. This does trigger an install dialog and asks for an Admin password but the Security control panel warning does not repeat. This looks like a Kext permission problem.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

Can you generate the error and then run Help > Collect Support Information and share the .tgz?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

Could you check if there is a folder named vmName.lck in vm bundle? Could you find a vmx process when this problem occur?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

There is a folder called: 564df29d-8306-ea25-f656-3cf09c96d22d.vmem.lck

I see no sign of any process called vmx.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

Not easily if this forum doesn’t support uploads. I can mail it to someone.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

1. Make sure you delete all .lck files from your virtual machine bundle, .lck are the locks files.

2. Try this command in terminal, kextstat | awk ‘$6 !

/^com.apple/ < print $6 " \t " $7 >‘ this will load the kext status.

3. If you see that kexts are not loading, then the issue is isolated at Mac OS level, Go to System Preferences -Security & Privacy-General- See if you get any message, which requires you to «allow» the VMware Fusion so that kext could get loaded.

If this doesn’t help, re-install Fusion.

1) Manually remove Fusion completely (better by using App cleaner from FreeMacSoft) and then execute the below commands in Terminal window on Mac Host

xattr -dr com.apple.quarantine

/Downloads/VMware-Fusion.xxxx.dmg (Here it would list you the possible quarantine, mostly chrome or safari, close that application) and run the command.

2. Install Fusion normally, this time, it should prompt you for the warning in Security & Preferences.

P.S: Note down your license key before uninstalling.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

I was able to resolve the «Internal error» issue and to install version 11 properly.

1. Do not start the «VMware Fusion.app» from the mounted .dmg

2. Remove all previous VMWare fusion installations. You could use e.g. «AppCleaner» (which, by the way, was used at the last upgrade hassle by an VMWare employee on my Mac 😉 )

3. Copy «VMWareFusion.app» to your Applications directory

4. Start «VMWareFusion.app» from the Applications directory

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

I solved the problem for me. But I don’t think it is a general solution. I suspect that you have to try many of the options presented in these pages and eventually something will work.

I’m fairly certain that the problem is with permissions for the kext’s that are part of the application. These are essentially system files and drivers that run at nearly the highest privilege in macOS. As such, Apple has spent effort on recent updates to make the security around kexts more robust. If you install VMWare Fusion and go to your /Library/ folder (not your

/Library/ folder), you will see something called StageExtensions. In there you see a few directories. I found the VMWare kexts in the /Library/StagedExtensions/Application/VMware Fusion.app folder. When I uninstall VMWare Fusion and reboot, they disappear.

One of the suggestions here was to install with a new Administrator account. I tried that but when I switched back to my normal admin account, I saw the same Internal Error. At the time, it didn’t occur to me try running VMWare from the new admin account. After uninstalling everything VMWare installs for the 10th time and creating another new admin account, the install worked and I could run a VM but only from the new admin account. My normal account still failed with the dreaded «Internal Error».

This makes me believe that macOS is holding on to some old permissions and not installing the new kexts for my user because the old ones are incompatible. So I uninstalled everything for the 11th time (or so) and created another new admin account (BTW, delete old admin accounts when you are done with them, they can be a security hole unless you are very careful with passwords etc.) This time, I downgraded my normal user account to turn off administrative rights and rebooted again. I then reinstalled VMWare Fusion from the newly created (and now only) admin account. I launched Fusion and ran one of my development VMs. It started up and worked perfectly. I then logged off the temporary admin account and logged in to my normal but now non-admin account. I got about 2 dozen errors asking for my admin password. I entered a few but then just started hitting cancel until they all went away. I launched Fusion with a copy of the VM that I used from the other account. And it started up normally and worked without any issues. I subsequently gave myself back admin permissions, rebooted and VMWare still works. My problem seems 100% solved.

I can’t say that this will fix other people’s «Internal Error» problems but it worked for me. I suspect you will have to try multiple things until VMWare figures out the exact problem and issues an update.

Источник

BigR’s Weblog

Something you might need to know, one day…

OSX Fusion / VMWare vmdk has one or more internal errors that cannot be fixed

Not the best sight to greet you when you try and start up a VMWare session on Fusion (VMWare’s OSX implementation). I knew that I had caused this by Force Quitting Fusion the night before because I thought it had hung. In fact it was moving disk blocks around because I had deleted a snapshot.

The Library looked okay:

I could see no ‘reclaimable’ shading on the bar so it seemed that the old snapshot had been cleaned up correctly.

But the session would not start. I needed to find the log file to see what was going on.

So the first thing is to find the VMWare files in question. I navigated to the following path (where raza is the username for the machine):

Inside this folder was one file – the container holding the operating system I am using on the machine under Fusion.

You need to right click on the file and Show Package Contents to open the container,

So I looked in the log file and saw:

2014-06-18T19:13:20.515Z| Worker#0| I120: DISK: OPEN scsi0:0 ‘/Users/raza/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm/Windows XP Professional-000002.vmdk’ persistent R[]
2014-06-18T19:13:20.528Z| Worker#0| I120: Current OS Release is 13.2.0
2014-06-18T19:13:20.573Z| Worker#0| I120: DISKLIB-SPARSECHK: [/Users/raza/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm/Windows XP Professional-000002.vmdk] GT Error (GG2): GT[728][509] = 72349440 / 14630400
2014-06-18T19:13:20.759Z| Worker#0| I120: DISKLIB-SPARSECHK: [/Users/raza/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm/Windows XP Professional-000002.vmdk] Grain #565030 @72349568 is orphaned.
2014-06-18T19:13:20.759Z| Worker#0| I120: DISKLIB-SPARSECHK: [/Users/raza/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm/Windows XP

followed by more “Grain #nnnnnn is orphaned” messages for the the vast majority of the 106MB log file.

It was at this point I realised that I had older snapshots, and I had a backup of the data inside the current container because I use a backup agent when the container is working. What I didn’t have was a backup of the container (or rather of the physical file). I hadn’t done this because of course the file is huge and when you are in Fusion, the file is open so you can’t get a consistent backup anyway.

So I did what any sensible person does at this point. I googled. It looked like it might just be a lock file issue (it wasn’t, and that was the solution because I did have to go to an older snapshot in the end) so I thought I would visually document the answer if it had been a lock file problem – which has the same symptoms.

In the folder, the 02 suffix file was the snapshot that had the issue – 75GB of changes… ouch!

Anyway, you can see the lock folder file with the .lck extension:

and inside this folder is a lock file:

So I deleted the folder.

Now the Library window shows that the snapshots are accessible.

Sure enough, you can see them.

But annoyingly if you try and start the Current State file, it still fails with the same error.

A thread at https://communities.vmware.com/ suggested repairing the vmdk file. For me using Fusion 6.0.3 this meant the following command string:

sudo “/Applications/VMware Fusion.app/Contents/Library/vmware-vdiskmanager” -R /Users/raza/Documents/Virtual\ Machines.localized/Windows\ XP\ Professional.vmwarevm/Windows\ XP\ Professional-000002.vmdk

No joy though, as I got the message:

The virtual disk, ‘/Users/raza/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm/Windows XP Professional-000002.vmdk’, is corrupted and cannot be repaired.

There was no choice but to go back to the last snapshot and then apply all the changes I had made. Luckily there were not many, and those that could have been tricky – like applications, turned out to be okay because I had retained copies of them on a network volume (I had deleted them from the physical PC that was being migrated to a VM as I completed each transfer). Once that was done I reinstalled the backup software and pulled any local user files from the last backup.

Of course this was a learning exercise and I learnt I should have been

a) using automatic snapshots using the Fusion Autoprotect feature

b) that I should backup the container vmdk file (so I now do that once a week, if the file is not open – an option in Crashplan – to a local NAS)

c) that snapshots are not equal to backups because they are on the same physical host and even if you were to copy them elsewhere, they are a chain of files holding changes from the last snapshot. That means if you lose one, you risk not being able to use later snapshots.

The article https://communities.vmware.com/thread/177906 and https://communities.vmware.com/message/2118363 suggests I might be able to open the corrupt vmdk using VDK or UFS Explorer under a windows 32bit platform… I’ll update this post if I ever try that.

Update: 21st June 2014:

Wow! I tried UFS Explorer (on OSX) against the damaged vmdk file. It had absolutely no problem reading it and let me do a recovery of files without a problem. I didn’t need anything from the container but at least I was able to verify that I had not missed anything in recreating it from an old snapshot + backups.

Источник