Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 232869

Re: unable to enlarge virtual disk

$
0
0

André Pett wrote: According to the support file the .vmdk file exists and seems to be ok!?

 

 

After a cursory review of the support bundle it looks as though the "/Virtuelle Systeme/1_active systems/Win 7 x64 Entwicklung/Win7 x64 Entwicklung.vmwarevm" Virtual Machine was pointing to the "/Virtuelle Systeme/1_active systems/Win 7 x64 Entwicklung/Windows 7 x64 Ultimate.vmwarevm/Windows 7 x64 Ultimate.vmdk" virtual hard disk and during the snapshot cleanup process it did not write the fully qualified pathname to the "Windows 7 x64 Ultimate.vmdk" in "/Virtuelle Systeme/1_active systems/Win 7 x64 Entwicklung/Windows 7 x64 Ultimate.vmwarevm" for the "scsi0:0.fileName" option in the  "/virtuelle Systeme/1_active systems/Win 7 x64 Entwicklung/Win7 x64 Entwicklung.vmwarevm/Win7 x64 Entwicklung.vmx" configuration file.

 

I gleaned this from reviewing the "/Users/broy/Library/Logs/VMware Fusion/vmware-vmfusion.log" and /virtuelle Systeme/1_active systems/Win 7 x64 Entwicklung/Win7 x64 Entwicklung.vmwarevm/vmware*.log files

 

So if what I gleaned is correct then the "scsi0:0.fileName" option in the "/virtuelle Systeme/1_active systems/Win 7 x64 Entwicklung/Win7 x64 Entwicklung.vmwarevm/Win7 x64 Entwicklung.vmx" configuration file should be the following:

 

scsi0:0.fileName = "/virtuelle Systeme/1_active systems/Win 7 x64 Entwicklung/Windows 7 x64 Ultimate.vmwarevm/Windows 7 x64 Ultimate.vmdk"

 

not

 

scsi0:0.fileName = "Windows 7 x64 Ultimate.vmdk"

 

So André, if you'd check that out I'd appreciate it.


Viewing all articles
Browse latest Browse all 232869

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>