VMware Horizon Community
rahulgarg
VMware Employee
VMware Employee
‎07-03-2017 09:50 PM
Jump to solution

RDS Host running on Windows 2012 is crashing while establishing multiple connections

I am trying to connect to RDS host. So If I connect only through single user, I face no issue.

But if I try to establish multiple connection, within few seconds my host crashes. 

I have created this VM using view RDS farm and then added it to pool.

From the vmware.log, it shows following panic :

2017-07-03T11:58:07Z[+0.000]| vmx| W115: Caught signal 11 -- tid 1226630 (addr BFDB052F98)

2017-07-03T11:58:07Z[+0.000]| vmx| I125: SIGNAL: rip 0xbfd9e1544d rsp 0x35f6b0e1920 rbp 0x35f6b0e1930

2017-07-03T11:58:07Z[+0.000]| vmx| I125: SIGNAL: rax 0xbfdadd2fc0 rbx 0xbfdb052f98 rcx 0x0 rdx 0x4fffb rsi 0x1 rdi 0xbfdb052f98

2017-07-03T11:58:07Z[+0.000]| vmx| I125:         r8 0xbfda8b3231 r9 0x12b786 r10 0x0 r11 0x246 r12 0x1 r13 0x35f6b0e19dc r14 0xbfdc03a090 r15 0x35f6b0e19e0

2017-07-03T11:58:07Z[+0.000]| vmx| I125: SIGNAL: stack 35F6B0E1920 : 0x0000000000000000 0x000000bfdccef1b0

2017-07-03T11:58:07Z[+0.000]| vmx| I125: SIGNAL: stack 35F6B0E1930 : 0x0000035f6b0e19a0 0x000000bfd9f7d91d

2017-07-03T11:58:07Z[+0.000]| vmx| I125: SIGNAL: stack 35F6B0E1940 : 0x000000bfdc3ccc00 0x000000bfdb307df8

2017-07-03T11:58:07Z[+0.000]| vmx| I125: SIGNAL: stack 35F6B0E1950 : 0x000000bfdb6ae560 0x0000000000000000

2017-07-03T11:58:07Z[+0.000]| vmx| I125: SIGNAL: stack 35F6B0E1960 : 0x000000c01d439010 0x000000bfda1efccb

2017-07-03T11:58:07Z[+0.000]| vmx| I125: SIGNAL: stack 35F6B0E1970 : 0x000000c01d439010 0x000000c01d439010

2017-07-03T11:58:07Z[+0.000]| vmx| I125: SIGNAL: stack 35F6B0E1980 : 0x000000bfdccef1b0 0x0000035f6b0e19dc

2017-07-03T11:58:07Z[+0.000]| vmx| I125: SIGNAL: stack 35F6B0E1990 : 0x0000000000000000 0x0000035f6b0e19e0

2017-07-03T11:58:07Z[+0.000]| vmx| I125: Backtrace:

2017-07-03T11:58:07Z[+0.000]| vmx| I125: Backtrace[0] 0000035f6b0e13a0 rip=000000bfda23d047 rbx=000000bfda23cb40 rbp=0000035f6b0e13c0 r12=0000000000000000 r13=000000bfdaec2801 r14=000000

2017-07-03T11:58:07Z[+0.000]| vmx| I125: Backtrace[1] 0000035f6b0e13d0 rip=000000bfda46cb00 rbx=0000035f6b0e19a0 rbp=0000035f6b0e15e0 r12=000000000000000b r13=000000bfdaec2801 r14=000000

2017-07-03T11:58:07Z[+0.000]| vmx| I125: Backtrace[2] 0000035f6b0e15f0 rip=000000bfda46cf04 rbx=0000000000000000 rbp=0000035f6b0e1640 r12=000000c01d437378 r13=000000bfdaec2868 r14=000000

2017-07-03T11:58:07Z[+0.000]| vmx| I125: Backtrace[3] 0000035f6b0e1650 rip=000000000022e00f rbx=000000bfdb052f98 rbp=0000035f6b0e1890 r12=0000035f6b0e16d0 r13=0000035f6b0e19dc r14=000000

2017-07-03T11:58:07Z[+0.000]| vmx| I125: SymBacktrace[0] 0000035f6b0e13a0 rip=000000bfda23d047 in function (null) in object /bin/vmx loaded at 000000bfd9bc3000

2017-07-03T11:58:07Z[+0.000]| vmx| I125: SymBacktrace[1] 0000035f6b0e13d0 rip=000000bfda46cb00 in function (null) in object /bin/vmx loaded at 000000bfd9bc3000

2017-07-03T11:58:07Z[+0.000]| vmx| I125: SymBacktrace[2] 0000035f6b0e15f0 rip=000000bfda46cf04 in function (null) in object /bin/vmx loaded at 000000bfd9bc3000

2017-07-03T11:58:07Z[+0.000]| vmx| I125: SymBacktrace[3] 0000035f6b0e1650 rip=000000000022e00f

2017-07-03T11:58:07Z[+0.000]| vmx| E105: PANIC: Unexpected signal: 11.

2017-07-03T11:58:07Z[+19.399]| vmx| W115: A core file is available in "/vmfs/volumes/vsan:527041e89038204c-24815a7b4db16197/daf15959-edbe-397e-a4b7-0cc47a5971be/vmx-zdump.002"

2017-07-03T11:58:26.841Z| mks| W115: Panic in progress... ungrabbing

Any pointers, what could be the problem ?

1 Solution

Accepted Solutions
bluefirestorm
Champion
Champion
‎07-03-2017 10:49 PM
Jump to solution

The signal 11 just means it is a memory segment fault. The cause of the memory segment fault is another matter.

Before the signal 11 in the vmware.log do you see any lines similar to these

vcpu-0| I125: GuestMsg: Too many channels opened.

vmx| I125: GuestRpc: Too many RPCI vsocket channels opened

If yes, you may want to look at this KB for the possible workaround

https://kb.vmware.com/kb/2149642

View solution in original post

2 Replies
bluefirestorm
Champion
Champion
‎07-03-2017 10:49 PM
Jump to solution

The signal 11 just means it is a memory segment fault. The cause of the memory segment fault is another matter.

Before the signal 11 in the vmware.log do you see any lines similar to these

vcpu-0| I125: GuestMsg: Too many channels opened.

vmx| I125: GuestRpc: Too many RPCI vsocket channels opened

If yes, you may want to look at this KB for the possible workaround

https://kb.vmware.com/kb/2149642

rahulgarg
VMware Employee
VMware Employee
‎07-03-2017 11:13 PM
Jump to solution

Thanks for the solution, it worked like a charm.

0 Kudos