1 person found this helpful
Have you ever taken a snapshot of this machine? If so, then your preallocated disk is no longer being written to - a child disk is.
yes i have done a snapshot. Should I partition my hard disk and configure my virtual machines to use physical disks instead? Would that alleviate this problem?
No - this will not help you at all.
Only thing that helps is understanding how many disk-space is used by snapshots.
In your case - selecting a preallocated disk and then creating a snapshot wastes about 60Gb of your disks.
Don't use preallocated disks when you plan to use snapshots
This also works on a Vm Workstation 7.0 aswell
I have a Ubuntu 9.10 with a VMware 7.0. I'am using vmware to boot my physical partition of WXP.
This last days, i was getting a "Vmware has paused your VM because disk full message...." and vmware pauses my Xp vm . It"s impossible to work because the vm gets paused.
On the vmware.log, i see:
Mar 12 11:38:03.633: vmx| Msg_Question: msg.mainMemPosix.noSpace reply=0
Mar 12 11:38:04.377: vmx| Msg_Question:
Mar 12 11:38:04.377: vmx| http://msg.mainMemPosix.noSpace VMware Workstation has paused this virtual machine because the disk on which the virtual machine is stored is almost full. To continue, free up at least 33.9 MB of disk space.
This issue is caused by the "temp files" generated by the VM when its on. The file are mostely called:
*.vmem and *.vmem.lck. Just like this:
You need to specify the fallowing lines in config file and the vmx file of the virtual machine. SInce i have two location of the config file, i modified all of them....
- Edit file in /home/user/vmware/VirtualMAchine/Virtualmachine.vmx
- Edit file in /etc/vmware/config
- Edit file in /home/user/.vmware/config
For all this files, enter:
mainMem.useNamedFile = "FALSE"
tmpDirectory = "/dev/shm"
workingDir = "/root/vmware" #I specify here the /root but in your case, you need to specify a partition with sufficient space disk.
After this, /etc/init.D/vmware restart and it will resolve your disk full problems
Sorry for bringing this old post but, it"s the first post i found on Google talking about the same issue as mine that appeared after an up of VM 6.5 to 7.0
Since the post was not closed, i updated it with "a" solution for the next buddies....