Corrupted vm image, call for a vmware expert.

ufmale · 04-22-2009, 10:15 PM

I have fedora vmware on my xp machine. Today, when i start the fedora vm, it tries to restore state and shows a pop up error message as follows:

=======================================================
VMware Player unrecoverable error: (vmx)
Exception 0xc0000006 (disk error while paging) has occurred.
A log file is available in "C:\vm\fedora-7-i386\vmware.log". A core file is available in "C:\vm\fedora-7-i386\vmware-vmx-4108.dmp". Please request support and include the contents of the log file and core file.
To collect data to submit to VMware support, run "vm-support".
We will respond on the basis of your support entitlement.
==========================================================

In fact, this is not the only time it happens. It also happens awhile back, but i just choose to ignore the problem by replacing the corrupt vm image with a new one. I am really curious what cause the problem and if there is any way i can fix it (or avoid this type of problem).

There are also a log files containg information that I do not understand. If anyone would like to see I will post it here.

irishbitte · 04-23-2009, 07:59 PM

Please post the files, they will hopefully explain what is happening to your vmx

ufmale · 04-24-2009, 02:24 AM

Here is the vmware.log

Code:

Apr 24 03:17:12.682: vmx|   checksum 0x0013dc6b timestamp 0x42e5be93
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\ole32.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2726
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x77dd0000 size 0x0x0009b000
Apr 24 03:17:12.682: vmx|   checksum 0x000a0de4 timestamp 0x411096a7
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\advapi32.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x77e70000 size 0x0x00092000
Apr 24 03:17:12.682: vmx|   checksum 0x0008ec00 timestamp 0x46923396
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\rpcrt4.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.3173
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x77fe0000 size 0x0x00011000
Apr 24 03:17:12.682: vmx|   checksum 0x0001a281 timestamp 0x411096c1
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\secur32.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x7c9c0000 size 0x0x00816000
Apr 24 03:17:12.682: vmx|   checksum 0x008166c2 timestamp 0x472160d2
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\shell32.dll
Apr 24 03:17:12.682: vmx|   file version 6.0.2900.3241
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x77f60000 size 0x0x00076000
Apr 24 03:17:12.682: vmx|   checksum 0x0007dd11 timestamp 0x48f7194f
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\shlwapi.dll
Apr 24 03:17:12.682: vmx|   file version 6.0.2900.3462
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x74ae0000 size 0x0x00007000
Apr 24 03:17:12.682: vmx|   checksum 0x0000593f timestamp 0x4110969d
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\cfgmgr32.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x77920000 size 0x0x000f3000
Apr 24 03:17:12.682: vmx|   checksum 0x000f596b timestamp 0x411096b0
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\setupapi.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x71ab0000 size 0x0x00017000
Apr 24 03:17:12.682: vmx|   checksum 0x0002030b timestamp 0x411096f2
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\ws2_32.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x71aa0000 size 0x0x00008000
Apr 24 03:17:12.682: vmx|   checksum 0x0000aff6 timestamp 0x411096f3
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\ws2help.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x77120000 size 0x0x0008b000
Apr 24 03:17:12.682: vmx|   checksum 0x00086dd3 timestamp 0x47559e94
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\oleaut32.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.3266
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x72280000 size 0x0x0002a000
Apr 24 03:17:12.682: vmx|   checksum 0x000295b2 timestamp 0x411096af
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\dinput.dll
Apr 24 03:17:12.682: vmx|   file version 5.3.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x76b40000 size 0x0x0002d000
Apr 24 03:17:12.682: vmx|   checksum 0x0002ed0a timestamp 0x411096d6
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\winmm.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x73f10000 size 0x0x0005c000
Apr 24 03:17:12.682: vmx|   checksum 0x0006138b timestamp 0x411096d4
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\dsound.dll
Apr 24 03:17:12.682: vmx|   file version 5.3.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x77c00000 size 0x0x00008000
Apr 24 03:17:12.682: vmx|   checksum 0x00011d78 timestamp 0x411096b7
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\version.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x77a80000 size 0x0x00094000
Apr 24 03:17:12.682: vmx|   checksum 0x00096491 timestamp 0x41109691
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\crypt32.dll
Apr 24 03:17:12.682: vmx|   file version 5.131.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x77b20000 size 0x0x00012000
Apr 24 03:17:12.682: vmx|   checksum 0x000116ad timestamp 0x411096e3
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\msasn1.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x5ed00000 size 0x0x000cc000
Apr 24 03:17:12.682: vmx|   checksum 0x000b130c timestamp 0x411096f8
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\opengl32.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x68b20000 size 0x0x00020000
Apr 24 03:17:12.682: vmx|   checksum 0x0002db90 timestamp 0x41109697
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\glu32.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x73760000 size 0x0x00049000
Apr 24 03:17:12.682: vmx|   checksum 0x0004d982 timestamp 0x411096a0
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\ddraw.dll
Apr 24 03:17:12.682: vmx|   file version 5.3.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x73bc0000 size 0x0x00006000
Apr 24 03:17:12.682: vmx|   checksum 0x00008edf timestamp 0x4110969f
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\dciman32.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x76380000 size 0x0x00005000
Apr 24 03:17:12.682: vmx|   checksum 0x00005405 timestamp 0x41109727
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\msimg32.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x76d60000 size 0x0x00019000
Apr 24 03:17:12.682: vmx|   checksum 0x0001a172 timestamp 0x446dc13d
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\iphlpapi.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2912
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x723d0000 size 0x0x0001c000
Apr 24 03:17:12.682: vmx|   checksum 0x000215c4 timestamp 0x411096b4
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\winscard.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x76f50000 size 0x0x00008000
Apr 24 03:17:12.682: vmx|   checksum 0x00008c06 timestamp 0x41109703
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\wtsapi32.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x76360000 size 0x0x00010000
Apr 24 03:17:12.682: vmx|   checksum 0x00014d19 timestamp 0x411096b8
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\winsta.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x5b860000 size 0x0x00054000
Apr 24 03:17:12.682: vmx|   checksum 0x00058895 timestamp 0x48f62113
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\netapi32.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.3462
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x76d80000 size 0x0x0001e000
Apr 24 03:17:12.682: vmx|   checksum 0x00027e80 timestamp 0x446dc13d
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\dhcpcsvc.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2912
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x76f20000 size 0x0x00027000
Apr 24 03:17:12.682: vmx|   checksum 0x00027283 timestamp 0x485bebb6
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\dnsapi.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.3394
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x4d4f0000 size 0x0x00058000
Apr 24 03:17:12.682: vmx|   checksum 0x00055d26 timestamp 0x411096d3
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\winhttp.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x10000000 size 0x0x0006a000
Apr 24 03:17:12.682: vmx|   checksum 0x0006e87f timestamp 0x48ad293e
Apr 24 03:17:12.682: vmx|   image file C:\Program Files\VMware\VMware Player\vmcryptolib.DLL
Apr 24 03:17:12.682: vmx|   file version 6.5.0.4136
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x76390000 size 0x0x0001d000
Apr 24 03:17:12.682: vmx|   checksum 0x0002a024 timestamp 0x411096ae
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\imm32.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x629c0000 size 0x0x00009000
Apr 24 03:17:12.682: vmx|   checksum 0x000094b6 timestamp 0x411096aa
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\lpk.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x74d90000 size 0x0x0006b000
Apr 24 03:17:12.682: vmx|   checksum 0x000656c9 timestamp 0x411096ba
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\usp10.dll
Apr 24 03:17:12.682: vmx|   file version 1.420.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x773d0000 size 0x0x00103000
Apr 24 03:17:12.682: vmx|   checksum 0x0010f2bd timestamp 0x44ef1b33
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\comctl32.dll
Apr 24 03:17:12.682: vmx|   file version 6.0.2900.2982
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x636e0000 size 0x0x00029000
Apr 24 03:17:12.682: vmx|   checksum 0x0002c65a timestamp 0x489b9df1
Apr 24 03:17:12.682: vmx|   image file C:\Program Files\Spyware Doctor\smumhook.dll
Apr 24 03:17:12.682: vmx|   file version 6.0.0.2
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x5ad70000 size 0x0x00038000
Apr 24 03:17:12.682: vmx|   checksum 0x0003e638 timestamp 0x411096bb
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\uxtheme.dll
Apr 24 03:17:12.682: vmx|   file version 6.0.2900.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x63000000 size 0x0x00014000
Apr 24 03:17:12.682: vmx|   checksum 0000000000 timestamp 0x46bd1138
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\SynTPFcs.dll
Apr 24 03:17:12.682: vmx|   file version 7.5.17.25
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x0fb00000 size 0x0x000df000
Apr 24 03:17:12.682: vmx|   checksum 0x000e104d timestamp 0x460435d7
Apr 24 03:17:12.682: vmx|   image file C:\Program Files\VMware\VMware Player\libeay32.dll
Apr 24 03:17:12.682: vmx|   file version 0.9.7.100
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x71ad0000 size 0x0x00009000
Apr 24 03:17:12.682: vmx|   checksum 0x00012c31 timestamp 0x411096ff
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\wsock32.dll
Apr 24 03:17:12.682: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x7c360000 size 0x0x00056000
Apr 24 03:17:12.682: vmx|   checksum 0x0005bf56 timestamp 0x44b451e8
Apr 24 03:17:12.682: vmx|   image file C:\WINDOWS\system32\MsVcR71.dll
Apr 24 03:17:12.682: vmx|   file version 7.10.6030.0
Apr 24 03:17:12.682: vmx| CoreDump: including module base 0x0x097f0000 size 0x0x00027000
Apr 24 03:17:12.682: vmx|   checksum 0x0002f8c3 timestamp 0x460435ed
Apr 24 03:17:12.682: vmx|   image file C:\Program Files\VMware\VMware Player\ssleay32.dll
Apr 24 03:17:12.682: vmx|   file version 0.9.7.100
Apr 24 03:17:12.692: vmx| CoreDump: including module base 0x0x0ffd0000 size 0x0x00028000
Apr 24 03:17:12.692: vmx|   checksum 0x0002a6dc timestamp 0x40eb5d28
Apr 24 03:17:12.692: vmx|   image file C:\WINDOWS\system32\rsaenh.dll
Apr 24 03:17:12.692: vmx|   file version 5.1.2600.2161
Apr 24 03:17:12.692: vmx| CoreDump: including module base 0x0x76780000 size 0x0x00009000
Apr 24 03:17:12.692: vmx|   checksum 0x0000774e timestamp 0x411096b8
Apr 24 03:17:12.692: vmx|   image file C:\WINDOWS\system32\shfolder.dll
Apr 24 03:17:12.692: vmx|   file version 6.0.2900.2180
Apr 24 03:17:12.692: vmx| CoreDump: including module base 0x0x77690000 size 0x0x00021000
Apr 24 03:17:12.692: vmx|   checksum 0x0001ffbf timestamp 0x411096ce
Apr 24 03:17:12.692: vmx|   image file C:\WINDOWS\system32\ntmarta.dll
Apr 24 03:17:12.692: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.692: vmx| CoreDump: including module base 0x0x76f60000 size 0x0x0002c000
Apr 24 03:17:12.692: vmx|   checksum 0x0003811e timestamp 0x411096bb
Apr 24 03:17:12.692: vmx|   image file C:\WINDOWS\system32\wldap32.dll
Apr 24 03:17:12.692: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.692: vmx| CoreDump: including module base 0x0x71bf0000 size 0x0x00013000
Apr 24 03:17:12.692: vmx|   checksum 0x00019c51 timestamp 0x411096ad
Apr 24 03:17:12.692: vmx|   image file C:\WINDOWS\system32\samlib.dll
Apr 24 03:17:12.692: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.692: vmx| CoreDump: including module base 0x0x71a50000 size 0x0x0003f000
Apr 24 03:17:12.692: vmx|   checksum 0x0004aa81 timestamp 0x485bebb6
Apr 24 03:17:12.692: vmx|   image file C:\WINDOWS\system32\mswsock.dll
Apr 24 03:17:12.692: vmx|   file version 5.1.2600.3394
Apr 24 03:17:12.692: vmx| CoreDump: including module base 0x0x76fc0000 size 0x0x00006000
Apr 24 03:17:12.692: vmx|   checksum 0x0000a47c timestamp 0x44a01b46
Apr 24 03:17:12.692: vmx|   image file C:\WINDOWS\system32\rasadhlp.dll
Apr 24 03:17:12.692: vmx|   file version 5.1.2600.2938
Apr 24 03:17:12.692: vmx| CoreDump: including module base 0x0x0a4d0000 size 0x0x00115000
Apr 24 03:17:12.692: vmx|   checksum 0x0010087a timestamp 0x46fc2029
Apr 24 03:17:12.692: vmx|   image file C:\Program Files\VMware\VMware Player\dbghelp.dll
Apr 24 03:17:12.692: vmx|   file version 6.8.4.0
Apr 24 03:17:12.692: vmx| CoreDump: including module base 0x0x76c30000 size 0x0x0002e000
Apr 24 03:17:12.692: vmx|   checksum 0x0003069e timestamp 0x411096b9
Apr 24 03:17:12.692: vmx|   image file C:\WINDOWS\system32\wintrust.dll
Apr 24 03:17:12.692: vmx|   file version 5.131.2600.2180
Apr 24 03:17:12.692: vmx| CoreDump: including module base 0x0x76c90000 size 0x0x00028000
Apr 24 03:17:12.692: vmx|   checksum 0x0002e238 timestamp 0x411096a9
Apr 24 03:17:12.692: vmx|   image file C:\WINDOWS\system32\imagehlp.dll
Apr 24 03:17:12.692: vmx|   file version 5.1.2600.2180
Apr 24 03:17:12.692: vmx| CoreDump: including module base 0x0x74ad0000 size 0x0x00008000
Apr 24 03:17:12.692: vmx|   checksum 0x00012759 timestamp 0x411096c5
Apr 24 03:17:12.692: vmx|   image file C:\WINDOWS\system32\powrprof.dll
Apr 24 03:17:12.692: vmx|   file version 6.0.2900.2180
Apr 24 03:17:12.692: vmx| CoreDump: Including thread 6632
Apr 24 03:17:12.692: vmx| CoreDump: Including thread 700
Apr 24 03:17:12.692: vmx| CoreDump: Including thread 5776
Apr 24 03:17:13.002: vmx| ----Backtrace using dbghelp.dll----
Apr 24 03:17:13.002: vmx| Module path: C:\Program Files\VMware\VMware Player\vmware-vmx.exe
Apr 24 03:17:13.002: vmx| backtrace[00] frame 0x0012faf8 IP 0x0060dd77 params 0 0 0x12fb44 0x1e300 [C:\Program Files\VMware\VMware Player\vmware-vmx.exe base 0x00400000 0x0001:0x0020cd77] (no symbol information): 487
Apr 24 03:17:13.032: vmx| backtrace[01] frame 0x0012fb14 IP 0x0060dfaf params 0x1e300 0x1e340 0x2 0xa38eca0 [C:\Program Files\VMware\VMware Player\vmware-vmx.exe base 0x00400000 0x0001:0x0020cfaf] (no symbol information): 487
Apr 24 03:17:13.032: vmx| backtrace[02] frame 0x0012fb4c IP 0x0060e680 params 0x23c00 0xaa692a1 0xa38eca0 0xa38eca0 [C:\Program Files\VMware\VMware Player\vmware-vmx.exe base 0x00400000 0x0001:0x0020d680] (no symbol information): 487
Apr 24 03:17:13.032: vmx| backtrace[03] frame 0x0012fb6c IP 0x0060eda2 params 0xa38eca0 0xa82840 0xffff 0x12feac [C:\Program Files\VMware\VMware Player\vmware-vmx.exe base 0x00400000 0x0001:0x0020dda2] (no symbol information): 487
Apr 24 03:17:13.032: vmx| backtrace[04] frame 0x0012fb80 IP 0x0051b34a params 0xa38eca0 0xaa683e8 0xaa683e8 0 [C:\Program Files\VMware\VMware Player\vmware-vmx.exe base 0x00400000 0x0001:0x0011a34a] (no symbol information): 487
Apr 24 03:17:13.032: vmx| backtrace[05] frame 0x0012feac IP 0x0043a635 params 0xa38eca0 0x973c30 0x45944a 0x78134b6c [C:\Program Files\VMware\VMware Player\vmware-vmx.exe base 0x00400000 0x0001:0x00039635] (no symbol information): 487
Apr 24 03:17:13.032: vmx| backtrace[06] frame 0x0012fed0 IP 0x0043b5be params 0x78134b6c 0xa383770 0 0xa1f1c58 [C:\Program Files\VMware\VMware Player\vmware-vmx.exe base 0x00400000 0x0001:0x0003a5be] (no symbol information): 487
Apr 24 03:17:13.032: vmx| backtrace[07] frame 0x0012fee8 IP 0x00405cec params 0 0x78134b6c 0xa383770 0x366501 [C:\Program Files\VMware\VMware Player\vmware-vmx.exe base 0x00400000 0x0001:0x00004cec] (no symbol information): 487
Apr 24 03:17:13.032: vmx| backtrace[08] frame 0x0012ff1c IP 0x004062f6 params 0x6 0x366570 0x12ffc0 0x40193a [C:\Program Files\VMware\VMware Player\vmware-vmx.exe base 0x00400000 0x0001:0x000052f6] (no symbol information): 487
Apr 24 03:17:13.032: vmx| backtrace[09] frame 0x0012ff2c IP 0x00405048 params 0x400000 0 0x20bc2 0xa [C:\Program Files\VMware\VMware Player\vmware-vmx.exe base 0x00400000 0x0001:0x00004048] (no symbol information): 487
Apr 24 03:17:13.032: vmx| backtrace[10] frame 0x0012ffc0 IP 0x0040193a params 0x150000 0x375e3f8 0x7ffde000 0xffffffffc0000006 [C:\Program Files\VMware\VMware Player\vmware-vmx.exe base 0x00400000 0x0001:0x0000093a] (no symbol information): 487
Apr 24 03:17:13.032: vmx| backtrace[11] frame 0x0012fff0 IP 0x7c816fd7 params 0x401aaa 0 0x78746341 0x20 [C:\WINDOWS\system32\kernel32.dll base 0x7c800000 0x0001:0x00015fd7] (RegisterWaitForInputIdle + 0x0049)
Apr 24 03:17:13.052: vmx| ----End of backtrace----
Apr 24 03:17:13.052: vmx| Warning: the system was unable to load a page of memory; this can be caused by network problems or a failing hard disk drive.
Apr 24 03:17:13.052: vmx| 
Apr 24 03:17:13.052: vmx| Msg_Post: Error
Apr 24 03:17:13.052: vmx| [msg.log.error.unrecoverable] VMware Player unrecoverable error: (vmx)
Apr 24 03:17:13.052: vmx| Exception 0xc0000006 (disk error while paging) has occurred.
Apr 24 03:17:13.052: vmx| [msg.panic.haveLog] A log file is available in "C:\vm\fedora-7-i386\vmware.log".  [msg.panic.haveCore] A core file is available in "C:\vm\fedora-7-i386\vmware-vmx-4456.dmp".  [msg.panic.requestSupport.withLogAndCore] Please request support and include the contents of the log file and core file.  [msg.panic.requestSupport.vmSupport.windowsOrLinux.player] 
Apr 24 03:17:13.052: vmx| To collect data to submit to VMware support, run "vm-support".
Apr 24 03:17:13.052: vmx| [msg.panic.response] We will respond on the basis of your support entitlement.
Apr 24 03:17:13.052: vmx| ----------------------------------------

