urahara
Contributor
Contributor

VM of Esxi 6 crash after too many TSE connexion

Jump to solution

Hi all,

I don't know what to do to resolve this problem, I'm totally stuck.

When too many users log on at the same time (within the same 2 min) with terminal sessions the VM crash.

I'm using a custom version of Esxi 6 provided by HP (found on vmware website) on a HP server.

I updated all the firmware and disabled logging of the VM (found on a KB here : link )

Someone have any idea to resolve this problem?

Regards

Here the logfile I have :

2015-07-06T15:31:11.845Z| vcpu-6| I120: GuestMsg: channel 1: wrong cookie, discarding message.

2015-07-06T15:31:24.565Z| vcpu-1| I120: GuestRpc: Reinitializing Channel 3(toolbox-dnd)

2015-07-06T15:31:39.845Z| vcpu-0| I120: GuestMsg: channel 6: wrong cookie, discarding message.

2015-07-06T15:31:39.845Z| vcpu-0| I120: GuestMsg: channel 6: wrong cookie, discarding message.

2015-07-07T05:52:56.954Z| vmx| I120: Guest: toolbox-dnd: Version: build-2476743

2015-07-07T05:52:56.954Z| vcpu-0| I120: GuestRpc: Channel 1, guest application toolbox-dnd.

2015-07-07T05:53:01.006Z| vmx| I120: Guest: toolbox-dnd: Version: build-2476743

2015-07-07T05:53:04.303Z| vmx| I120: GuestRpc: Got error for connection 1507:Remote connection failure

2015-07-07T05:53:34.047Z| vcpu-7| I120: GuestRpc: Channel conflict: guest application toolbox-dnd tried to register, but it is still registered on channel 1

2015-07-07T06:19:08.765Z| vmx| I120: Guest: toolbox-dnd: Version: build-2476743

2015-07-07T06:19:14.681Z| vmx| I120: Guest: toolbox-dnd: Version: build-2476743

2015-07-07T06:39:00.978Z| vmx| I120: Guest: toolbox-dnd: Version: build-2476743

2015-07-07T06:39:04.316Z| vmx| I120: Guest: toolbox-dnd: Version: build-2476743

2015-07-07T06:45:03.375Z| vcpu-3| I120: GuestMsg: Too many channels opened.

2015-07-07T06:45:03.375Z| vcpu-3| I120: GuestMsg: Too many channels opened.

2015-07-07T06:53:23.052Z| vcpu-6| I120: GuestMsg: Too many channels opened.

2015-07-07T06:53:23.052Z| vcpu-6| I120: GuestMsg: Too many channels opened.

2015-07-07T06:59:28.682Z| vcpu-0| I120: GuestRpc: Channel conflict: guest application toolbox-dnd tried to register, but it is still registered on channel 1

2015-07-07T07:25:08.953Z| vmx| I120: Guest: toolbox-dnd: Version: build-2476743

2015-07-07T07:25:09.954Z| vmx| I120: GuestRpc: Got error for connection 1607:Remote connection failure

2015-07-07T07:25:12.160Z| vmx| I120: Guest: toolbox-dnd: Version: build-2476743

2015-07-07T07:25:15.848Z| vcpu-3| I120: GuestMsg: Too many channels opened.

2015-07-07T07:25:15.849Z| vcpu-3| I120: GuestMsg: Too many channels opened.

2015-07-07T07:25:15.973Z| vcpu-3| I120: GuestMsg: Too many channels opened.

2015-07-07T07:25:15.974Z| vcpu-3| I120: GuestMsg: Too many channels opened.

2015-07-07T07:25:16.129Z| vcpu-6| I120: GuestMsg: Too many channels opened.

2015-07-07T07:25:16.130Z| vcpu-6| I120: GuestMsg: Too many channels opened.

2015-07-07T07:25:16.169Z| vcpu-0| I120: GuestMsg: Too many channels opened.

2015-07-07T07:25:16.170Z| vcpu-0| I120: GuestMsg: Too many channels opened.

2015-07-07T07:25:16.393Z| vcpu-2| I120: GuestMsg: Too many channels opened.

2015-07-07T07:25:16.393Z| vcpu-2| I120: GuestMsg: Too many channels opened.

2015-07-07T08:33:19.984Z| vcpu-7| I120: GuestMsg: Too many channels opened.

2015-07-07T08:33:19.984Z| vcpu-7| I120: GuestMsg: Too many channels opened.

2015-07-07T08:34:20.081Z| vcpu-2| I120: GuestMsg: Too many channels opened.

2015-07-07T08:34:20.082Z| vcpu-2| I120: GuestMsg: Too many channels opened.

2015-07-07T08:42:03.240Z| vmx| I120: Guest: toolbox-dnd: Version: build-2476743

2015-07-07T08:42:04.561Z| vcpu-5| I120: GuestMsg: channel 4: wrong cookie, discarding message.

2015-07-07T08:42:04.561Z| vcpu-5| I120: GuestMsg: channel 4: wrong cookie, discarding message.

2015-07-07T08:42:09.559Z| vcpu-7| I120: GuestMsg: channel 7: wrong cookie, discarding message.

2015-07-07T08:42:09.559Z| vcpu-7| I120: GuestMsg: channel 7: wrong cookie, discarding message.

2015-07-07T08:42:12.560Z| vcpu-1| I120: GuestMsg: channel 6: wrong cookie, discarding message.

2015-07-07T08:42:12.560Z| vcpu-1| I120: GuestMsg: channel 6: wrong cookie, discarding message.

2015-07-07T08:42:13.260Z| vcpu-2| I120: GuestMsg: Too many channels opened.

2015-07-07T08:42:13.260Z| vcpu-2| I120: GuestMsg: Too many channels opened.

2015-07-07T08:42:15.561Z| vcpu-4| I120: GuestMsg: channel 3: wrong cookie, discarding message.

2015-07-07T08:42:15.561Z| vcpu-4| I120: GuestMsg: channel 3: wrong cookie, discarding message.

2015-07-07T08:42:15.561Z| vcpu-4| I120: GuestMsg: Too many channels opened.

2015-07-07T08:42:15.561Z| vcpu-4| I120: GuestMsg: Too many channels opened.

2015-07-07T10:45:26.448Z| vcpu-3| I120: GuestMsg: Too many channels opened.

2015-07-07T10:45:26.448Z| vcpu-3| I120: GuestMsg: Too many channels opened.

2015-07-07T10:45:28.610Z| vcpu-7| I120: GuestMsg: Too many channels opened.

2015-07-07T10:45:28.610Z| vcpu-7| I120: GuestMsg: Too many channels opened.

2015-07-07T10:58:45.472Z| vmx| I120: Guest: toolbox-dnd: Version: build-2476743

2015-07-07T10:58:51.159Z| vmx| I120: GuestRpc: Too many RPCI vsocket channels opened.

2015-07-07T10:58:51Z[+0.000]| vmx| W110: Caught signal 11 -- tid 38383 (addr 31F2DD50)

2015-07-07T10:58:51Z[+0.000]| vmx| I120: SIGNAL: rip 0x30c221f1 rsp 0x3ffceb4f970 rbp 0x3ffceb4f9a0

2015-07-07T10:58:51Z[+0.000]| vmx| I120: SIGNAL: rax 0x31cadd70 rbx 0x32685590 rcx 0x1 rdx 0x4fffb rsi 0x0 rdi 0x3209e130

2015-07-07T10:58:51Z[+0.000]| vmx| I120:         r8 0x3ffceb4f711 r9 0x204943505220796e r10 0x2074656b636f7376 r11 0x0 r12 0xffff r13 0xffff r14 0x1 r15 0x3ffceb4fa3c

2015-07-07T10:58:51Z[+0.000]| vmx| I120: SIGNAL: stack 3FFCEB4F970 : 0x0000000000000000 0x00000000326dc4c0

2015-07-07T10:58:51Z[+0.000]| vmx| I120: SIGNAL: stack 3FFCEB4F980 : 0x00000000326dc638 0x00000000326dc4c0

2015-07-07T10:58:51Z[+0.000]| vmx| I120: SIGNAL: stack 3FFCEB4F990 : 0x00000000326dc638 0x0000000032475e00

2015-07-07T10:58:51Z[+0.000]| vmx| I120: SIGNAL: stack 3FFCEB4F9A0 : 0x000003ffceb4f9f0 0x0000000030d74bd9

2015-07-07T10:58:51Z[+0.000]| vmx| I120: SIGNAL: stack 3FFCEB4F9B0 : 0x000003f700000000 0x00000000a64294ae

