VMware Communities
oldMACdonnell
Enthusiast
Enthusiast

Virtual Machines.localized exceeds fixed 40 Gb size

Hello,

I have an iMac, RAM 2 Gb, HD 320 Gb, OS 10.6.8

Installed VMWARE Fusion, VMW Tools, Windows XP Home Ed.

I use windows only for a number of bridge games. Installed size 1 Gb max.

Recently I updated the Windows software, ran a virusscan.

The Virtual Machines .localized file then started growing each VMW session.

I used the Space Gremlin prog to see what was in the file.

More than 150 files. A lot of 1 -  2,1 Gb files .vmdk, smaller .vmem files, snapshot.vmem files, .vmss and .vmsn files.

I deleted some of the oldest files, but then the program did not work anymore. I recovered an earlier version of the VM.localized file with Time Machine and all was OK. Yet the size was 44,8 Gb.

In Mac Activities vmware uses 630 Mb

1. Why is the file getting bigger and bigger, even above the fixed size?

2. Can I restrict this?

3. Can I edit or restrict the size of the file, leaving only the content I need? Deleting snapshots (I kept 4 ) has only limited effect. Or should I start from scratch?

4. Was the windows update to blame?

Who can help me?

0 Kudos
12 Replies
oldMACdonnell
Enthusiast
Enthusiast

VMWARE Fusion 2.0

0 Kudos
a_p_
Leadership
Leadership

With more than 150 files I assume you have more than 4 snapshots (40GB will results in ~20 .vmdk files for the base disk and/or snapshots). So unless I'm mistaken you currently have 6 snapshots. Snapshots in VMware products work as a chain, each chain link is used and write operations will go to the latest chain link, growing this up to the provisioned size of the bas disk.

André

0 Kudos
oldMACdonnell
Enthusiast
Enthusiast

Hello Andre,

Thank you very much for your prompt reply!    Smiley Happy

I checked the number of snapshots, and you are right.

I had 2 snapshots hidden in the snapshots overview which belonged to the autoprotect function.  :smileygrin:

So I deleted one autoprotect snapshot. It only gained me 0,6 Gb of disk space.

Now I have 5 snapshots as far as I can see, but still 44,2 Gb of diskspace.

Even full snapshot removal would not bring me below 40 Gb.

And I am surprised that thedisk space limit of 40 Gb has been exceeded.

What can I do?

0 Kudos
a_p_
Leadership
Leadership

Please run "Collect Support Information" from the Fusion Help menu and attach the resulting archive to your next post. This should help to find out what can be done.

André

0 Kudos
oldMACdonnell
Enthusiast
Enthusiast

Hello Andre,

Please find the file below

Kind Regards

0 Kudos
WoodyZ
Immortal
Immortal

Not that this has a direct impact on your issue but why are you still running VMware Fusion 2.0?  You should have updated to a later 2.x release as it's free and fixes the issues that the 2.0 release have! Smiley Wink

Anyway the Virtual Machine has 5 Snapshots and if you what to regain any Host Disk Space then you'll need to delete some or all of the Snapshots.  Additionally if the issue is not enough free space in the Guest OS then you'll need to delete the Snapshots in order to enlarge the virtual hard disk.

0 Kudos
a_p_
Leadership
Leadership

In addition to what Woody said, you may delete the snapshots starting with the oldest one first (the left most snapshot in the Snapshot Manager). As mentioned before, snapshots are used in a chain. Deleting a snapshot will merge the data into its direct parent virtual disk, so only the left most snapshot will be merged into the base virtual disk. If you delete a snapshot other than the oldest one, this data is merged into it's preceding snapshot, most likely growing its size.

Please take a look at http://kb.vmware.com/kb/1015180 which explains how snapshots work.


André

0 Kudos
oldMACdonnell
Enthusiast
Enthusiast

Thank you all for your replies. I have been travelling and need some time to process all this.

I will report the results end of next week.

0 Kudos
oldMACdonnell
Enthusiast
Enthusiast

Hello Andre and Woody,

I did all the things that you mentioned. I studied how the "tree" works and have a much better understanding now.

With Time Machine I reloaded an older version of the Virtual Machines file.

1. I deleted all snapshots, including the hidden ones from Autoprotect, one at a time, starting with the oldest and so on until I had one left.

I takes a while each time.

2. The version I then had was about 40 Gb, including 17 Gb of documents. Without these It would be 30 Gb, the size of the original partition.

3. I also followed Woody's advice and upgraded to latest Fusion version 2.0.8. I was originally on automatic upgrade but that had not worked.

4. At that point I could not get on the internet anymore. It took me a lot of time finding out how to do this, but you have to first turn off the virtual machine and only then you can connect the network adapter.

5. The whole system is now working without any problems and smoother and also slightly faster than with 2.0.

Pitty I cannot upgrade further than 2.0.8.

One last thing that is troubling me is how can the disk size exceed the limit of 40 Gb that is in my preferences now?

