One of the benefits of virtual machines is that they are (for the most part) portable.
Note that the guest OS should be *shut down*, not *suspended* before copying to another host computer, however.
You can check the vmware.log in the VM's folder on the new host to see if there are any error messages which point you towards the problem.
I couldn't even get to the point where I could power on the VM.
When I do a File -> Open -> .vmx, I get a blank screen. VMware Workstation is not even loading the details of this VM
As a result, most of the menu options including the menu VM -> Power are all grayed out.
I am almost positive I had all VM's shutdown before making the copies. I want to clarify when I say "Copy". This is actually what
1. Powered off the VM
2. I used ISOCreator to create an ISO file starting at the root directory of my VM.
For example, I may have these VM's on my host machines
So I used ISOCreator to create a "windows7.iso"
4. I then copied this "windows7.iso" to the new Dell machine
5. Unpacked the "windows7.iso" giving me the exact directory structure as where it came from.
So that's what I did. This is the same as doing a COPY command except it takes much longer. Creating an ISO is much more
compact and much faster. This is typically how I would clone a VM. But I have never cloned it to another host with different hardware.
I have done this many times to the same but a different location and never had an issue.
In addition, when I tried to load the .vmx file, it's almost acting as if nothing happened. I just see a blank screen
on the right pane side of my VMware Workstation. The left pane would still have what I had opened previously
but it just won't open the VM I want after the copy/move/clone however you want to call it.
I guess my question is: can I actually run my VM after I "copied" it to the new Dell machine knowing this Dell
machine has different hardware configurations than the machine the VM came from?
Of course you can copy a VM to another machine with different hardware. The issue you have run into if that you cannot "open" the VM, which has nothing to do with the new hardware (because you have never powered on the VM). I have never try to burn the VM to an iso image in order to copy it. When we want to copy the VM to another machine, we just copy the whole VM folder. But it should not be the cause of the issue since you can do it successfully within the same machine. Please paste the UI log (You can find the location of ui log from Workstation menu Help > About VMware Workstation > UI log file).
If you have added the files to an ISO image to copy, and copied them from the CD (or ISO image) onto the new PC, make sure the copied files are not marked read-only - many will be when you put them onto a CD.
Just to clarify, I did not "burn" the image to any media. I simply created the ISO (ie Windows7.iso) and copied this ISO to the target machine
via a USB flash drive.
Here's a couple of new discoveries from last night. I did a File -> Scan for Virtual Machines. I pointed it to the supposedly "bad" .vmx file.
I then imported it so it showed up on the left pane of my VMware Workstation. Now when I tried to open it, I got an error saying "vmx corrupt".
Went to Google and searched.... I followed one of articles to re-create the .vmx file. I first renamed the bad .vmx. Went through steps
and it created the new one. Tried to open the new .vmx but got a new error. Now it says "Bad dictionary" or "No Dictionary" or something to this
affect. It was late in the night and I just stopped there.
Does this give you more clues as to what might have caused this?
Also, someone said make sure the vm was powered off before I do the copy or create the ISO.
So I fired up this VM on the source machine last night just to be absolutely sure it was working. I
did a shutdown within Windows Server 2016 which powered off the VM. I re-did the ISO.
It did not fix my problem.
Please attach your vmx-file to your next reply
The original bad .vmx or the one I re-created last night?
That vmx-file is corrupted beyond repair.
Please attach all the vmware.logs you still have instead.
Can the vmx file be re-created using existing supporting files for this virtual machine? I know when I followed one of the articles I found last
night, it did re-create file but did not fix my issue. If this is possible, would you kindly share your experience on how to do this? I will look into
this more this weekend.
I will get a copy of the vmx file from the source and put it on the target and see what happens.