GUI Panic while defragmenting a vmdk

[continuum]

Trying to use the "defragment" feature that is available when you click "Utilities"  crashes the Workstation GUI.
Running VMs are not affected.

WS 8 could handle the same vmdk  - a mean one as I have to admit   - without any problems.

2012-09-13T23:26:46.329+02:00| vmui| I120: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB
2012-09-13T23:26:46.611+02:00| vmui| I120: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB
2012-09-13T23:26:46.673+02:00| vmui| I120: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB
2012-09-13T23:26:49.814+02:00| vmui| I120: MKSInterfaceIsVMKBDInstalled: OpenService failed, error: 1060
2012-09-13T23:26:50.001+02:00| vmui| I120: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB
2012-09-13T23:26:50.189+02:00| vmui| I120: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB
2012-09-13T23:26:50.204+02:00| vmui| I120: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB
2012-09-13T23:26:50.204+02:00| vmui| I120: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB
2012-09-13T23:28:22.017+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [0]: "32tb-s001.vmdk" (0x18)
2012-09-13T23:28:23.470+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [1]: "32tb-s002.vmdk" (0x18)
2012-09-13T23:28:24.892+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [2]: "32tb-s003.vmdk" (0x18)
2012-09-13T23:28:26.314+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [3]: "32tb-s004.vmdk" (0x18)
2012-09-13T23:28:27.736+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [4]: "32tb-s005.vmdk" (0x18)
2012-09-13T23:28:29.142+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [5]: "32tb-s006.vmdk" (0x18)
2012-09-13T23:28:30.579+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [6]: "32tb-s007.vmdk" (0x18)
2012-09-13T23:28:31.986+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [7]: "32tb-s008.vmdk" (0x18)
2012-09-13T23:28:33.392+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [8]: "32tb-s009.vmdk" (0x18)
2012-09-13T23:28:34.798+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [9]: "32tb-s010.vmdk" (0x18)
2012-09-13T23:28:36.220+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [10]: "32tb-s011.vmdk" (0x18)
2012-09-13T23:28:37.626+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [11]: "32tb-s012.vmdk" (0x18)
2012-09-13T23:28:39.064+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [12]: "32tb-s013.vmdk" (0x18)
2012-09-13T23:28:40.501+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [13]: "32tb-s014.vmdk" (0x18)
2012-09-13T23:28:41.939+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [14]: "32tb-s015.vmdk" (0x18)
2012-09-13T23:28:43.345+02:00| vthread-5| I120: DISKLIB-DSCPTR: Opened [15]: "32tb-s016.vmdk" (0x18)
2012-09-13T23:28:43.345+02:00| vthread-5| I120: DISKLIB-LINK  : Opened 'R:\2tb-vm-test\32tb.vmdk' (0x18): twoGbMaxExtentSparse, 68283269120 sectors / 31.8 TB.
2012-09-13T23:28:43.345+02:00| vthread-5| I120: DISKLIB-LIB   : Opened "R:\2tb-vm-test\32tb.vmdk" (flags 0x18, type twoGbMaxExtentSparse).
2012-09-13T23:28:43.970+02:00| vthread-5| I120: DISKLIB-SPARSE: FRAGMENTATION=0% ngt=65120 ngf=4 nga=2850
2012-09-13T23:28:44.595+02:00| vthread-5| I120: DISKLIB-SPARSE: FRAGMENTATION=0% ngt=65120 ngf=0 nga=0
2012-09-13T23:28:45.423+02:00| vthread-5| I120: DISKLIB-SPARSE: FRAGMENTATION=0% ngt=65120 ngf=0 nga=0
2012-09-13T23:28:48.923+02:00| vthread-5| I120: DISKLIB-SPARSE: FRAGMENTATION=0% ngt=65120 ngf=0 nga=0
2012-09-13T23:28:49.345+02:00| vthread-5| I120: MEM_ALLOC d:\build\ob\bora-812388\bora\lib\public\memaligned.h:193
2012-09-13T23:28:49.345+02:00| vthread-5| I120: Backtrace:
2012-09-13T23:28:49.345+02:00| vthread-5| W110: CoreDump: SymInitializeW() failed: 127
2012-09-13T23:28:49.345+02:00| vthread-5| W110: Win32 object usage: GDI 1448, USER 1004
2012-09-13T23:28:49.345+02:00| vthread-5| I120: CoreDump_CoreDump: faking exception to get context
2012-09-13T23:28:49.345+02:00| vthread-5| I120: Msg_Post: Error
2012-09-13T23:28:49.345+02:00| vthread-5| I120: [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (vthread-5)
2012-09-13T23:28:49.345+02:00| vthread-5| I120+ MEM_ALLOC d:\build\ob\bora-812388\bora\lib\public\memaligned.h:193
2012-09-13T23:28:49.345+02:00| vthread-5| I120: [msg.panic.haveLog] A log file is available in "E:\temp\vmware-Administrator\vmware-ui-5956.log". 
2012-09-13T23:28:49.345+02:00| vthread-5| I120: [msg.panic.requestSupport.withoutLog] You can request support. 
2012-09-13T23:28:49.345+02:00| vthread-5| I120: [msg.panic.requestSupport.vmSupport.windowsOrLinux]
...

full log is attached

[Felix-The-Cat]

Hi Ulli,

Could  you please provide more info regarding Hosts (Windows Server 2003 Enterprise Edition Service Pack 2 - as I see in the log) and Guest (especialy!) config - OS, CPU, RAM, Video, etc...

---------------

Cheers

FTC

[continuum]

Host is 2k3 EE Sp2 32bit running a Dell Optiplex 980 with 8 Gb RAM

GuestOS is  vmkernel5 using some extra-large split sparse vmdks.

Latest vmware.log is attached - that was after the GUI crash

[Felix-The-Cat]

Uli,

I think vmware.log (118.5 K) belongs to Capture Movie records black frames discussion :smileycool:

[continuum]

No - thats the correct vmware.log of the same VM that produced the UI crash before.
You wanted to have details about the VM - here they are

[Felix-The-Cat]

Thanks Ulli :smileycool:

----------------------

Cheers

[Felix-The-Cat]

Reply from development:

<<  Filed a bug...

I think that only workaround is to use 64bit VMware on Linux - there we have 64bit UI, which should not crash.  32bit UI on either Linux or Windows will die. >>

------------------

Cheers

FTC

[continuum]

> 32bit UI on either Linux or Windows will die.

whats the problem ?
I used the same function against other vmdks without crash.

Is it the halfdead vmdk or the size of it ?