VMware Cloud Community
dmgenesys
Contributor
Contributor

VC 2.5 and ESX 3.5 U2 Upgrade - now DRS Rules crash VMware VirtualCenter Server

Another serious issue following the upgrade -- we haven't used DRS rules before (prior to upgrade) Now per recommendation from VMware - I started playing with Rules that would group simillar VMs. Within minutes of enabling the rule - the VC service crashed... Nothing changed - just added the rule. Disabling the rule (not deleting - only disable) stopped the crash. Played with the bunch of things - no matter what - only disabling will stop the crash. Anyone has ideas? Did somebody experience it in previous versions? Where should I look? Any pointers are appreciated.

... And any crash produces this type of enty in vpxd log (if other logs are needed - let me know):

Drmdump written: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs/drmdump/cluster8/12862705033240-proposeActions.dump

Win32 exception: Access Violation (0xc0000005)

Read (0) at address 0xea007800

eip: 0xea007800 esp: 0x564f018 ebp: 0x564f060

eax: 0x6b63108 ebx: 0x6a961e4 ecx: 0x65cc528 edx: 0xe9ffff edi: 00000000 esi: 0x6a961d8

Exception: Win32 exception

Backtrace:

backtrace[00] eip 0x0127e3e6 ?GenerateCoreDump@System@Vmacore@@YAXXZ

backtrace[01] eip 0x011c6d3a ?CreateBacktrace@SystemFactoryImpl@System@Vmacore@@UAEXAAV?$Ref@VBacktrace@System@Vmacore@@@3@@Z

backtrace[02] eip 0x011a000e ??0Throwable@Vmacore@@QAE@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z

backtrace[03] eip 0x011a06e7 ?PanicExit@Vmacore@@YAXABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z

backtrace[04] eip 0x01282a77 ?GetThisThread@System@Vmacore@@YAPAVThread@12@XZ

backtrace[05] eip 0x7c359c97 __CxxLongjmpUnwind

backtrace[06] eip 0x7c359629 __CxxExceptionFilter

backtrace[07] eip 0x7c3598ad __CxxExceptionFilter

backtrace[08] eip 0x7c35994a __CxxExceptionFilter

backtrace[09] eip 0x7c359b9d __CxxFrameHandler

backtrace[10] eip 0x7c828752 RtlRaiseStatus

backtrace[11] eip 0x7c828723 RtlRaiseStatus

backtrace[12] eip 0x7c82855e KiUserExceptionDispatcher

backtrace[13] eip 0x00bd214e (no symbol)

backtrace[14] eip 0x00bd24c3 (no symbol)

backtrace[15] eip 0x00bd2d66 (no symbol)

backtrace[16] eip 0x00bd30d1 (no symbol)

backtrace[17] eip 0x00bd2085 (no symbol)

backtrace[18] eip 0x00bd24c3 (no symbol)

backtrace[19] eip 0x00bd45ae (no symbol)

backtrace[20] eip 0x00bd4b41 (no symbol)

backtrace[21] eip 0x00bb4c4f (no symbol)

backtrace[22] eip 0x00ba833a (no symbol)

backtrace[23] eip 0x008e56fe (no symbol)

backtrace[24] eip 0x008e5d10 (no symbol)

backtrace[25] eip 0x008e6261 (no symbol)

backtrace[26] eip 0x006e74cd (no symbol)

backtrace[27] eip 0x006ec43e (no symbol)

backtrace[28] eip 0x006f2294 (no symbol)

backtrace[29] eip 0x00a46eba (no symbol)

backtrace[30] eip 0x77e64829 GetModuleHandleA

backtrace[31] eip 0x013a7067 ?GetVersion@TypeImpl@Vmomi@@UAEPAVVersion@2@XZ

CoreDump: Writing minidump to C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs\vpxd-1948-1800.dmp

0 Kudos
2 Replies
dmgenesys
Contributor
Contributor

Just a short update in case somebody wonders - this issue was fixed by the express patch for U2 update. No more VC service crashes... Just gotta love this update - will be remembered for years to come Smiley Happy

0 Kudos
TimRG
Contributor
Contributor

I've recently upgraded from VC U2 to U3 successfully and all my hosts are either running 3.5U2 or U3 and I'm now having the same issue.

I have 5 rules in place but if I enable a specific two of them and then try to generate recommendations in the DRS tab of the cluster it crashes the VC. If I disable these two rules then VC doesn't crash and I get all the normal recommendations I get from the other three rules.

Recreating the rules appears to have no effect.

Anyone else having these problems?

0 Kudos