Virtual machine fails with an unexpected signal 11 error
search cancel

Virtual machine fails with an unexpected signal 11 error

book

Article ID: 327857

calendar_today

Updated On:

Products

VMware

Issue/Introduction

This article describes a specific issue. If you experience all of the preceding symptoms, refer the following sections. If you experience some but not all of these symptoms, your issue is not related to this article. Search for your symptoms in the Knowledge Base or Open a Support Request.


Symptoms:
  • A virtual machine fails after it experiences the signal 11 error (sigfault).
  • In the vmware.log file, you see entries similar to:

    vcpu-1| TOOLS unified loop capability requested by 'toolbox-dnd'; now sending options via TCLO
    vcpu-1| GuestRpc: Channel 1, App stopped
    vcpu-1| GuestRpc: Reinitializing Channel 1(toolbox-dnd)
    vcpu-1| GuestRpc: Channel 1 reinitialized.
    vcpu-1| GuestRpc: Channel 2, guest application toolbox-dnd.
    vcpu-1| VMXVmdb_LoadRawConfig: Loading raw config
    vcpu-1| VMXVmdb_LoadRawConfig: Loading raw config
    vcpu-1| Caught signal 11 -- tid 18012684
    vcpu-1| SIGNAL: eip 0x4f467cee esp 0x7b408dc8 ebp 0x7b408e20
    vcpu-1| SIGNAL: eax 0x7b408ea0 ebx 0x2a0ac5b0 ecx 0x29fec9c0 edx 0x15 esi 0x0 edi 0x7b408ea0
    vcpu-1| r8 0x6 r9 0x7b408ea0 r10 0x2 r11 0x206 r12 0x10000 r13 0x6 r14 0x15 r15 0x15
    vcpu-1| SIGNAL: stack 7B408DC8 : 0x2979475e 0x00000000 0x7b408e60 0x00000000
    vcpu-1| SIGNAL: stack 7B408DD8 : 0x29866ad0 0x00000000 0x7b408ea0 0x00000000
    vcpu-1| SIGNAL: stack 7B408DE8 : 0x29fec9c0 0x00000000 0x7b408e00 0x00000000
    vcpu-1| SIGNAL: stack 7B408DF8 : 0xe27212c8 0x000003ff 0x00000015 0x00000000
    vcpu-1| SIGNAL: stack 7B408E08 : 0x00000006 0x00000000 0x7b408ea0 0x00000000
    vcpu-1| SIGNAL: stack 7B408E18 : 0x29794270 0x00000000 0x7b408e60 0x00000000
    vcpu-1| SIGNAL: stack 7B408E28 : 0x297b3041 0x00000000 0x00000000 0x00000000
    vcpu-1| SIGNAL: stack 7B408E38 : 0x00000000 0x00000000 0xe2737980 0x000003ff
    vcpu-1| Backtrace:
    vcpu-1| Backtrace[0] 000000007b4089c0 rip=0000000029a691cd rbx=0000000000000000 rbp=000000007b4089e0 r12=0000000029a68fd0 r13=000000007b408a01 r14=000000007b408b70 r15=0000000000000005
    vcpu-1| Backtrace[1] 000000007b4089f0 rip=0000000029702d96 rbx=0000000000000080 rbp=000000007b408ae0 r12=000000000000000b r13=000000007b408a01 r14=000000007b408b70 r15=0000000000000005
    vcpu-1| Backtrace[2] 000000007b408af0 rip=000000000022c00f rbx=000000002a0ac5b0 rbp=000000007b408d30 r12=000000007b408b70 r13=0000000000000006 r14=0000000000000015 r15=0000000000000015
    vcpu-1| SymBacktrace[0] 000000007b4089c0 rip=0000000029a691cd in function (null) in object /bin/vmx loaded at 0000000029590000
    vcpu-1| SymBacktrace[1] 000000007b4089f0 rip=0000000029702d96 in function (null) in object /bin/vmx loaded at 0000000029590000
    vcpu-1| SymBacktrace[2] 000000007b408af0 rip=000000000022c00f
    vcpu-1| Unexpected signal: 11.
    vcpu-1| Writing monitor corefile "/vmfs/volumes/1479eb9f-f3c6c519/vw-srv710-sanjose/vmware64-core0.gz"
    vcpu-1| CoreDump: dumping core with superuser privileges
    vcpu-1| VMK Stack for vcpu 0 is at 0x417f838b9000
    vcpu-1| Saving busmem frames
    vcpu-1| Saving anonymous memory
    vcpu-1| Beginning monitor coredump
    vcpu-1| End monitor coredump
    vcpu-1| Beginning extended monitor coredump
    vcpu-1| Writing anonymous pages at pos: 4008000
    vcpu-1| Writing monitor corefile "/vmfs/volumes/1479eb9f-f3c6c519/vw-srv710-sanjose/vmware64-core1.gz"
    vcpu-1| CoreDump: dumping core with superuser privileges
    vcpu-1| VMK Stack for vcpu 1 is at 0x417f838c9000
    vcpu-1| Saving busmem frames
    vcpu-1| Saving anonymous memory
    vcpu-1| Beginning monitor coredump
    vcpu-1| End monitor coredump
    vcpu-1| Beginning extended monitor coredump
    vcpu-1| Writing anonymous pages at pos: 4008000
    vcpu-1| Backtrace:
    vcpu-1| Backtrace[0] 000000007b4084c0 rip=0000000029a691cd rbx=0000000000000000 rbp=000000007b4084e0 r12=0000000029a68fd0 r13=000000002a096220 r14=000000007b408b70 r15=0000000000000005
    vcpu-1| Backtrace[1] 000000007b4084f0 rip=000000002966bdb4 rbx=0000000000000001 rbp=000000007b4089e0 r12=000000007b4084f0 r13=000000002a096220 r14=000000007b408b70 r15=0000000000000005
    vcpu-1| Backtrace[2] 000000007b4089f0 rip=0000000029702f2f rbx=000000007b408a30 rbp=000000007b408ae0 r12=000000000000000b r13=000000007b408a01 r14=000000007b408b70 r15=0000000000000005
    vcpu-1| Backtrace[3] 000000007b408af0 rip=000000000022c00f rbx=000000002a0ac5b0 rbp=000000007b408d30 r12=000000007b408b70 r13=0000000000000006 r14=0000000000000015 r15=0000000000000015
    vcpu-1| SymBacktrace[0] 000000007b4084c0 rip=0000000029a691cd in function (null) in object /bin/vmx loaded at 0000000029590000
    vcpu-1| SymBacktrace[1] 000000007b4084f0 rip=000000002966bdb4 in function (null) in object /bin/vmx loaded at 0000000029590000
    vcpu-1| SymBacktrace[2] 000000007b4089f0 rip=0000000029702f2f in function (null) in object /bin/vmx loaded at 0000000029590000
    vcpu-1| SymBacktrace[3] 000000007b408af0 rip=000000000022c00f
    vcpu-1| Msg_Post: Error
    vcpu-1| [msg.log.error.unrecoverable] VMware ESX unrecoverable error: (vcpu-1)
    vcpu-1| Unexpected signal: 11.

  • The vmware directory contains the vmx core dump vmx-core.00#.


Cause

This issue may occur:
  • If the communication between VMware Tools and the vmx is interrupted at a particular point and is then restarted at a later stage.
  • On any virtual machine, but more often on virtual machines with VMware Tools running, especially on busy virtual machines where VMware Tools needs to get scheduled to run.

Resolution

This issue is resolved in VMware ESX/ESXi 4.1 Update 3, available at VMware Downloads.


Additional Information

How to file a Support Request in Customer Connect