![]() Why is that? (assuming you have the HDD space for the huge backups) >You mentioned that Time Machine is not always a reliable way to make sure your VM's are backed up. VMware handles the part it knows about and you need a filesystem-aware tool to handle the latter (as each guest can use a myriad of formats). Resizing a VMDK is a two part process, expanding the VMDK container capacity size and resizing the embedded filesystem. Without verifying your VMDK's consistency (with a command line vmware-vdiskmanager -R) and/or the state of the HFS+ volume that VMDK resides (with Apple Disk Utility), you could have been in a latent landmine state before making a major format change like changing the allocation format (split/monolithic) or resizing the VMDK capacity.Ģ) Any idea why the HDD didn't want to change size? It is currently listed at a 40GB capacity and I need to increase it to about 80GB (at least), however I now have very cold feet at changing anything. one thing we must infer is that you recounted what you did in a foggy state. If you don't mind someone else jumping in. I was wondering if you could help me answer a 2 questions though:ġ) Any idea what happened / what I did wrong? (other than not backing things up before making any changes) Next attach the filelist.txt file that was created on the Desktop to a reply post.Īlso the vmware.log files, (usually 4 of them), from within the target Virtual Machine Package and if you need help getting them have a look at Ls -lAF /Users/$/Documents/Virtual Machines.localized/Windows XP.vmwarevm > ~/Desktop/filelist.txtĥ. Next type the following without quotes, including leading space, then press Enter: " > ~/Desktop/filelist.txt"Įxample of the full command line in Terminal: Drag and drop the target Virtual Machine onto the Terminal and this will populate the fully qualified pathname of the Virtual Machine.Ĥ. In Fusion's Virtual Machine Library (VMware Fusion (menu bar) > Window > Virtual Machine Library), ctrl-click the target Virtual Machine and then select "Show in Finder".ģ. In a Terminal (/Applications/Utilities/Terminal), type the following without the quotes, including the trailing space, however do not press Enter yet and note that the following contains lowercase L's, not ones: "ls -lAF "Ģ. Need to see a file listing of the target Virtual Machine Package and you can use the directions below to get it in the preferred form.ġ. In the worse case (assuming no hope), is it possible to data files from the wreckage of the VM? If this file was moved, please provide its new location" This file is required to power on this virtual machine. Now, when I try to start the VM, I get the dreaded message: "File not found: Windows XP Professional.vmdk. VMWare started to do it's thing (took a very long time) and ended with a 'file not found' error'. I did a cursory check into the help files (with my foggy-sick brain) and thought that this was not the correct setting, so I unchecked it and clicked 'apply'. ![]() So I powered down and pulled up the VM Settings> Hard Disks and saw that the 'Split into 2GB Files' was checked'. I could read the files from the various folders, but explorer could not read the HDD. When I got into the VM and tried to open an explorer window, the VM coudn't read the HDD (it had that animated 'searching' icon). So I powered down the iMac completely, let it sit, then restarted everything. So I thought perhaps I need to power off the Mac in case there is some sort of HDD conflict. I tried powering the VM off and closing VMWare, but when I restarted it the VM showed a 40GB HDD (even though the settings showed it at 80). I started up the VM and the HDD was still at 40GB. I changed the VM's HDD from 40 to 80 GB and clicked apply. VMWare did it's thing and removed all of the snapshots (took a LONG time). I was prompted that I cannot make changes to the VM's HDD if there were any snapshots so (cringe) I removed them all. I needed to increase it (and have the space), so I powered down the VM and tried to change the HDD size. I have a Virtual Machine of WinXP Pro SP3 (32-bit). No need to chastize me - I am already beating myself up pretty badly. I made the supreme mistake of trying to work on my computer when I am sick and not thinking clearly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |