[Solved] error: "A breakpoint has been reached."(0x80000003)

[santo998]

Since a week, I have an error at starting Fedora 22 (ultimate release version) in a Windows 8.1 host.
Also it runs very, very slow. I don't know if I need to install some packages or not to run it well.
Please help me, I send you my logs as an attachment, sorry for my bad english, please help me.

[mpack]

Please post a VM log file. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

[santo998]

Ok, there is my VM log file

[mpack]

Though probably unrelated, I see this in the log :-

00:00:09.415600 HM: HMR3Init: Falling back to raw-mode: VT-x is disabled in the BIOS for both all CPU modes

I see that you have a KVM interface turned on for the guest. As a new feature I would toggle that and see if that makes a difference. Does Fedora have KVM support anyway?

The "very very slow" part could be due to running with only 512MB RAM. You can double that on your host.

The last part of the log has this :-

00:00:44.709126 NAT: Link up
00:01:42.315449
00:01:42.315451 !!Assertion Failed!!
00:01:42.315452 Expression: (efl & X86_EFL_IF) || fPatchCode || rawRC == VINF_PATM_PENDING_IRQ_AFTER_IRET || RT_FAILURE(rawRC)
00:01:42.315454 Location : F:\tinderbox\win-5.0\src\VBox\VMM\VMMAll\PATMAll.cpp(169) void __cdecl PATMRawLeave(struct VM *,struct CPUMCTX *,int)
00:01:42.315620 Inconsistent state at ff269bc2 rc=VINF_EM_RAW_GUEST_TRAP

PATM is (I believe) "Patch Manager", the part of VirtualBox which patches code that can't be virtualized. It would imply that the guest OS is doing something nasty. This should go away if you enable VT-x.

[loukingjr]

FWIW, I believe the "Default" paravirtualization setting for all Linux guests is KVM.

[santo998]

Thank's you so much guys!!!
My problem was that VT-x was disabled in the BIOS
I just enabled VT-x in the BIOS and now Fedora 22 it's running faster than before and without any errors