2015-07-07T10:58:51Z[+0.000]| vmx| I120: SIGNAL: stack 3FFCEB4F9C0 : 0x00000000325f7e00 0x000000003235ccf0

2015-07-07T10:58:51Z[+0.000]| vmx| I120: SIGNAL: stack 3FFCEB4F9D0 : 0x000003ffceb4f9f0 0x000003ffced7f010

2015-07-07T10:58:51Z[+0.000]| vmx| I120: SIGNAL: stack 3FFCEB4F9E0 : 0x0000000000000000 0x00000000322fcbf0

2015-07-07T10:58:51Z[+0.000]| vmx| I120: Backtrace:

2015-07-07T10:58:51Z[+0.000]| vmx| I120: Backtrace[0] 000003ffceb4f490 rip=00000000310c904e rbx=00000000310c8b30 rbp=000003ffceb4f4b0 r12=0000000000000000 r13=000003ffceb548c0 r14=000003ffceb4f9f0 r15=000000000000000b

2015-07-07T10:58:51Z[+0.000]| vmx| I120: Backtrace[1] 000003ffceb4f4c0 rip=00000000311337bc rbx=000000000000000b rbp=000003ffceb4f690 r12=0000000000000000 r13=000003ffceb548c0 r14=000003ffceb4f9f0 r15=000000000000000b

2015-07-07T10:58:51Z[+0.000]| vmx| I120: Backtrace[2] 000003ffceb4f6a0 rip=000000000020700f rbx=0000000032685590 rbp=000003ffceb4f8e0 r12=000003ffceb4f720 r13=000000000000ffff r14=0000000000000001 r15=000003ffceb4fa3c

2015-07-07T10:58:51Z[+0.000]| vmx| I120: SymBacktrace[0] 000003ffceb4f490 rip=00000000310c904e in function (null) in object /bin/vmx loaded at 00000000309d9000

2015-07-07T10:58:51Z[+0.000]| vmx| I120: SymBacktrace[1] 000003ffceb4f4c0 rip=00000000311337bc in function (null) in object /bin/vmx loaded at 00000000309d9000

2015-07-07T10:58:51Z[+0.000]| vmx| I120: SymBacktrace[2] 000003ffceb4f6a0 rip=000000000020700f

2015-07-07T10:58:51Z[+0.000]| vmx| I120: Unexpected signal: 11.

2015-07-07T10:58:51Z[+110.342]| vmx| W110: A core file is available in "/vmfs/volumes/53dc319c-b50abf59-ed6b-9c8e99671274/SERVEUR2008/vmx-zdump.003"

2015-07-07T10:58:51Z[+110.342]| vmx| W110: Writing monitor corefile "/vmfs/volumes/53dc319c-b50abf59-ed6b-9c8e99671274/SERVEUR2008/vmmcores.gz"

2015-07-07T10:58:51Z[+110.535]| vmx| W110: Dumping core for vcpu-0

2015-07-07T10:58:51Z[+110.535]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-07-07T10:58:51Z[+110.535]| vmx| I120: VMK Stack for vcpu 0 is at 0x43916f813000

2015-07-07T10:58:51Z[+110.535]| vmx| I120: Beginning monitor coredump

2015-07-07T10:58:51Z[+111.197]| vmx| I120: End monitor coredump

2015-07-07T10:58:51Z[+111.197]| vmx| W110: Dumping core for vcpu-1

2015-07-07T10:58:51Z[+111.197]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-07-07T10:58:51Z[+111.198]| vmx| I120: VMK Stack for vcpu 1 is at 0x43916f913000

2015-07-07T10:58:51Z[+111.198]| vmx| I120: Beginning monitor coredump

2015-07-07T10:58:51Z[+111.823]| vmx| I120: End monitor coredump

2015-07-07T10:58:51Z[+111.824]| vmx| W110: Dumping core for vcpu-2

2015-07-07T10:58:51Z[+111.824]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-07-07T10:58:51Z[+111.824]| vmx| I120: VMK Stack for vcpu 2 is at 0x43916f993000

2015-07-07T10:58:51Z[+111.824]| vmx| I120: Beginning monitor coredump

2015-07-07T10:58:51Z[+112.450]| vmx| I120: End monitor coredump

2015-07-07T10:58:51Z[+112.451]| vmx| W110: Dumping core for vcpu-3