irishbitte · 04-26-2009, 04:17 AM

Hi again,

This line:

Quote:

Apr 24 03:17:13.052: vmx| Warning: the system was unable to load a page of memory; this can be caused by network problems or a failing hard disk drive.

is the one that interests me most! Have you got fedora running on a windows server host?

What I would be afraid of is that your physical hard disk is failing. You say this happened before:

Quote:

It also happens awhile back, but i just choose to ignore the problem by replacing the corrupt vm image with a new one.

I wouldn't recommend that course of action! Failure to act is failure on your part, so for what it's worth, deal with this issue now.

unSpawn · 04-26-2009, 05:21 AM

To be more specific: the VMware Knowledge base tells you to check the VM hosts' HD for failures when you encounter a 0xc0000006.
I agree with Irishbitte that ostrich behaviour may seem convenient but it just isn't a good practice. Errors do not go away by ignoring them.

irishbitte · 04-26-2009, 08:18 AM

You should look at:
1. Backing up everything you can from the XP host machine
2. Buy a new hard disk and install it
OR
2. Get an IT person to replace hard disk
3. reinstall whatever you need.

unSpawn · 04-26-2009, 08:52 AM

Quote:

Originally Posted by irishbitte

1. Backing up everything you can from the XP host machine

...making backups never hurt anyone, but

