VMware Communities
Kotalos
Contributor
Contributor

A fault has occurred causing a virtual CPU to enter the shutdown state.

Hi All,

I use VM Player 14.1.2 on WIn10 64 Bits and I recently experienced some of the above message with one of my win 7 VM.

After a few trial, I discovered that my isssue is close related to network "Bridged: Connected directly to physical network".

Everything run fine if "NAT: Used to share the host's IP address".

So did the trial to boot in NAT mode and when every was up and running, switch over to Bridged mode @ 11AM. Here is the log file extract 

Any idea about the thing I do wrong ?

2018-06-19T11:00:00.554+02:00| vmx| I125: TOOLS received request in VMX to set option 'synctime' -> '1'

2018-06-19T11:00:00.554+02:00| vmx| A100: ConfigDB: Setting tools.syncTime = "TRUE"

2018-06-19T11:00:00.570+02:00| vmx| I125: VMXVmdb_SetCfgState: cfgReqPath=/vm/#_VMX/vmx/cfgState/req/#8f/, remDevPath=/vm/#_VMX/vmx/vigor/setCfgStateReq/#c0/in/

2018-06-19T11:00:00.617+02:00| vmx| I125: TOOLS received request in VMX to set option 'synctime' -> '1'

2018-06-19T11:00:00.617+02:00| vmx| A100: ConfigDB: Setting tools.syncTime = "TRUE"

2018-06-19T11:00:00.648+02:00| vmx| A100: ConfigDB: Setting tools.upgrade.policy = "upgradeAtPowerCycle"

2018-06-19T11:00:00.707+02:00| vmx| A100: ConfigDB: Unsetting "ethernet0.connectionType"

2018-06-19T11:00:00.707+02:00| vmx| I125: FILE: FileDeletionRetry: Non-retriable error encountered (D:\Virtual Machines\Win 7 Professional 32Bits\Windows 7 Professional 32Bits.vmx~): The system cannot find the file specified (2)

2018-06-19T11:00:00.779+02:00| vmx| A100: ConfigDB: Setting ethernet0.addressType = "generated"

2018-06-19T11:00:00.779+02:00| vmx| A100: ConfigDB: Setting ethernet0.generatedAddress = "00:0C:29:B2:8F:76"

2018-06-19T11:00:00.813+02:00| vmx| A100: ConfigDB: Setting ethernet0.virtualDev = "e1000"

2018-06-19T11:00:00.880+02:00| vmx| I125: Vigor_EthernetScheduleReconnect: reconnect delay = 7 seconds, reconnectEthVector = 0x1

2018-06-19T11:00:02.782+02:00| vcpu-1| I125: DISKUTIL: scsi0:0 : capacity=125829120 logical sector size=512

2018-06-19T11:00:02.782+02:00| vcpu-0| I125: DISKUTIL: scsi0:0 : capacity=125829120 logical sector size=512

2018-06-19T11:00:03.990+02:00| vcpu-1| I125: DISKUTIL: scsi0:0 : capacity=125829120 logical sector size=512

2018-06-19T11:00:04.372+02:00| vcpu-0| I125: DISKUTIL: scsi0:0 : capacity=125829120 logical sector size=512

2018-06-19T11:00:04.670+02:00| vcpu-1| I125: DISKUTIL: scsi0:0 : capacity=125829120 logical sector size=512

2018-06-19T11:00:04.685+02:00| vcpu-0| I125: DISKUTIL: scsi0:0 : capacity=125829120 logical sector size=512

2018-06-19T11:00:06.577+02:00| vcpu-1| I125: DISKUTIL: scsi0:0 : capacity=125829120 logical sector size=512

2018-06-19T11:00:06.577+02:00| vcpu-1| I125: DISKUTIL: scsi0:0 : capacity=125829120 logical sector size=512

2018-06-19T11:00:06.592+02:00| vcpu-0| I125: DISKUTIL: scsi0:0 : capacity=125829120 logical sector size=512

2018-06-19T11:00:09.408+02:00| vmx| I125: VNET: MACVNetConnectToNetwork 'Ethernet0' notify available.

2018-06-19T11:00:09.408+02:00| vmx| I125: EthernetDelayedConnect: Delayed connect of network adapter ethernet0 succeeded.

2018-06-19T11:00:17.475+02:00| vcpu-1| I125: Triple fault.

2018-06-19T11:00:17.475+02:00| vcpu-1| I125: MsgHint: msg.monitorEvent.tripleFault

2018-06-19T11:00:17.475+02:00| vcpu-1| I125+ A fault has occurred causing a virtual CPU to enter the shutdown state. If this fault had occurred outside of a virtual machine, it would have caused the physical machine to restart. The shutdown state can be reached by incorrectly configuring the virtual machine, a bug in the guest operating system, or a problem in VMware Player.---------------------------------------

Reply
0 Kudos
0 Replies