4 Replies Latest reply on May 9, 2017 6:34 AM by CharlesToro

    VM running on VMWARE host 6.5 has crashed and analyzing vmx-zdump.00 file

    CharlesToro Novice

      Hi,

      One of my vms running on vmware host 6.5 has crashed this morning. It has created a vmx-zdump.000 file I need some guidance to analyze this file . I am using VMWare essential licenses.

      File is attached.

       

      Thanks

      Charles Nana

        • 1. Re: VM running on VMWARE host 6.5 has crashed and analyzing vmx-zdump.00 file
          dariusd Virtuoso
          VMware EmployeesUser Moderators

          It would be much easier to analyze starting with the vmware.log file and a description of what the VM was running/doing at the time of the crash.  Any chance you could take any vmware.log (and vmware-1.log, etc.) from the VM's folder and attach those to a reply here too?

           

          Thanks,

          --

          Darius

          • 2. Re: VM running on VMWARE host 6.5 has crashed and analyzing vmx-zdump.00 file
            CharlesToro Novice

            Hi dariusd,

            Thanks for responding and direct me to the correct direction.

            I copied the 3 log files to my desktop and open them I could see following portion in vmware-2.log file. How to interpret this ? I am attaching all 3 log files downloaded from the vm's folder.

             

             

             

            loaded at 0000004a963d7000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[3] 0000004add487720 rip=0000004a96a03ee8 in function (null) in object /bin/vmx loaded at 0000004a963d7000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[4] 0000004add487750 rip=0000004a96eb9969 in function (null) in object /bin/vmx loaded at 0000004a963d7000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[5] 0000004add487770 rip=0000004a967ba768 in function (null) in object /bin/vmx loaded at 0000004a963d7000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[6] 0000004add487790 rip=0000004a967b96cc in function (null) in object /bin/vmx loaded at 0000004a963d7000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[7] 0000004add4877e0 rip=0000004a967bdb9b in function (null) in object /bin/vmx loaded at 0000004a963d7000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[8] 0000004add487820 rip=0000004a967bd1bb in function (null) in object /bin/vmx loaded at 0000004a963d7000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[9] 0000004add4878e0 rip=0000004a967bda97 in function (null) in object /bin/vmx loaded at 0000004a963d7000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[10] 0000004add487940 rip=0000004a966a92f2 in function (null) in object /bin/vmx loaded at 0000004a963d7000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[11] 0000004add487960 rip=0000004a966ac702 in function (null) in object /bin/vmx loaded at 0000004a963d7000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[12] 0000004add4879b0 rip=0000004a966abd22 in function (null) in object /bin/vmx loaded at 0000004a963d7000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[13] 0000004add487a40 rip=0000004a9699f301 in function (null) in object /bin/vmx loaded at 0000004a963d7000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[14] 0000004add487a80 rip=0000004a969c6b56 in function (null) in object /bin/vmx loaded at 0000004a963d7000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[15] 0000004add487ad0 rip=0000004a9699f3e8 in function (null) in object /bin/vmx loaded at 0000004a963d7000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[16] 0000004add487af0 rip=0000004a96a3c225 in function (null) in object /bin/vmx loaded at 0000004a963d7000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[17] 0000004add487c50 rip=0000004ad7a8eddc in function (null) in object /lib64/libpthread.so.0 loaded at 0000004ad7a87000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[18] 0000004add487d60 rip=0000004ad959600d in function clone in object /lib64/libc.so.6 loaded at 0000004ad94c4000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: SymBacktrace[19] 0000004add487d68 rip=0000000000000000

            2017-05-08T09:24:35.592Z| vcpu-4| I125: Msg_Post: Error

            2017-05-08T09:24:35.592Z| vcpu-4| I125: [msg.log.error.unrecoverable] VMware ESX unrecoverable error: (vcpu-4)

            2017-05-08T09:24:35.592Z| vcpu-4| I125+ MXUserAllocSerialNumber: too many locks!

            2017-05-08T09:24:35.592Z| vcpu-4| I125: [msg.panic.haveLog] A log file is available in "/vmfs/volumes/58d5407f-3c75947b-e521-1866daf7c776/CA-Winporte/vmware.log". 

            2017-05-08T09:24:35.592Z| vcpu-4| I125: [msg.panic.requestSupport.withoutLog] You can request support. 

            2017-05-08T09:24:35.592Z| vcpu-4| I125: [msg.panic.requestSupport.vmSupport.vmx86]

            2017-05-08T09:24:35.592Z| vcpu-4| I125+ To collect data to submit to VMware technical support, run "vm-support".

            2017-05-08T09:24:35.592Z| vcpu-4| I125: [msg.panic.response] We will respond on the basis of your support entitlement.

            2017-05-08T09:24:35.592Z| vcpu-4| I125: ----------------------------------------

            2017-05-08T09:24:35.593Z| vcpu-4| I125: Exiting

            • 3. Re: VM running on VMWARE host 6.5 has crashed and analyzing vmx-zdump.00 file
              dariusd Virtuoso
              VMware EmployeesUser Moderators

              If your VM has multiple users logged in concurrently (e.g. a virtual server running Terminal Services), the issue you are encountering is that described in this VMware KB article: VMs PANIC: MXUserAllocSerialNumber: too many locks (2149941)

               

              There is a workaround given in that article, and a fix is queued for upcoming update releases of ESXi 6.5.

               

              Thanks,

              --

              Darius

              • 4. Re: VM running on VMWARE host 6.5 has crashed and analyzing vmx-zdump.00 file
                CharlesToro Novice

                Hi,

                Thanks for your prompt reply. I will try to implement work around.