Quote:

Originally Posted by irishbitte

2. Buy a new hard disk and install it

...the exception error does not automagically mean a faulty HD, it can easily be a filesystem error.

irishbitte · 04-26-2009, 09:43 AM

Ok, I accept your point unSpawn, but can you explain how you would go about checking the HDD in Windows XP for the OP? Because this:

Quote:

the exception error does not automagically mean a faulty HD, it can easily be a filesystem error.

may well be the case, but I don't fancy the job of trying to figure out whether or not that is the case. That is up to the OP to decide. If it is a corrupt filesystem, what would you do?

unSpawn · 04-26-2009, 10:08 AM

Checking consistency should be as easy as running 'ntfsresize -vnfi /dev/NTFS_partition' or 'fsck.vfat -vn /dev/VFAT_partition' from GNU/Linux or 'chkdsk %DRIVELETTER' from cmd. If all appears consistent on that level then I'd run a full SMART test.

irishbitte · 04-26-2009, 10:32 AM

For the uninitiated, what is a SMART test?

unSpawn · 04-26-2009, 10:46 AM

"Self-Monitoring, Analysis and Reporting Technology".

ufmale · 04-26-2009, 05:35 PM

Quote:

Originally Posted by irishbitte

Hi again,

This line: is the one that interests me most! Have you got fedora running on a windows server host?

What I would be afraid of is that your physical hard disk is failing. You say this happened before:
I wouldn't recommend that course of action! Failure to act is failure on your part, so for what it's worth, deal with this issue now.

This image has been working on my window host for quite some time, but it just decided to stop couple of days ago.
I ran the chkdisk on my harddisk, but couldn't find any problem. I was afraid that the vmware disk image itself is actually corrupted somehow.
Are there any approach to fix this image? I think one of fedora-7-i386-s00*.vmdk that is corrupted (there are 4 of them).

I have started to use a backup vm image now, but still want to try to fix the corrupted one in case it fails again in the future.