Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
vCenter Server fails with Stack Overflow errors
Symptoms
- vCenter Server fails
- The vpxd.log file contains Stack Overflow errors similar to:
- [2009-12-03 11:37:32.876 01700 verbose 'App'] [VpxdInvtVmDb] DB:UPDATE:END Vm Id = 4816
[2009-12-03 11:37:32.891 01152 error 'App'] Win32 exception: Stack overflow (0xc00000fd)
[2009-12-03 11:37:32.891 01152 error 'App'] eip: 0x21c9c2b esp: 0x6582fec ebp: 0x6583060
[2009-12-03 11:37:32.891 01152 error 'App'] eax: 0x6585084 ebx: 00000000 ecx: 0x12e33e0 edx: 0xfffffffe edi: 0x852a298 esi: 0x000007
- [2009-12-03 11:27:56.981 02944 verbose 'App'] [VpxdInvtVm] Saving fields for USTXCARVALW05 (/vpx/vm/#5459/): FILE_NAME=sanfs://vmfs_uuid:4a92d373-28768c72-7b
2b-001cc4eb36cc/USTXCARVALW05/USTXCARVALW05.vmx, DATACENTER_ID=50
[2009-12-03 11:27:57.028 02944 verbose 'PropertyProvider'] RecordOp ASSIGN: config.npivWorldWideNameType, vm-5459
[2009-12-03 11:27:57.044 02944 verbose 'PropertyProvider'] RecordOp ASSIGN: config.hardware.device[2001].backing.fileName, vm-5459
[2009-12-03 11:27:57.044 02944 verbose 'PropertyProvider'] RecordOp ASSIGN: config.hardware.device[2001].backing.contentId, vm-5459
[2009-12-03 11:27:57.044 02944 verbose 'PropertyProvider'] RecordOp ASSIGN: config.hardware.device[2001].backing.parent.fileName, vm-5459
[2009-12-03 11:27:57.044 02944 verbose 'PropertyProvider'] RecordOp ASSIGN: config.hardware.device[2001].backing.parent.diskMode, vm-5459
[2009-12-03 11:27:57.059 02944 verbose 'PropertyProvider'] RecordOp ASSIGN: config.hardware.device[2001].backing.parent.contentId, vm-5459
[2009-12-03 11:27:57.075 02944 verbose 'PropertyProvider'] RecordOp ASSIGN: config.hardware.device[2001].backing.parent.parent.fileName, vm-5459
[2009-12-03 11:27:57.122 02944 verbose 'PropertyProvider'] RecordOp ASSIGN: config.hardware.device[2001].backing.parent.parent.diskMode, vm-5459
[2009-12-03 11:27:57.122 02944 verbose 'PropertyProvider'] RecordOp ASSIGN: config.hardware.device[2001].backing.parent.parent.contentId, vm-5459
[2009-12-03 11:27:57.122 02944 verbose 'PropertyProvider'] RecordOp ASSIGN: config.hardware.device[2001].backing.parent.parent.parent.fileName, vm-5459
[2009-12-03 11:27:57.184 02944 verbose 'PropertyProvider'] RecordOp ASSIGN: config.hardware.device[2001].backing.parent.parent.parent.diskMode, vm-5459
[2009-12-03 11:27:57.184 02944 verbose 'PropertyProvider'] RecordOp ASSIGN: config.hardware.device[2001].backing.parent.parent.parent.contentId, vm-5459
-
[2010-09-16 14:04:25.801 03612 warning 'App'] [VpxdMoHost::GetLinkedVmInt] Getting linked vm for vmid 97 on host 10.0.0.16 - COULD NOT FIND IT[2010-09-16 14:04:26.257 03612 error 'App'] Win32 exception: Stack overflow (0xc00000fd)[2010-09-16 14:04:26.257 03612 error 'App'] eip: 0x1b5e1fb esp: 0x57b2f9c ebp: 0x57b3010[2010-09-16 14:04:26.257 03612 error 'App'] eax: 0x57b5034 ebx: 00000000 ecx: 0x1302d48 edx: 0xfffffffe edi: 0x3fc7118 esi: 0x000007[2010-09-16 14:04:26.467 03424 warning 'VpxProfiler'] [VpxdHostSync] GetChanges host:1
- [2009-12-03 11:37:32.876 01700 verbose 'App'] [VpxdInvtVmDb] DB:UPDATE:END Vm Id = 4816
- In the Windows 2008 Server event logs, you see this application error for vpxd:
Faulting module DBGhelp.DLL version 6.8.4.0
- If trivia logging is enabled in vCenter Server, the vpxd.log contains errors similar to:
- [2012-01-23 15:40:19.642 06024 trivia 'App'] [Vdb::Connection::Record] Recording (3dec8b0:6) select BACKING_ID from VPX_VDEVICE_FILE_BACKING where HARD_DEVICE_BACKING_FILE_NAME = 'sanfs://vmfs_uuid:4a8c0086-1e42ed25-310a-001a64e5df4a/A-GPS-DC1/A-GPS-DC1-000065.vmdk' and VM_ID = 23 <------offending VM
[2012-01-23 15:40:19.642 06024 trivia 'App'] [VpxdDbSave] FillInUniqueKeys: no unique keys for table VPX_VDEVICE_BACKING_REL
[2012-01-23 15:40:19.642 06024 trivia 'App'] [VpxdDbSave] FillInUniqueKeys: no unique keys for table VPX_VDEVICE_FILE_BACKING_X
[2012-01-23 15:40:19.736 06024 error 'App'] Win32 exception: Stack overflow (0xc00000fd)
[2012-01-23 15:40:19.736 06024 error 'App'] eip: 0x197e1fb esp: 0x4b42fcc ebp: 0x4b43040
[2012-01-23 15:40:19.736 06024 error 'App'] eax: 0x4b45064 ebx: 00000000 ecx: 0x1302d48 edx: 0xfffffffe edi: 0x3dec8b0 esi: 0x000007
Note: The crash happens right after the last three entries.
- [2012-01-23 15:40:19.642 06024 trivia 'App'] [Vdb::Connection::Record] Recording (3dec8b0:6) select BACKING_ID from VPX_VDEVICE_FILE_BACKING where HARD_DEVICE_BACKING_FILE_NAME = 'sanfs://vmfs_uuid:4a8c0086-1e42ed25-310a-001a64e5df4a/A-GPS-DC1/A-GPS-DC1-000065.vmdk' and VM_ID = 23 <------offending VM
Cause
This error occurs when:
-
A virtual machine has too many snapshots associated with it.
-
A virtual machine is pointing to a .vmx file other than its own. This is known to happen when the virtual machine's display name is changed. The vpxd.log shows:
- [2009-12-03 11:37:22.266 05544 verbose 'App'] [VpxdInvtVm] Saving fields for USTXCARVALW06 (/vpx/vm/#5393/): FILE_NAME=sanfs://vm
fs_uuid:4a92d3cc-72355f5b-2e5c-001cc4eb36cc/USTXCARVALW05/USTXCARVALW05.vmx, DATACENTER_ID=50
-
[2009-12-03 11:37:25.094 01152 verbose 'App'] [VpxdInvtVm] Saving fields for USTXCARVALW05 (/vpx/vm/#5459/): FILE_NAME=sanfs://vm
fs_uuid:4a92d373-28768c72-7b2b-001cc4eb36cc/USTXCARVALW05/USTXCARVALW05.vmx, DATACENTER_ID=50
- [2009-12-03 11:37:22.266 05544 verbose 'App'] [VpxdInvtVm] Saving fields for USTXCARVALW06 (/vpx/vm/#5393/): FILE_NAME=sanfs://vm
Resolution
To resolve this issue:
Note: If trivia logging needs to be enabled to determine if the issue is caused due to too many snapshots for virtual machine, see Enabling trivia logging in VirtualCenter (1001584).
Note: If trivia logging needs to be enabled to determine if the issue is caused due to too many snapshots for virtual machine, see Enabling trivia logging in VirtualCenter (1001584).
-
Unregister all virtual machines that are pointing to the incorrect .vmx files from the vCenter Server inventory.
-
Right-click on the Virtual Machine > Remove from Inventory
-
Restart vCenter Server.
-
Re-register the virtual machines.
-
Right-click the datastore and choose Browse Datastore
-
Navigate to the virtual machine folder to add to the Inventory
-
Right-click the virtual machine .vmx file and click Add to Inventory
-
Follow the steps in the Add to Inventory wizard to finish adding the virtual machine in the vCenter Server
-
Notes:
- For information on locating virtual machines running on snapshots and removing snapshots, see No more space for the redo log error when attempting to start a virtual machine (1002103).
- The full path to vpxd.cfg file in Windows is %ALLUSERPROFILE%\Application Data\VMware\VMware VirtualCenter\vpxd.cfg.
Tags
Update History
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
Actions
- KB Article:
- Updated:
- Categories:
- Product Family:
- Products:
- Product Versions:

