VMware Cloud Community
markajohnson
Contributor
Contributor

VCenter crash when using SDRS

[Note: I also posted this in vCenter -> vCenter Servers...]

Hi,

I'm trying to use the SDRS feature with vCenter and get a crash during the "applyStorageDrsRecommendation" task call.

We're using:

vCenter -- 5.0 Update 1a | 12 July 2012 | Build 755629
ESXi -- VMware ESXi 5.0.0 Update 1

I'm using the 5.1 version of the vSphere client API tools.

The call to "recommendDatastores" returns successfully and I get a couple of recomendations back.  I pass the key for the first recommendation to the "apply" task.

Thanks for any help.

Mark

Here's the crash information from the logs:

2012-10-08T14:53:40.057-05:00 [01980 verbose 'ProxySvc Req00647'] New
proxy client SSL(TCPStreamWin32(socket=TCP(fd=6076)
local=192.168.30.21:443,  peer=192.168.50.109:33812))
2012-10-08T14:53:40.135-05:00 [04168 verbose
'SoapAdapter.HTTPService'] User agent is 'JAX-WS RI 2.1.6 in JDK 6'
2012-10-08T14:53:40.135-05:00 [01980 verbose 'SoapAdapter']
Unrecognized version URI "urn:vim25/5.1"; using default handler for
"urn:vim25/5.0"
2012-10-08T14:53:40.135-05:00 [01672 verbose 'Default'] [VpxVmomi]
Invoking [applyRecommendation] on
[vim.StorageResourceManager:StorageResourceManager] session
[528ee927-8bc8-247b-9f8e-ac9c98ad5b4e(52ff00d7-0e6b-11e9-1ee1-614cbf803321)]
2012-10-08T14:54:56.213-05:00 [01672 info 'Default'] CoreDump: Writing minidump
2012-10-08T14:55:37.698-05:00 [01672 panic 'Default']
-->
--> Panic: Win32 exception: Access Violation (0xc0000005)
-->    Read (0) at address 0000000000000028
-->    rip: 00000000008e8315 rsp: 000000001513eeb0 rbp: 0000000020c51ff0
-->    rax: 0000000019f941b0 rbx: 0000000000000028 rcx: 0000000019f935f2
-->    rdx: 00000000000027c0 rdi: 0000000019f941b0 rsi: 000000001513eff0
-->    r8:  0000000000000000 r9:  0000000000000000 r10: 000000000274dfd0
-->    r11: 0000000019f935e0 r12: 00000000178e1e10 r13: 000000001ef540b0
-->    r14: 000000001bbb6090 r15: 000000001d468020
-->
--> Backtrace:
--> backtrace[00] rip 000000018013deba (no symbol)
--> backtrace[01] rip 0000000180101518 (no symbol)
--> backtrace[02] rip 0000000180101a5e (no symbol)
--> backtrace[03] rip 000000018015ee18 (no symbol)
--> backtrace[04] rip 000000018015ef87 (no symbol)
--> backtrace[05] rip 0000000180150536 (no symbol)
--> backtrace[06] rip 00000000747f5129 (no symbol)
--> backtrace[07] rip 00000000747f42d6 (no symbol)
--> backtrace[08] rip 00000000747f49de (no symbol)
--> backtrace[09] rip 00000000747f4c1d (no symbol)
--> backtrace[10] rip 00000000747f502b (no symbol)
--> backtrace[11] rip 0000000076e39d0d (no symbol)
--> backtrace[12] rip 0000000076e291af (no symbol)
--> backtrace[13] rip 0000000076e61278 (no symbol)
--> backtrace[14] rip 00000000008e8315 (no symbol)
--> backtrace[15] rip 00000001408fd1b4 (no symbol)
--> backtrace[16] rip 00000001408feee8 (no symbol)
--> backtrace[17] rip 000000014090dcbb (no symbol)
--> backtrace[18] rip 0000000140911158 (no symbol)
--> backtrace[19] rip 000000013ff3f4fc (no symbol)
--> backtrace[20] rip 0000000140877545 (no symbol)
--> backtrace[21] rip 00000001408772cb (no symbol)
--> backtrace[22] rip 0000000140877829 (no symbol)
--> backtrace[23] rip 00000000005242f1 (no symbol)
--> backtrace[24] rip 000000018015473d (no symbol)
--> backtrace[25] rip 0000000180155c64 (no symbol)
--> backtrace[26] rip 000000018014e575 (no symbol)
--> backtrace[27] rip 00000000747b2fdf (no symbol)
--> backtrace[28] rip 00000000747b3080 (no symbol)
--> backtrace[29] rip 0000000076c0652d (no symbol)
--> backtrace[30] rip 0000000076e3c521 (no symbol)
-->
2012-10-08T14:55:37.698-05:00 [01672 panic 'Default'] (Log recursion
level 2) Win32 exception: Access Violation (0xc0000005)
-->    Read (0) at address 0000000000000028
-->    rip: 00000000008e8315 rsp: 000000001513eeb0 rbp: 0000000020c51ff0
-->    rax: 0000000019f941b0 rbx: 0000000000000028 rcx: 0000000019f935f2
-->    rdx: 00000000000027c0 rdi: 0000000019f941b0 rsi: 000000001513eff0
-->    r8:  0000000000000000 r9:  0000000000000000 r10: 000000000274dfd0
-->    r11: 0000000019f935e0 r12: 00000000178e1e10 r13: 000000001ef540b0
-->    r14: 000000001bbb6090 r15: 000000001d468020
-->

0 Kudos
1 Reply
markajohnson
Contributor
Contributor

Found the problem - my storage spec type was set to CREATE and should have been CLONE.  I was passing in parameters for a clone operation and apparently this caused vCenter to crash.

0 Kudos