VMware Communities
Trung_IT
Contributor
Contributor
Jump to solution

Error "A fault has occurred causing a virtual CPU to enter the shutdown state..." when run "Browser_In_The_Box.5.2.2-r711.firefox.Archive.exe" in Vmware workstation 15 Pro.

Dear All,

This is my configuration:

Host:

  + Hardware: HP Z240 Tower Worktation

         Note:   enable Virtualization Technology( VTx),

                     enable Virtualization Technology for Directed I/O (Vtd)

  + OS: Windows 10 Pro 1709 (64 bit)

            Vmware workstation 15 Pro

            Note:    enable Virtualization engine

Guest:

+ OS: Windows 10 Pro 1903 (64 bit)  (UEFI / BIOS)

   

First, i setup "Browser_In_The_Box.5.2.2-r711.firefox.Archive.exe" in Guest OS. It is OK.

After that. I run "Browser in the Box" shortcut in the Desktop. I get error:

"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 Workstation".

BitBox_error.png

I try:

   + enable in BIOS Hp Z240: Virtualization Technology( VTx),

                                              Virtualization Technology for Directed I/O (Vtd)

   + install Guest OS in the both (UEFI/ BIOS)

   + seach google to find solution

   + enable all Virtualization engine of Vmware workstation 15 Pro

Enable VMWare Virtualization.png

But, It is still error.

Do you have any solution ?

Please help me.Thanks!

1 Solution

Accepted Solutions
Susie201110141
VMware Employee
VMware Employee
Jump to solution

Hi Trung_IT,

I've reproduced your issue locally, and the root cause of the error is due to a bug of virtual box.

To workaround this, you can add following line into you Win10 1903 VM's vmx file:
featMask.vm.cpuid.PCID="Max:0"

Let me know if it works for you well.

---------------------------------------------------------------------------------------------------------

Was it helpful? Let us know by completing this short survey here.

View solution in original post

20 Replies
asajm
Expert
Expert
Jump to solution

Hi

Look

VMware Knowledge Base

If you think your queries have been answered
Marking this response as "Solution " or "Kudo"
ASAJM
Reply
0 Kudos
Trung_IT
Contributor
Contributor
Jump to solution

Thanks  asajm

I try add monitor.suspend_on_triplefault to .vmx file before i post this.

The result is the same error Smiley Sad .

Reply
0 Kudos
asajm
Expert
Expert
Jump to solution

Try to add the following to the virtual machine VMX file

monitor_control.disable_longmode = TRUE

If you think your queries have been answered
Marking this response as "Solution " or "Kudo"
ASAJM
Reply
0 Kudos
Trung_IT
Contributor
Contributor
Jump to solution

Thanks  asajm

I try add monitor_control.disable_longmode = TRUE to .vmx file.

The result is the same error Smiley SadSmiley Sad .

If you free. You can test yourself.

BitBox - Browser in the Box (Chrome-Edition)

- https://www.chip.de/downloads/BitBox-Browser-in-the-Box-Chrome-Edition_72247952.html

- https://www.computerbild.de/download/BitBox-Browser-in-the-Box-Chrome-Edition-11284671.html

BitBox (Browser in the Box, Firefox-Edition)

- https://www.computerbild.de/download/BitBox-Browser-in-the-Box-Firefox-Edition-6187028.html

Reply
0 Kudos
continuum
Immortal
Immortal
Jump to solution

It makes no sense to randomly add vmx-parameters that are useful on other cases that produce the same error-message.

But it may help to see a vmware.log copied next time you reproduce the error.


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
Trung_IT
Contributor
Contributor
Jump to solution

Thanks continuum

This is my log:

...

2019-08-15T11:57:01.438+07:00| vcpu-1| W115: X86Fault_Warning: vmcore/vmm/cpu/interp.c:2279: cs:rip=0x10:0xfffff8063c961e60 fault=13

2019-08-15T11:57:01.438+07:00| vcpu-1| I125: Triple fault.

2019-08-15T11:57:01.438+07:00| vcpu-1| I125: MsgHint: msg.monitorEvent.tripleFault

2019-08-15T11:57:01.438+07: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 Workstation.---------------------------------------

2019-08-15T11:57:18.569+07:00| vmx| I125: Stopping VCPU threads...

2019-08-15T11:57:18.569+07:00| vcpu-0| I125: CPU reset: hard (mode 1)

2019-08-15T11:57:18.569+07:00| vcpu-1| I125: CPU reset: hard (mode 0)

2019-08-15T11:57:18.569+07:00| vcpu-2| I125: CPU reset: hard (mode 1)

2019-08-15T11:57:18.569+07:00| vcpu-3| I125: CPU reset: hard (mode 1)

...

Here is Full log:

Reply
0 Kudos
continuum
Immortal
Immortal
Jump to solution

Do you use G: for Onedrive ?


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
continuum
Immortal
Immortal
Jump to solution