Andre and Woody, thank you for your help!

0 Kudos
a_p_
Leadership
Leadership

One last thing that is troubling me is how can the disk size exceed the limit of 40 Gb that is in my preferences now?

The 40GB you configured is for the virtual disk (the .vmdk files) only. The sum of all .vmdk files should not exceed the 40GB (plus some kB/MB overhead). However, there are also other files in the .vmwarevm package which are required for the VM to work.

If there's anything which looks strange to you please create and post (attach) the latest support bundle. This might clear up things.

André

0 Kudos
WoodyZ
Immortal
Immortal

With Time Machine I reloaded an older version of the Virtual Machines file.

It is a known fact that Time Machine is not 100% reliable backing up/restoring Virtual Machines under all circumstances/conditions.  Also backing up Virtual Machines via Time Machine is disk/time intensive and wastes a tremendous amount of space for something that may be corrupt and worthless come time to restore it.  At a minimum I would exclude Virtual Machines from Time Machine and with the Virtual Machines shutdown, not suspended, and VMware Fusion closed then manually copy the Virtual Machines Package(s) to an alternate location, preferably on to a different physical hard disk.  Then keep the User Data that is stored within the Virtual Machine backed up off of the Virtual Machine on a regular basis so as to always have a current User Data Backup.  If you have to restore a properly backed up Virtual Machine that is not as current at least you'll have a working Virtual Machine and current User Data to go forward with when you find out your Time Machine Backup of the Virtual Machine fails.

Pitty I cannot upgrade further than 2.0.8.

If the current version is doing for you what you need then I wouldn't upgrade to the next or latest major version unless you had no choice, like if you were running Lion or Mountain Lion then VMware Fusion 2.x is not supported and will not run properly, if at all.  As a general rule, I like to go with, if it works then don't fix it! Smiley Wink

One last thing that is troubling me is how can the disk size exceed the limit of 40 Gb that is in my preferences now?

Technically a virtual disk cannot grow larger then it is allocated however each snapshot you take has to potential to grow to the allocated size so remember you had 5 Snapshots so theoretically in this case it could consume 240 GB of Host Disk Space but realistically it would probably never reach the theoretical limit.  However it would not be unrealistic to consume half that amount until you deleted the snapshots and then shrank the virtual hard disk.  In other words with no snapshots and a shrunk virtual hard disk then the virtual hard disk should only consume the amount of Host hard disk space as what's shown take up from within the Guest OS however keep in mind that once shrunk it will continue to grow up to the set size as you continue to use the Virtual Machine even without any Snapshots.  Each Snapshot has its own disk that can grow to the set size so the more Snapshots you take the more it adds up and can easily consume more Host disk space then the set size of the virtual hard disk.  Hope this makes sense.

0 Kudos
oldMACdonnell
Enthusiast
Enthusiast

Hi Woody and Andre,

Thanks a lot for all your comments.

I followed up all of your advice and now my virtual disk is about 25 Gb. Operation succeeded!  Smiley Happy

After my virtual disk had grown to 47 Gb, I did the following:

1. I removed all snapshots starting with the oldest.

This will take some time, the reason was explained by you earlier in this discussion.

Some are hidden in the snapshot overview. These are the autoprotect snapshots. Uncheck the "show only snapshots" and you can see them.

Yet the result in disk space was not impressive.

2. I disabled the autoprotect function.

At the time all was OK I made a copy of the file: Documents > Virtual machines > Windows XP Home Edition on an external HDD.

This should be a sufficient back up in case the current version crashes.

Note that first Windows was shut down and then VMWare (not suspended).

Snapshot and autoprotect are great tools if you keep on changing the content of the virtual disk, but they tend to take a lot of space on your HDD.

I do not chage a lot, so a copy of the correctly working virtual disk will do for me.

I use windows for games that cannot be played on a Mac.

3. I cleaned up Windows XP

Removed all programs and files I do not need.

4. Ran clean up disk

This can be found in VMWae  Virtual machine > settings > hard disks. Press clean up, even if it says it is not necessary.

This process takes a while, I think it was 1 hour, to complete

5. Ran defrag in Windows.

This also took at least one hour.

6. Ran Shrink disk

Install VMWare Tools, then choose the shrink tab.

The process takes also at least one hour. At one point I got the message that there was not enough free disk space.

Earlier I had set my disk to 40 Gb and the calculated used amount of disk volume was 22. The program then gave a few suggestions to clean up until below 20 Gb. An then it started. After an hour or so it is completed and YES, the size of the virtual machine was about 24 Gb and the 16 Gb free space was regained by the host, Mac. I checked if all was working well, which was the case.

At this point I made a copy of the virtual machine Windows to an external HDD as mentioned under 1.

For me: problem solved. Smiley Happy

Thank you guys for all your comments and help. You are doing a great job and you certainly helped me to reduce my computer stress levels.

I learned a lot and the problem is solved. I hope this is also helpful for others.

0 Kudos