Reaching breakpoint when trying to create red hat box on windows machine

Discussions about using Linux guests in VirtualBox.
Post Reply
ellebelle
Posts: 3
Joined: 3. Apr 2022, 11:16

Reaching breakpoint when trying to create red hat box on windows machine

Post by ellebelle »

Hi, I'm getting an ExceptionCode=0x80000003 and a Breakpoint dialog when trying to open a new box. I have looked at some of the other posts on this and looked at the logs, uninstalled and reinstalled virtual box, as well as trying different versions and also trying Ubuntu instead of red hat - nothing seems to work. I have virtualisation turned on on my machine and all config is the same as my colleagues who are all able to use virtual box without error - does anyone have any suggestions?
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Reaching breakpoint when trying to create red hat box on windows machine

Post by mpack »

Not a question about "Using VirtualBox".

I'm assuming this "breakpoint" is in the guest OS since you don't specify. Hence topic moved to "Linux Guests".

Provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
ellebelle
Posts: 3
Joined: 3. Apr 2022, 11:16

Re: Reaching breakpoint when trying to create red hat box on windows machine

Post by ellebelle »

I've attached the log here, thanks!
Attachments
VBox.zip
Thanks - here is the log
(114 Bytes) Downloaded 6 times
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Reaching breakpoint when trying to create red hat box on windows machine

Post by mpack »

That zip contains a 0 byte log. Not very useful. If we don't get complete log files or a complete description of the error then I'm afraid we can't help.
ellebelle
Posts: 3
Joined: 3. Apr 2022, 11:16

Re: Reaching breakpoint when trying to create red hat box on windows machine

Post by ellebelle »

Sorry, unsure why it won't save directly from virtualbox. I've copied into a notepad
Attachments
VBox.log.zip
(21.17 KiB) Downloaded 8 times
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Reaching breakpoint when trying to create red hat box on windows machine

Post by mpack »

And now it's the wrong log. You gave me a renamed VBoxHardening.log. The log I asked for is called "VBox.log". The hardening log shows the error code you mention, but I don't see many clues as to possible causes.

I think the fact that you have Windows configured to lie to you about filenames may be adding to your confusion. In Windows, open a file explorer window. Click on "View", then the "Options" button, select "View" again from the "Folder Options" dialog, and untick the option to "Hide extensions for known file types".
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Reaching breakpoint when trying to create red hat box on windows machine

Post by fth0 »

For a test, uninstall the Carbon Black software, and see if the issue persists.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Reaching breakpoint when trying to create red hat box on windows machine

Post by fth0 »

mpack wrote:I'm assuming this "breakpoint" is in the guest OS since you don't specify. Hence topic moved to "Linux Guests".
FWIW, the ExceptionCode 0x80000003 (STATUS_BREAKPOINT) means that running VirtualBox led to an INT3 breakpoint instruction being reached on the Windows host.
pixcellator
Posts: 1
Joined: 6. Dec 2022, 10:20

Re: Reaching breakpoint when trying to create red hat box on windows machine

Post by pixcellator »

fth0 wrote:For a test, uninstall the Carbon Black software, and see if the issue persists.
After hours wasted trying to resolve, it was CarbonBlack causing the issue - thank you!
Post Reply