2015-07-07T10:58:51Z[+112.451]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-07-07T10:58:51Z[+112.451]| vmx| I120: VMK Stack for vcpu 3 is at 0x43916fa13000

2015-07-07T10:58:51Z[+112.451]| vmx| I120: Beginning monitor coredump

2015-07-07T10:58:51Z[+113.077]| vmx| I120: End monitor coredump

2015-07-07T10:58:51Z[+113.078]| vmx| W110: Dumping core for vcpu-4

2015-07-07T10:58:51Z[+113.078]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-07-07T10:58:51Z[+113.078]| vmx| I120: VMK Stack for vcpu 4 is at 0x43916fa93000

2015-07-07T10:58:51Z[+113.078]| vmx| I120: Beginning monitor coredump

2015-07-07T10:58:51Z[+113.705]| vmx| I120: End monitor coredump

2015-07-07T10:58:51Z[+113.706]| vmx| W110: Dumping core for vcpu-5

2015-07-07T10:58:51Z[+113.706]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-07-07T10:58:51Z[+113.706]| vmx| I120: VMK Stack for vcpu 5 is at 0x43916fb13000

2015-07-07T10:58:51Z[+113.706]| vmx| I120: Beginning monitor coredump

2015-07-07T10:58:51Z[+114.335]| vmx| I120: End monitor coredump

2015-07-07T10:58:51Z[+114.336]| vmx| W110: Dumping core for vcpu-6

2015-07-07T10:58:51Z[+114.336]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-07-07T10:58:51Z[+114.336]| vmx| I120: VMK Stack for vcpu 6 is at 0x43916fb93000

2015-07-07T10:58:51Z[+114.336]| vmx| I120: Beginning monitor coredump

2015-07-07T10:58:51Z[+114.963]| vmx| I120: End monitor coredump

2015-07-07T10:58:51Z[+114.964]| vmx| W110: Dumping core for vcpu-7

2015-07-07T10:58:51Z[+114.964]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-07-07T10:58:51Z[+114.964]| vmx| I120: VMK Stack for vcpu 7 is at 0x43916fc13000

2015-07-07T10:58:51Z[+114.964]| vmx| I120: Beginning monitor coredump

2015-07-07T10:58:51Z[+115.593]| vmx| I120: End monitor coredump

2015-07-07T10:58:51Z[+123.317]| vmx| I120: Backtrace:

2015-07-07T10:58:51Z[+123.317]| vmx| I120: Backtrace[0] 000003ffceb4ef90 rip=00000000310c904e rbx=00000000310c8b30 rbp=000003ffceb4efb0 r12=0000000000000000 r13=000003ffceb548c0 r14=000003ffceb4f9f0 r15=000000000000000b

2015-07-07T10:58:51Z[+123.317]| vmx| I120: Backtrace[1] 000003ffceb4efc0 rip=0000000030b768ba rbx=0000000031d7e648 rbp=000003ffceb4f4b0 r12=0000000000000001 r13=000003ffceb548c0 r14=000003ffceb4f9f0 r15=000000000000000b

2015-07-07T10:58:51Z[+123.317]| vmx| I120: Backtrace[2] 000003ffceb4f4c0 rip=0000000031133816 rbx=000000000000000b rbp=000003ffceb4f690 r12=0000000000000000 r13=000003ffceb548c0 r14=000003ffceb4f9f0 r15=000000000000000b

2015-07-07T10:58:51Z[+123.317]| vmx| I120: Backtrace[3] 000003ffceb4f6a0 rip=000000000020700f rbx=0000000032685590 rbp=000003ffceb4f8e0 r12=000003ffceb4f720 r13=000000000000ffff r14=0000000000000001 r15=000003ffceb4fa3c

2015-07-07T10:58:51Z[+123.317]| vmx| I120: SymBacktrace[0] 000003ffceb4ef90 rip=00000000310c904e in function (null) in object /bin/vmx loaded at 00000000309d9000

2015-07-07T10:58:51Z[+123.317]| vmx| I120: SymBacktrace[1] 000003ffceb4efc0 rip=0000000030b768ba in function (null) in object /bin/vmx loaded at 00000000309d9000

2015-07-07T10:58:51Z[+123.317]| vmx| I120: SymBacktrace[2] 000003ffceb4f4c0 rip=0000000031133816 in function (null) in object /bin/vmx loaded at 00000000309d9000

