WoodyZ schrieb:
orangebanana wrote:
Thank you for helping, WoodyZ!
So if I get you right, I can use the remove-function
("I found an option to "remove" the virtual hard disk (right-click on the OS listed in VMware -> settings -> hard discs -> advanced options -> remove hard disc). Might this be useful? To remove it and create a new one which is smaller?")
and 'reinstall' the OSes without actually deleting the OSes? So basically I won't even need the WinXP \ Win7 discs to fix this? If so, how do I do that? Or will I have to delete the OSes and make a whole new copy of the Windows-files?
If you delete the existing virtual hard disks and empty the Trash the installed OS are gone and you have no choice but to reinstall using the installation media. The other option if you want to use what's already installed but transfer it to a smaller disk requires imaging software and then swap out the disks however you said you didn't want to have to use other software so just delete the VM and start over setting the size of the virtual hard disk before starting the install and be done with this!
Alright then, I am going to start this now and tell you if it worked later. It's 3:30 am
.
According to info in the support bundle the two VM are currently only sin less then 10 GB Host disk space when not running. When running an addition amount of space it temporarily used by the .vmem file for each VM in the size of the RAM allocated for each. This is then released when shutdown, not suspended.
This is really weird as I am currently not running any further OSes, not even VMware and the disk space is still as low as before. The virtual machines which are located in my documents-folder take about 10GB and when I say 40GB are "gone", I don't mean those 10GB. Bottom line, the whole installation of those virtual machines took 50GB of which 10GB are the virtual machines I can actually see as files and the 40GB for WinXP, whatever happened to those. The 60GB actually used for Win7 are not gone, even though. It's very confusing.
The size of the non pre-allocated disk is not how much space it initially takes on the Host's Filesystem and even though between the two VM they are 100 GB for the two virtual hard disks they currently take up less then 10 GB when not running and an additional 2.5 GB for the two .vmem files when running so whatever other Host disk space you're missing it has nothing to do with these two VM's at the moment.
I don't really understand that. Or maybe I do? Mac OS does not use the information that the virtual hard drives actually "take space" 40GB\60GB? So this really is all about actual files "being there" and not about VMware creating a boarder around the virtual hard disks so that the space can't be used by Mac OS anymore? So basically, the 40GB "loss" has to be caused by something else but VMware\windows-installations? Well, at least I just found out that deleting the OSes installed in VMware Fusion won't bring back the 40GB.
EDIT:
So basically, when it comes to RAM, the virtual machine backups the RAM in the .vmem files and the RAM itself is only used by WinXP\Win7 when its actually running? Or did I understand that wrong?
Yes that's correct and when the VM is shutdown, not suspended, the disk space released as the file is deleted. The RAM becomes accessible to the Host when the Virtual Machine is not running.
.
Thanks again for your help!
EDIT:
Well, I tried restarting the whole process of installing WinXP but the same will happen. It won't let me change the settings (40GB of disk space and 510MB of RAM). The only thing I can change is the location of the virtual machine. I added two screenshots of the windows showing this step of installation.