[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1540
  • Last Modified:

How Do I Change Location of a VM in VMWare Fusion?

I'm running VMWare Fusion 3.1.2 on my MacBook (OS X 10.6.8). I need to change the location of my virtual machines from the default of User\Documents\Virtual Machines.

I tried simply moving the windows.vmware file over to the new location. However, when I try to open the VM from the new location, I get a message saying, "A needed file was not found" and the VM does not open.
0
anuneznyc
Asked:
anuneznyc
  • 3
  • 2
2 Solutions
 
anuneznycAuthor Commented:
That's the way I thought it was supposed to work. But in my case, I get a message saying, "A needed file was not found" and the VM does not open. I don't get a dialog box asking me if the VM was moved or copied.
0
 
strungCommented:
What did you copy it to? Are you sure you copied everything? Do you possibly have a permissions error?
0
 
anuneznycAuthor Commented:
Figured it out. Turns out you have to copy the Virtual Machines folder for this to work. I had *moved* it by dragging & dropping using the Finder. That was no good. Once I did a copy & paste from the finder, then I was able to open the file, click on "I copied it here" and it loaded fine.

What I don't understand is what difference it makes to copy something instead of moving it. I know the obvious difference b/t the 2, but why should it make a difference here?? After all is said and done, the Virtual Machines folder ends up in the final location regardless of whether it was moved or copied! So there is must be some attributes or something that don't get moved properly unless they are copied.

Any idea why this would be the case??
0
 
anuneznycAuthor Commented:
Mine is the correct solution.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now