2015-07-07T10:58:51Z[+123.317]| vmx| I120: SymBacktrace[3] 000003ffceb4f6a0 rip=000000000020700f

2015-07-07T10:58:51Z[+123.317]| vmx| I120: Msg_Post: Error

2015-07-07T10:58:51Z[+123.317]| vmx| I120: [msg.log.error.unrecoverable] VMware ESX unrecoverable error: (vmx)

2015-07-07T10:58:51Z[+123.317]| vmx| I120+ Unexpected signal: 11.

2015-07-07T10:58:51Z[+123.317]| vmx| I120: [msg.panic.haveLog] A log file is available in "/vmfs/volumes/53dc319c-b50abf59-ed6b-9c8e99671274/SERVEUR2008/vmware.log". 

2015-07-07T10:58:51Z[+123.317]| vmx| I120: [msg.panic.requestSupport.withoutLog] You can request support. 

2015-07-07T10:58:51Z[+123.317]| vmx| I120: [msg.panic.requestSupport.vmSupport.vmx86]

2015-07-07T10:58:51Z[+123.317]| vmx| I120+ To collect data to submit to VMware technical support, run "vm-support".

2015-07-07T10:58:51Z[+123.317]| vmx| I120: [msg.panic.response] We will respond on the basis of your support entitlement.

2015-07-07T10:58:51Z[+123.317]| vmx| I120: ----------------------------------------

2015-07-07T10:58:51Z[+123.320]| vmx| I120: Vigor_MessageRevoke: message 'msg.panic.response' (seq 43987) is revoked

2015-07-07T10:58:51Z[+123.320]| vmx| I120: Exiting

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
DanielOprea
Hot Shot
Hot Shot

Hi,

Your problem is the S.O. in the guest, and not in the vm. Look and aplly this KB: How to troubleshoot “The Terminal Server security layer detected an error in the protocol stream and...

For solution to the event "Couldn't restart RpcOut channel; bad things may happen until the RPC channel is reset." you must folowing this steps:

- save config TCP/IP from network adapters

- uninstall the vmware tools

- delete the vNICs

- reboot

- add the vNIC VMXNET3 again

- install again the vmware tools (the last version available)

- reboot

-Look in the S.O. for the old vnic with this commands:

set devmgr_show_nonpresent_devices=1

start devmgmt.msc

Click Show hidden devices on the View menu in Device Manager before you can see devices that are not connected to the computer and delete/uninstall the OLD vNIC.

-reboot the vm again

- Finaly config the TCP/IP in the vNICs

And when you've finished the entire procedure, performed again test TS connectivity with multiple users.

Regards

Daniel

PLEASE CONSIDER AWARDING any HELPFUL or CORRECT answer. Thanks!! Por favor CONSIDERA PREMIAR cualquier respuesta ÚTIL o CORRECTA. ¡¡Muchas gracias!! Blogs: http://danieloprea.blogspot.com.es/ https://communities.vmware.com/blogs/doprea

View solution in original post

0 Kudos
15 Replies
DanielOprea
Hot Shot
Hot Shot

hello
Which version of S.O. is the guest?

Ts sessions only be done through Windows RDP client?

PLEASE CONSIDER AWARDING any HELPFUL or CORRECT answer. Thanks!! Por favor CONSIDERA PREMIAR cualquier respuesta ÚTIL o CORRECTA. ¡¡Muchas gracias!! Blogs: http://danieloprea.blogspot.com.es/ https://communities.vmware.com/blogs/doprea
0 Kudos
paudieo
VMware Employee
VMware Employee

You've a virtual machine monitor panic, as per log line

2015-07-07T10:58:51Z[+123.317]| vmx| I120: Msg_Post: Error

2015-07-07T10:58:51Z[+123.317]| vmx| I120: [msg.log.error.unrecoverable] VMware ESX unrecoverable error: (vmx)

2015-07-07T10:58:51Z[+123.317]| vmx| I120+ Unexpected signal: 11.

2015-07-07T10:58:51Z[+123.317]| vmx| I120: [msg.panic.haveLog] A log file is available in "/vmfs/volumes/53dc319c-b50abf59-ed6b-9c8e99671274/SERVEUR2008/vmware.log".

2015-07-07T10:58:51Z[+123.317]| vmx| I120: [msg.panic.requestSupport.withoutLog] You can request support.

