VMware logfiles are very useful to debug problems with virtual
They can be used to restore lost vmx-files and even lost virtual-disk
"FLOPPYLIB-IMAGE: Invalid boot sector: signature 00, sector size 0, sectors 0"
If a VMware.log contains this line - the VM never got past a black screen at boot - it hangs forever.
This problem occurs when you use an unformatted floppyimage - connected
You may want to set the floppy to start disconnected.
Or send an email with "diagnostic logstrings" to the webmaster
at sanbarrow dot com.
More on the VMbrowser / Diskreport-project:
|"vmx| VMX exit."||clean exit||VMware has cleanly exited||nothing to do|
|"vmx| DUMPER: Dumper_EndRestore"||clean resume||looks like this VM has beed resumed cleanly||nothing to do|
|"vmx| DUMPER: Creating checkpoint file"||clean suspend||looks like this VM has been suspended cleanly||nothing to do|
|"vmx| VMXVmdbCbVmVmxExecState: Exec state change requested to state poweredOff without reset"||manual poweroff||VM has been stopped via the "Stop-button"||nothing to do|
|"vcpu-0| CPU reset: hard"||clean start||VM has been initialized successfully||nothing to do|
|"FLOPPYLIB-IMAGE: Invalid boot sector: signature 00, sector size 0, sectors 0"||unformatted flp bug||VM hangs forever at bootup||set the floppy to start disconnected|
|"Grain #* @* is orphaned. "||sparsedisk broken||a growing disk is corrupted||EMERGENCY: use vdk or forensic tools to recover your data|
|"msg.disklib.tooBigForFS"||file too large||VMware can't handle the filesystem||try to add:
diskLib.sparseMaxFileSizeCheck = "FALSE"
|"tripple fault"||tripple fault||serious - immediate crash - no core-dump||DO NOT START AGAIN- needs indepth troubleshooting|
Above are some examples for useful strings.