I'm a bit new to the whole VM concept, and I need some help.
I'm running Windows XP as a VM on an external HDD. When I added the virtual machine to Fusion 1.1.2 on my Macbook Pro (OS X 10.4.11), a file with the extension .vmwarevm was placed in my "Documents" folder under "Virtual Machines". The package contents almost look like replicas of the VM on my external HDD, but I can't run the VM from the local file, only the external one. At first this file was about 4 GB and I didn't think much of it, but now it's almost 45 GB and I'm running out of disk room. Do I need this file? Isn't the VM located on my external HDD?
Any thought?
Contents of the ~45 GB .vmwarevm bundle (ctrl-click, select Show Package Contents)?
The contents of the package are as follows:
564db47d-c335-f2a9-5fe6-cf0d74dc9a3f.vmem
564db47d-c335-f2a9-5fe6-cf0d74dc9a3f.vmem.lck
Applications
vmware-0.log
vmware-1.log
vmware-2.log
vmware.log
Work PC-000002-s001.vmdk
Work PC-000002-s002.vmdk
Work PC-000002-s003.vmdk
Work PC-000002-s004.vmdk
Work PC-000002-s005.vmdk
Work PC-000002-s006.vmdk
Work PC-000002-s007.vmdk
Work PC-000002-s008.vmdk
Work PC-000002-s009.vmdk
Work PC-000002-s010.vmdk
Work PC-000002-s011.vmdk
Work PC-000002-s012.vmdk
Work PC-000002-s013.vmdk
Work PC-000002-s014.vmdk
Work PC-000002-s015.vmdk
Work PC-000002-s016.vmdk
Work PC-000002-s017.vmdk
Work PC-000002-s018.vmdk
Work PC-000002-s019.vmdk
Work PC-000002-s020.vmdk
Work PC-000002-s021.vmdk
Work PC-000002-s022.vmdk
Work PC-000002-s023.vmdk
Work PC-000002-s024.vmdk
Work PC-000002-s025.vmdk
Work PC-000002-s026.vmdk
Work PC-000002.vmdk
Work PC-000002.vmdk.lck
Work PC-Snapshot4.vmem
Work PC-Snapshot4.vmsn
Work PC.nvram
Work PC.vmsd
Work PC.vmx
Work PC.vmx.lck
Each of the "Work PC..." files is about 2 GB, which sure makes it look like a copy of the actual VM on my external drive. Do I need these? Would it hurt to remove these files temporarily and try to start up the VM?
Look at the modify dates on these files (and the vmwarevm package). Pretty sure this is your VM. Do the same check on the files on your external drive. Pretty sure it hasn't been touched in a while...
You can also check under settings for your VM what files it's actually using.
/Mikael
Ok, that got me a little closer. The files on my local HDD have been modified recently, whereas the ones on my external haven't been changed in the last 2 months (which is about when I created this VM). So I should be able to unplug my external HDD and run the VM, but when I open Fusion and double click on "Work PC" a message comes up that says "File not found: Work PC.vmdk". Why would that file be on my external drive, but the rest on my local drive? Can I just move it to the local package?
Thanks for helping me. I really appreciate it.
Attach both Work PC.vmx files. Rename one to denote which was on the external drive.
Looks to me that you're running with a snapshot. The master VM is on the external drive and the snapshot files have ended up in the default location on your hard drive.
If that's the case and you revert the snapshot you will loose everything back to the date when the external VM files was last touched.
Check if the "Revert to Snapshot" toolbar menu item is grayed out or not.
/Mikael
In addition to what Woody said, what happens if you disconnect the drive and open the local virtual machine from the Finder (instead of from Fusion's Library window, which is referencing the virtual machine on the external drive)?
webfrasse: A snapshot wouldn't explain the presence of what appears to be a complete virtual machine on the local drive; the modification times on the external drive would also be current (due to the .vmx, logs, etc. updating). It sounds to me like the original poster's been running from the local drive this whole time. One possibility is if the .vmx files have an absolute path pointing at the local drive, and the one in the Library is the one on the external drive.
One possibility is if the .vmx files have an absolute path pointing at the local drive, and the one in the Library is the one on the external drive.
Eric, I know you know what I'm about to say so this is meant for webfrasse and others reading this thread... Yes and this is one of the reasons I asked for the .vmx files to be posted and the one from the ext hdd to me marked as this would explain this however if the .vmx files do not show what I was thinking it would have been nice to have a dir list with date/time stamps of both Virtual Machine Bundle Packages too however I wasn't going to ask for that until I saw the .vmx files.
The names of the vmdk files does indicate that a snapshot has been taken at some point...
A fresh or cloned VM instance wouldn't have vmdk files named like that.
/Mikael
These are the contents of the vmwarevm on my local HDD:
Applications
vmware-0.log
vmware-1.log
vmware-2.log
vmware.log
Work PC-000002-s001.vmdk
Work PC-000002-s002.vmdk
Work PC-000002-s003.vmdk
Work PC-000002-s004.vmdk
Work PC-000002-s005.vmdk
Work PC-000002-s006.vmdk
Work PC-000002-s007.vmdk
Work PC-000002-s008.vmdk
Work PC-000002-s009.vmdk
Work PC-000002-s010.vmdk
Work PC-000002-s011.vmdk
Work PC-000002-s012.vmdk
Work PC-000002-s013.vmdk
Work PC-000002-s014.vmdk
Work PC-000002-s015.vmdk
Work PC-000002-s016.vmdk
Work PC-000002-s017.vmdk
Work PC-000002-s018.vmdk
Work PC-000002-s019.vmdk
Work PC-000002-s020.vmdk
Work PC-000002-s021.vmdk
Work PC-000002-s022.vmdk
Work PC-000002-s023.vmdk
Work PC-000002-s024.vmdk
Work PC-000002-s025.vmdk
Work PC-000002-s026.vmdk
Work PC-000002.vmdk
Work PC-Snapshot4.vmem
Work PC-Snapshot4.vmsn
Work PC.nvram
Work PC.vmem
Work PC.vmsd
Work PC.vmss
Work PC.vmx
-
And these are the contents of the VM on my external drive:
Work PC
Work PC-f001.vmdk
Work PC-f002.vmdk
Work PC-f003.vmdk
Work PC-f004.vmdk
Work PC-f005.vmdk
Work PC-f006.vmdk
Work PC-f007.vmdk
Work PC-f008.vmdk
Work PC-f009.vmdk
Work PC-f010.vmdk
Work PC-f011.vmdk
Work PC-f012.vmdk
Work PC-f013.vmdk
Work PC-f014.vmdk
Work PC-f015.vmdk
Work PC-f016.vmdk
Work PC-f017.vmdk
Work PC-f018.vmdk
Work PC-f019.vmdk
Work PC-f020.vmdk
Work PC-f021.vmdk
Work PC-f022.vmdk
Work PC-f023.vmdk
Work PC-f024.vmdk
Work PC-f025.vmdk
Work PC-f026.vmdk
Work PC.vmdk
Work PC.vmx
-
Notice the first one on my external drive is also a vmwarevm file. It's contents are as follows:
vmware-0.log
vmware-1.log
vmware-2.log
vmware.log
Work PC-000001-s001.vmdk
Work PC-000001-s002.vmdk
Work PC-000001-s003.vmdk
Work PC-000001-s004.vmdk
Work PC-000001-s005.vmdk
Work PC-000001-s006.vmdk
Work PC-000001-s007.vmdk
Work PC-000001-s008.vmdk
Work PC-000001-s009.vmdk
Work PC-000001-s010.vmdk
Work PC-000001-s011.vmdk
Work PC-000001-s012.vmdk
Work PC-000001-s013.vmdk
Work PC-000001-s014.vmdk
Work PC-000001-s015.vmdk
Work PC-000001-s016.vmdk
Work PC-000001-s017.vmdk
Work PC-000001-s018.vmdk
Work PC-000001-s019.vmdk
Work PC-000001-s020.vmdk
Work PC-000001-s021.vmdk
Work PC-000001-s022.vmdk
Work PC-000001-s023.vmdk
Work PC-000001-s024.vmdk
Work PC-000001-s025.vmdk
Work PC-000001-s026.vmdk
Work PC-000001.vmdk
Work PC-Snapshot1.vmem
Work PC-Snapshot1.vmsn
Work PC.nvram
Work PC.vmsd
Work PC.vmx
I did take snapshots every once in a while, whenever I was about to change something important. I was under the impression that this was some kind of backup mechanism.
So you have two VM's on your external drive? Looks like that to me.
You can say that a snapshot is a kind of backup. It allows you to undo everything from the moment you took the snapshot. It's a great way to rollback the state of the VM after a demo or when you wanted to try a beta of a product of a patch. You can the either rollback (revert) = undo everything or commit all changes. I think the semantics of the later is a little confused in VMware Fusion. It's better on the Windows and Linux version (VMware Workstation). Here you can either discard the snapshot or take a new one.
I think a new snapshot will merge the old snapshot with the pre-snapshot VM (commit the changes). Discard to me mean throw away the changes which is what a Revert to Snapshot also does. Maybe someone from VMware can clarify this...the online help isn't helping a bit.
I'm not using snapshots on Fusion since it's so crippled compared to what Workstation offers. Been using VMware Workstation on Windows since version 2...
/Mikael
I'm not too sure what some of that meant. What are you saying you think i should do?
I didn't realize there was a second VM package on my external HDD until you guys asked me to list the contents.
"Revert to snapshot" is NOT greyed out. What does that mean? How large is a snapshot? Should I just not do that?
Not sure...I'm waiting for Eric, etung, to step in. He works at VMware. I basically think they messed up a working semantics from Windows and Linux versions when they introduced snapshots in Fusion. That's why I don't use it on the Mac.
Can you describe how you created the VMware instance in the first place on your Mac? The one that is growing...
There is no size limit on a snapshot. It can well go into the size you see on your local drive
/Mikael
-
I'm not sure how the one on my local drive was created. I just noticed it there a couple months ago when I was cleaning out my Documents folder. It was originally about 4GB so I didn't care too much. I'm not so much worried about where they all came from and what they're doing. If there is a way for me to take what is currently running when I open the "Work PC" VM in the library, I would gladly just make a new one and toss the old ones. I don't need the backups, just more HDD space. If I open up XP and convert it into a new VM, can I just use that one and toss the other ones?
Can I just say "Discard Snapshot"? Would that get rid of the old one?
OK, so I connected myself to a network drive with 260 GB free space. I'll convert my current VM (wherever it happens to be running from) to a new VM and just put the files on the network drive for now. Then, when it's finished, I'll take all three of the ones I currently have, both on my local HDD and my external HDD, and put them in a folder on the network drive. Then I'll just take the new one I created and put it back on my personal drive. If it works alright I'll just trash all of those other ones.
That should work, right? Out of curiosity, I'd still like to know what the heck is going on with all of these other VM's though.
That sounds like a safe plan. Question. What do you do exactly when you
say "convert my Current VM"?
I'm curious too. I have never seen this behavior. You must be doing
something that triggers files to be generated on other drives or you
somehow managed to have your master VM on one drive and the snapshot
files on a another drive. I would stop using snapshots. Seems to me like
your also a bit unclear as to how the really work in fusion.
Must say that I'm a bit disappointed in etungs silence since yesterday.
The documentation around snapshots in fusion is anything but good. It's
downright marketing to me. No depth.
I think if you revert or discard a snapshot all changes are lost, rolled
back. If you take a new snapshot. The changes in the existing snapshot
is merged with the VM before the new snapshot is taken. So if you want
to remove a snapshot but keep the changes instead of rolling back what
you did you need to take a new snapshot and then immediately remove the
new one (which is empty).
I'd like to see a confirmation from VMware on this or they are welcome
to point me to where this is described in detail in the documentation.
/Mikael
Must say that I'm a bit disappointed in etungs silence since yesterday.
Sorry, it's been pretty busy for the past couple days. I do have to do things other than hang out on the forums all the time My silence is not necessarily meaningful - I could be busy/distracted, on vacation (coming up), think others are handling it fine, etc.
I agree that this situation is perplexing, and that Converter is a good way to recover regardless of what's going on under the hood.