Please try if it works with the attached vmx-file.

Preferably try on a full copy of the VM-directory.

Dont be surprised - I removed USB-support and other questionable devices.

Ulli


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
Trung_IT
Contributor
Contributor
Jump to solution

Thanks continuumfor test.vmx

I replace my "Win10_64_UEFI_1903.vmx" by your test.vmx ( removed USB-support and other questionable devices.).

But, the result is the same Smiley Sad .

I think the best way. you should download and test by yourself.

BitBox - Browser in the Box (Chrome-Edition)

- https://www.chip.de/downloads/BitBox-Browser-in-the-Box-Chrome-Edition_72247952.html

- https://www.computerbild.de/download/BitBox-Browser-in-the-Box-Chrome-Edition-11284671.html

BitBox (Browser in the Box, Firefox-Edition)

- https://www.computerbild.de/download/BitBox-Browser-in-the-Box-Firefox-Edition-6187028.html

Reply
0 Kudos
continuum
Immortal
Immortal
Jump to solution

> I think the best way. you should download and test by yourself.

I already tried - I even created a Win 10 - 1903 VM extra for that purpose but my results will not help you as I dont use a Win 10 host - ( I am not qualified for that - lack of masochistic tendencies) and I dont use WS 15 as my hardware only allows WS 12.

Anyway - on WS 12 a Win10 VM can run Browser in a Box without tripple fault.

I would suggest you search google for "how to run nested VMs in WS 15" and "how to run Virtualbox inside a Workstation VM."


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
Trung_IT
Contributor
Contributor
Jump to solution

Thanks continuum for your recommend.

After many unsuccessful solution, i decide test more some case:

1. Still configured as above, i run "Browser_In_The_Box" in Compatibility Mode = Windows 8. Error still occurs.Smiley Sad

2. I keep VMWare 15 pro, and only change "Hardware Compatibility" of Guest OS "Win10_64_UEFI_1903" down to:  14.x, 12.x, 11.x 10.x, 9.x. Error still occurs.Smiley Sad

3. I keep VMWare 15 pro, and i install one more Windows 10 1709 64 bit (same version with Host OS). The result is OK :smileycheck: Smiley Happy.

    But i am worried, after a period of use. Guest OS (Win 1709) will auto upgrade to 1903 or higher and may lead to errors.  

Reply
0 Kudos
Susie201110141
VMware Employee
VMware Employee
Jump to solution

Hi Trung_IT,

I've reproduced your issue locally, and the root cause of the error is due to a bug of virtual box.

To workaround this, you can add following line into you Win10 1903 VM's vmx file:
featMask.vm.cpuid.PCID="Max:0"

Let me know if it works for you well.

---------------------------------------------------------------------------------------------------------

Was it helpful? Let us know by completing this short survey here.

Trung_IT
Contributor
Contributor
Jump to solution

Many thanks Susie201110141

Hi Trung_IT,

I've reproduced your issue locally, and the root cause of the error is due to a bug of virtual box.

I do not think so. It is not a Bug of virtual box. Because, i can run BitBox (without add featMask.vm.cpuid.PCID="Max:0" to .vmx file) in Guest OS (Windows 10 1709 64 bit = version with Host OS). The result is OK:smileycheck:. (see previous post ). It is very strange ? It is hard to understand ? :smileydevil:

And I also can run Virtual box independently without  error.

VB_5.png

To workaround this, you can add following line into you Win10 1903 VM's vmx file:
featMask.vm.cpuid.PCID="Max:0"

Let me know if it works for you well.

It work great :smileycheck::smileycheck::smileycheck:. You are PRO Smiley HappyHeart.

Reply
0 Kudos
Susie201110141
VMware Employee
VMware Employee
Jump to solution

Good to know that it works for you.

You can mark the issue as "answered" if you could Smiley Happy. Enjoy using workstation!

Reply
0 Kudos
Trung_IT
Contributor
Contributor
Jump to solution

Oh, no problem Smiley Happy.

Thanks Susie201110141

Have a nice day!

Reply
0 Kudos
hiyal
Enthusiast
Enthusiast
Jump to solution

That solved the problem

Now i can run Android emulator in Win10 guest in vmware

Reply
0 Kudos
HickWand
Contributor
Contributor
Jump to solution

It worked for me!

Reply
0 Kudos
SpiffJ
Contributor
Contributor
Jump to solution

Hi

 

Does anyone know how i can locate Win10 VM's vmx file?  Is it the one highlighted in the attached screenshot? i have  also attched my system info

Reply
0 Kudos
Technogeezer
Immortal
Immortal
Jump to solution

It's easier to locate if you change the settings in File Explorer to show extensions. 

The one you have highlighted is not the file. - it is a lock file directory, used to note that Workstation has the .vmx file open. 

- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides
Reply
0 Kudos