We have a vm guest that always reported unexpected restart but can find an issue within, but to make sure I have here the vmlogs of that guest for checking. Can someone knows how to read this logs or with this logs, do we have a configuration settings that need to be implemented?
Thank you
Jun 20 22:33:05.268: vcpu-0| VMMouse: CMD Disable
Jun 20 22:33:05.268: vcpu-0| VMMouse: Disabling VMMouse mode
Jun 20 22:33:06.532: vcpu-0| VMMouse: CMD Read ID
Jun 20 22:33:12.132: vcpu-1| Balloon: Start: vmmemctl reset balloon
Jun 20 22:33:12.132: vcpu-1| Balloon: Reset (n 9 pages 0)
Jun 20 22:33:12.132: vcpu-1| Balloon: Reset: nUnlocked 0 size 0
Jun 20 22:33:12.494: vcpu-0| GuestRpc: Channel 2 reinitialized.
Jun 20 22:33:12.569: vcpu-0| GuestRpc: Channel 1, App stopped
Jun 20 22:33:12.569: vcpu-0| GuestRpc: Reinitializing Channel 1(toolbox)
Jun 20 22:33:12.569: vcpu-0| GuestMsg: Channel 1, Cannot unpost because the previous post is already completed
Jun 20 22:33:12.570: vcpu-0| GuestRpc: Channel 1 reinitialized.
Jun 20 22:33:12.570: vcpu-0| GuestRpc: application toolbox already registered, id: -1
Jun 20 22:33:12.570: vcpu-0| GuestRpc: Channel 3, guest application toolbox.
Jun 20 22:33:12.623: vcpu-0| TOOLS ToolsCapabilityGuestTempDirectory received 1 /tmp/vmware-root
Jun 20 22:33:12.624: vcpu-0| TOOLS autoupgrade protocol version 2
Jun 20 22:33:12.626: vcpu-0| TOOLS ToolsCapabilityGuestConfDirectory received /etc/vmware-tools
Jun 20 22:33:12.626: vcpu-0| ToolsSetVersionWork did nothing; new tools version (8295) matches old Tools version
Jun 20 22:33:12.627: vcpu-0| TOOLS unified loop capability requested by 'toolbox'; now sending options via TCLO
Jun 20 22:33:12.628: vcpu-0| Guest: toolbox: Version: build-341836
Jun 20 22:33:34.257: vcpu-2| CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0
Jun 20 22:33:34.261: vcpu-2| CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0
Jun 20 22:33:34.295: vcpu-0| FLOPPYLIB-MAIN : CMD Checking status for non-existent Drive 0
Jun 20 22:33:58.930: vcpu-2| VMMouse: CMD Disable
Jun 20 22:33:58.930: vcpu-2| VMMouse: Disabling VMMouse mode
Jun 20 22:33:59.100: vcpu-3| SVGA: Unregistering IOSpace at 0x10d0
Jun 20 22:33:59.100: vcpu-3| SVGA: Unregistering MemSpace at 0xd4000000(0xd4000000) and 0xd8000000(0xd8000000)
Jun 20 22:33:59.104: vcpu-3| SVGA: Registering IOSpace at 0x10d0
Jun 20 22:33:59.104: vcpu-3| SVGA: Registering MemSpace at 0xd4000000(0xd4000000) and 0xd8000000(0xd8000000)
Jun 20 22:33:59.233: vcpu-0| SVGA: Unregistering IOSpace at 0x10d0
Jun 20 22:33:59.233: vcpu-0| SVGA: Unregistering MemSpace at 0xd4000000(0xd4000000) and 0xd8000000(0xd8000000)
Jun 20 22:33:59.237: vcpu-0| SVGA: Registering IOSpace at 0x10d0
Jun 20 22:33:59.237: vcpu-0| SVGA: Registering MemSpace at 0xd4000000(0xd4000000) and 0xd8000000(0xd8000000)
Jun 20 22:33:59.555: mks| Guest display topology changed: numDisplays 1
Jun 20 22:33:59.560: vcpu-2| VMMouse: CMD Read ID
Jun 20 22:33:59.560: vcpu-2| VMMouse: CMD Disable
Jun 20 22:33:59.560: vcpu-2| VMMouse: Disabling VMMouse mode
Jun 20 22:34:00.597: vcpu-0| VMMouse: CMD Read ID