Fatal failure : Guru Meditation

[NMe]

Hello,

I experience a fatal failure in a VM, warning asks to post to Oracle VirtualBox Forum.

Host is W10 Pro x64.
VM is W10 Pro x64 recently installed over W7 Pro x64.
VBox version is 6.1.0 r135406 (Qt5.6.2)

The fatal failure happens when I launch Corel Paint X5 application, just after display of the Corel Paint logo.
The warning mentions Guru Meditation.
I pressed OK button to close the VM.
Please find log and vbox files in the joined zip.

Corel Suite X5 has been installed a few years ago, and Paint application (photos, pixels) had often showed brutal stops after a period about one hour working. But never when at start. Note Draw (drawings, vectoriel) application starts and operates normally.

For your information, and thank you for a workaround, if any.

NMe

[scottgus1]

Here's what happens before the Guru Meditation:

00:12:49.351776 HM: VERR_VMX_UNABLE_TO_START_VM:
00:12:49.351780 HM: CPU[1] Guest VMCS active
00:12:49.351784 HM: CPU[1] Instruction error    0x0
00:12:49.351787 HM: CPU[1] Exit reason          0x0
00:12:49.351791 HM: VERR_VMX_UNABLE_TO_START_VM: VM-entry allowed-1  0xffff
00:12:49.351795 HM: VERR_VMX_UNABLE_TO_START_VM: VM-entry allowed-0  0x11ff

Googling:
VERR_VMX_UNABLE_TO_START_VM site:forums.virtualbox.org
shows that regrettably we have not been able to pin down exactly what causes this.

Microsoft Hyper-V could be running on your host PC. In most cases Hyper-V blocks Virtualbox. See I have a 64bit host, but can't install 64bit guests. Try this:

1. Shut down all programs. You will have to reboot your host.

2. Look into the 64-bits tutorial, 2nd post, points 2 & 3 and ensure that none of these things are running.

3. Find the Command Prompt icon, right click it and choose Run As Administrator.

4. Enter this command:

bcdedit /set hypervisorlaunchtype off

5. Enter this command:

shutdown -s -t 2

6. When the computer turns off, unplug it for 20 seconds. Then plug it in again and boot up Windows 10.

[fth0]

Probably related to viewtopic.php?f=2&t=96077 / https://www.virtualbox.org/ticket/19171, although you are using a different application. I don't know a solution ATM, though.

[softjury]

The cause of this issue was identified and a fix will be shipped with the next patch release of VirtualBox, see Ticket 19171.