which I guess means the VM restarted after a crash

I would immediately file an SR to get the monitor core analysed

0 Kudos
urahara
Contributor
Contributor

The guest is a Windows Server 2008.

The TS sessions are done by Windows RDP and Wyse.

0 Kudos
urahara
Contributor
Contributor

What do you mean by "I would immediately file an SR to get the monitor core analysed" ??

The VM doesn't restart, I need to start it manually. It only happen when too many users log on at the same times (they are all in TS session).

I saw that the CPU sometimes reaches near 100% during log on phases, do you think the problem is here? (I saw the VM crashed without 100% CPU charge)

The VM is converted from an original OS on a previous server, with 2* 4 cores processor in the old and new one.

0 Kudos
cykVM
Expert
Expert

He meant to contact VMWare support and open a service request (SR)/ticket and VMWare support should analyze the crash dump.

Did you check Windows event logs on that Terminal Server VM? Maybe any errors or warnings are thrown there right before the VM crashes.

Dos the VM show a blue screen on console after the crash? If it does the STOP error might help.

Which vNIC type is attached to the VM (E1000e, VMXNET 3 or ...)? Maybe switching that helps to resolve the problem.

Generally it's not recommended to P2V Windows servers with "special" services (like AD, terminal services etc.). You may face several issues.

0 Kudos
DanielOprea
Hot Shot
Hot Shot

Hi,

Please check this KB: https://support.microsoft.com/en-us/kb/2477176#/en-us/kb/2477176

Regards

Daniel

PLEASE CONSIDER AWARDING any HELPFUL or CORRECT answer. Thanks!! Por favor CONSIDERA PREMIAR cualquier respuesta ÚTIL o CORRECTA. ¡¡Muchas gracias!! Blogs: http://danieloprea.blogspot.com.es/ https://communities.vmware.com/blogs/doprea
0 Kudos
urahara
Contributor
Contributor

I have a TermDD id:56 error : The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.

And this Wmware Tools warning id:1000 : [ warning] [vmusr:vmusr] Couldn't restart RpcOut channel; bad things may happen until the RPC channel is reset.

But not right before the crash.

No blue screen at all, the VM just instantly shut down and need to be restarted manually.

The vNIC attached is a vmxnet 3, I need to change it ?

I checked the Microsoft KB too, and looked into the TS manager.

I have 5 active temporary licenses affected, is it a problem?

Unlimited connexions are authorized.

Last question, you think I can request a support ticket from vmware with an ESXI? Do you have a link for submit a ticket?

Regards

0 Kudos
cykVM
Expert
Expert

Last question, you think I can request a support ticket from vmware with an ESXI? Do you have a link for submit a ticket?

Are you running free license on ESXi? In that case you won't get any support, especially no free support.

Maybe it's even a Microsoft licensing issue. Is the underlying Windows still activated after it was converted (P2V)?

Are enough terminal server/RDS CALs entered?

Is there any anti-virus application running in ther terminal environment? This might also produce issues.

The hard shutdown/power off is at least very starnge.

0 Kudos
paudieo
VMware Employee
VMware Employee

>What do you mean by "I would immediately file an SR to get the monitor core analysed" ??

the Virtual machine crashed.

it generated a core dump

see log:

2015-07-07T10:58:51Z[+112.451]| vmx| I120: Beginning monitor coredump

2015-07-07T10:58:51Z[+113.077]| vmx| I120: End monitor coredump

2015-07-07T10:58:51Z[+113.078]| vmx| W110: Dumping core for vcpu-4

2015-07-07T10:58:51Z[+113.078]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-07-07T10:58:51Z[+113.078]| vmx| I120: VMK Stack for vcpu 4 is at 0x43916fa93000

2015-07-07T10:58:51Z[+113.078]| vmx| I120: Beginning monitor coredump

2015-07-07T10:58:51Z[+113.705]| vmx| I120: End monitor coredump

2015-07-07T10:58:51Z[+113.706]| vmx| W110: Dumping core for vcpu-5

2015-07-07T10:58:51Z[+113.706]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-07-07T10:58:51Z[+113.706]| vmx| I120: VMK Stack for vcpu 5 is at 0x43916fb13000

2015-07-07T10:58:51Z[+113.706]| vmx| I120: Beginning monitor coredump

2015-07-07T10:58:51Z[+114.335]| vmx| I120: End monitor coredump

