On Wednesday 06 December 2006 19:05, [EMAIL PROTECTED] wrote: > > never had this happen before. > > usually you have to remove the VM from the list of servers in the > > "inventory" first. > > then blow away the files. > > possibly something is still holding them open. > > you could always reboot the host server and then try deleting the files. > > Ben > > Thanks for replying, Ben. > > I did remove the first VM from the inventory before creating the second > one, thinking that that would release the 8GB. I didn't remove the > second VM before uninstalling the application, foolishly thinking that > the first 8GB had already been released and that uninstalling would put > an end to the allocation of the second 8MB. > > I have rebooted the host, but df -h still shows that 29GB out of 36GB on > the / partition are used, whereas, before I started this foolhardy > adventure, it showed that only 13GB had been used. > > I've also searched for directories and files with vmware in their name > and deleted all of them (or almost all), but that hasn't hit the jackpot > yet. I'll keep on with that.
When you created and setup your vmware you specified where the files were: /var/lib/vmware/Virtual Machines is the default place. I must say I've got toys loose in the attic: I cannot get a downloaded VM to work, or even 1 I've made to work for another user, despite chowning the files. EG jam creates a VM. chown -R mary ThisVMName. Mary can't use the VM :-(. I get a DL VM belonging to (say) carlos, no such user all owned by 1012 chown to jam and jam does not have permission to run ??? [open VM <click>, same as if you had not pressed <click>] James -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
