Opened 6 years ago
Last modified 6 years ago
#17349 new defect
VINF_EM_TRIPLE_FAULT
| Reported by: | ke | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.2.0 |
| Keywords: | triple fault VINF_EM_TRIPLE_FAULT | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
I get guru meditation immediately after the Virtualbox BIOS screen and the log says VINF_EM_TRIPLE_FAULT. This is in a guest machine where I just freshly installed RHEL 7.4 64 bit running on Windows 7 64 bit host. The guest started to boot the first start after I installed RHEL but triple fault occurred before boot finished. Every other boot gets triple fault immediately after the Virtualbox BIOS screen. I see lots of other triple fault bugs but none for Red Hat.
Error occurs on latest stable and latest testing builds
Stable VirtualBox-5.2.2-119230-Win.exe
Testing Version 5.2.3 r119405 (Qt5.6.2)
Attachments (2)
Change History (6)
by , 6 years ago
comment:1 by , 6 years ago
https://forums.virtualbox.org/search.php?keywords=VINF_EM_TRIPLE_FAULT says Search found 0 matches. However Google points to https://forums.virtualbox.org/viewtopic.php?f=7&t=62174 which has VINF_EM_TRIPLE_FAULT in the title so there are matches. I have tried to search the forum anyway.
Also I don't see how to modify the ticket.
I appreciate all help on this. Thanks very much. Brendan
comment:2 by , 6 years ago
Host RAM: 8055MB (7.8GB) total, 440MB available RamSize <integer> = 0x000000007d000000 (2 097 152 000, 2 000 MB)
You are assigning memory to your guest, that you do not have available. Either close some applications on the host, buy more RAM for the host, or reduce the amount of RAM assigned to the guest.
CPUM: Physical host cores: 2 NumCPUs <integer> = 0x0000000000000002 (2)
You have assigned all your CPUs to the VM. The host is going to run low on resources, since VirtualBox cares about physical processors, not logical ones. See: "CPU Cores versus threads" and "Why is it a bad idea to allocate as many VCPUs as there are physical CPUs?". Also, check the specifications for your i5-3427U CPU and check the number of cores.
00:00:01.591507 VRamSize <integer> = 0x0000000000c00000 (12 582 912, 12 MB)
Your video RAM seems a tad too low. I would take it up to 16 or 32 MB.
Finally, may I suggest something? It's usually better and faster, if issues get first addressed in the VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of.
comment:3 by , 6 years ago
The first post I saw in the forum about VINF_EM_TRIPLE_FAULT, linked above, recommended creating a bug. Sorry, I didn't realise the process was to always start in the forum first. What now? Do you want me to take this to the forum instead or stay here?
Problem still exists after reducing virtual machine processors to 1, VRAM to 32mbytes and ensuring plenty of free host memory.
comment:4 by , 6 years ago
No, it doesn't help if you go to the forums now, we have directed you to file a new ticket in any event... :)
You are right that Triple_Faults should be addressed in the bug tracker, mainly because they are too cryptic for normal volunteers to debug. The advice I gave you was a "generic" one, something that I give every user out there.
If you made those changes that I suggested, and you're still getting the Guru Meditation, you're in the right place ;)
VINF_EM_TRIPLE_FAULT