you can try to change the cpuidFaulting.enable line to FALSE in .vmx file assuming the VM was switched off before copying its files. If the line is not present, simply add:
cpuidFaulting.enable = "FALSE"
Also, search for any cpuid lines in the .vmx file and try to remove them to get rid of any remnants from the old host.
That shoud do the trick ;-)
The cpuidFaulting.enable line was not present and I added it. There was no other mention of cpuid in that file. However the virtual machine still does not run. When I try to open it, I get the question below:
to which I answer "I Copied it". After this I get the following error message:
and when I click "Restart Windows" nothing happens. It is just a black screen with the start button active and each time that I press it I have the same error.
I am not quite sure but now that I am thinking again about it, I have the impression that this virtual machine has been created on a Macbook Pro Core 2 Duo 2.66 GHz from 2009. It runs without problem on the more recent Macbook Pro Core i7 2.2 GHz mentioned in the beginning but not on the iMac. I don't know if that makes any difference though.
Not sure if I understand. A virtual machine is either running or shut down and its state is stored by VMware.
So I don't see what exactly you are asking me to do. Should I, perhaps, open the VM in the Macbook Pro (where it runs without problems), suspend it from there and post here the vmware.log file? The log file posted previously has been obtained after my failed attempts to open the VM in the iMac.
I don't know what to believe anymore. I tried again with two different virtual machines and the transition from the Macbook Pro to the iMac was flawless for the two of them. Only a proper shutdown on the MBP before connecting to the iMac was necessary, as one would logically expect.
I don't know why, but the errors definitely look as if you were trying to resume the virtual machine from suspended state, not shutdown state.
You might try to delete any .lck and .vmss files from the virtual machine directory if present. That should force a clean start.
Otherwise I suggest forcing fusion to emulate the old CPU by adding these to the .vmx file:
Thank you so much for trying to help me but none of the proposed steps worked. I always have the same errors.
In the meantime I found the installation disk and I tried to start from scratch. So, I created a new image from within VMware which tried automatically to boot before installing the operating system. I don't know (don't remember) if this is normal, so I switched manually to CD/DVD as boot media and tried to restart from there. Same problem as always.
Could you please post here the details for the creation of a new Windows VM under VMware Fusion 8, so that I can check the procedure that I followed?
Your original post implies that you are trying to run Fusion 8 on your new iMac that's running macOS 10.14 (Mojave). Am I interpreting that correctly?
You do realize that Fusion 8 is not supported on Mojave per KB2088571
Have you tried to install Fusion 11 (you can get it as an evaluation version to try it out) and see if the problem is still there?
No, this is new to me. I just transferred my VMware 8 copy on the iMac under macOS Mojave and it ran without incident. No error whatsoever. As I mentioned previously, I even managed to run on the iMac other virtual machines (Windows and Linux) created in the Macbook Pro without any special manipulation.
I remember other cases in the past when an old VMware version could not even open after a major Mac OS X (at that time) update. But this is not the case with VMware 8 and macOS Mojave. So, this is a mystery to me in view of the compatibility table, unless I am missing something here.
But yes, I will try VMware Fusion 11 once I get the chance to. By the way, does this version support hardware accelerated 3D graphics for Snow Leopard VMs?