2015-07-07T10:58:51Z[+114.336]| vmx| W110: Dumping core for vcpu-6

2015-07-07T10:58:51Z[+114.336]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-07-07T10:58:51Z[+114.336]| vmx| I120: VMK Stack for vcpu 6 is at 0x43916fb93000

2015-07-07T10:58:51Z[+114.336]| vmx| I120: Beginning monitor coredump

2015-07-07T10:58:51Z[+114.963]| vmx| I120: End monitor coredump

2015-07-07T10:58:51Z[+114.964]| vmx| W110: Dumping core for vcpu-7

2015-07-07T10:58:51Z[+114.964]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-07-07T10:58:51Z[+114.964]| vmx| I120: VMK Stack for vcpu 7 is at 0x43916fc13000

2015-07-07T10:58:51Z[+114.964]| vmx| I120: Beginning monitor coredump

2015-07-07T10:58:51Z[+115.593]| vmx| I120: End monitor coredump

So there is more than likely a zdump file on the folder of the VMFS volume where the VM is stored

Filing a support  service request with VMware Global Support Services will help investigate the virtail machine backtrace

I also noted you said "The VM is converted from an original OS on a previous server, with 2* 4 cores processor"

I advise build a clean new OS and retest to see if 3rd party s/w within the VM has a factor , this is merely a troubleshooting step to determine the root cause and narrow the problem down

0 Kudos
DanielOprea
Hot Shot
Hot Shot

Hi,

Your problem is the S.O. in the guest, and not in the vm. Look and aplly this KB: How to troubleshoot “The Terminal Server security layer detected an error in the protocol stream and...

For solution to the event "Couldn't restart RpcOut channel; bad things may happen until the RPC channel is reset." you must folowing this steps:

- save config TCP/IP from network adapters

- uninstall the vmware tools

- delete the vNICs

- reboot

- add the vNIC VMXNET3 again

- install again the vmware tools (the last version available)

- reboot

-Look in the S.O. for the old vnic with this commands:

set devmgr_show_nonpresent_devices=1

start devmgmt.msc

Click Show hidden devices on the View menu in Device Manager before you can see devices that are not connected to the computer and delete/uninstall the OLD vNIC.

-reboot the vm again

- Finaly config the TCP/IP in the vNICs

And when you've finished the entire procedure, performed again test TS connectivity with multiple users.

Regards

Daniel

PLEASE CONSIDER AWARDING any HELPFUL or CORRECT answer. Thanks!! Por favor CONSIDERA PREMIAR cualquier respuesta ÚTIL o CORRECTA. ¡¡Muchas gracias!! Blogs: http://danieloprea.blogspot.com.es/ https://communities.vmware.com/blogs/doprea

View solution in original post

0 Kudos
urahara
Contributor
Contributor

Thanks for all your answers, I will test it very soon and come back to you with my results.

0 Kudos
urahara
Contributor
Contributor

I disabled rss + chminey + NetDMA.

I deleted all Nic + vmware tool, stopped the VM, deleted and reinstalled a Nic on the VM, booted and reinstalled VMware tools + reconfig of the Nic.

I tried with 8 logons at the same time and it was good, but to be 100% ok I need to wait next week with all peoples.

I let you know.

0 Kudos
DanielOprea
Hot Shot
Hot Shot

OK perfect! I await your news!

PLEASE CONSIDER AWARDING any HELPFUL or CORRECT answer. Thanks!! Por favor CONSIDERA PREMIAR cualquier respuesta ÚTIL o CORRECTA. ¡¡Muchas gracias!! Blogs: http://danieloprea.blogspot.com.es/ https://communities.vmware.com/blogs/doprea
0 Kudos
urahara
Contributor
Contributor

The solution of DanielOprea seems to work well (since one week).

Thanks all for your time.

Best regards

Adrien

0 Kudos
DanielOprea
Hot Shot
Hot Shot

Hi,

I'm glad you've solved the problem.

Regards

Daniel

PLEASE CONSIDER AWARDING any HELPFUL or CORRECT answer. Thanks!! Por favor CONSIDERA PREMIAR cualquier respuesta ÚTIL o CORRECTA. ¡¡Muchas gracias!! Blogs: http://danieloprea.blogspot.com.es/ https://communities.vmware.com/blogs/doprea
0 Kudos