Opened 13 years ago
Closed 11 years ago
#10621 closed defect (fixed)
EFI Panic: Unexpected trap!! on POWERING ON
Reported by: | Milan Oparnica | Owned by: | |
---|---|---|---|
Component: | EFI | Version: | VirtualBox 4.1.16 |
Keywords: | EFI BOOT CRASH PANIC 4.1.16 | Cc: | |
Guest type: | all | Host type: | Linux |
Description
Completele new VM crashes before boot screen when Enable EFI turned on under these circumtances:
Host: KUbuntu 12.04, 3GB RAM, I3 CPU
Guest: Mac OS X Server (the result is same with every other guest type) Base Memory: 1024 MB Acceleration: VT-x/AMD-V, Nested Paging, PAE/NX Video Memory: 6 MB (tried with 16MB and 32MB also) Remote Desktop Server: Disabled
I've tried to delete the machine and create new ones but they all crashed before even boot screen VirtualBox logo appears.
Please note that there are 4 other guest machines (WinXP x 2, Ubuntu 12.04 and Win 7) working perfectly. There must be something wrong with EFI boot option.
Attachments (6)
Change History (22)
by , 13 years ago
comment:1 by , 13 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
We aren't allowed to provide any support for Mac OS guest on non-Apple hardware.
follow-up: 5 comment:2 by , 13 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
You should read more carefully !
Forget about Mac OS (I regret mentioning).
Important thing is it behaves the same on any OS choice...(even unknown).
Please reopen the problem...here is the same VBox.log when Windows 7 is selected choice.
follow-up: 4 comment:3 by , 13 years ago
Hi,
The same issue happens with OS X Snow Leopard guest running on an OS X Snow Leopard host (machine is MacBook Pro). Log file is attached VBox-MacOS.log The crash seems to happen in the EFI boot.
Could you help please?
Thanks.
follow-up: 6 comment:4 by , 13 years ago
Replying to Hichem:
- it happens on on EFI boot, or while Mac goest starting?
- Does it make any difference whether 64-bit MacOS guest is selected?
follow-up: 7 comment:5 by , 13 years ago
Replying to milan.opa:
You should read more carefully !
Ok, MacOs guest is important selection, which on general PC could require addition configuration to start just EFI shell. I've also have noticed OSX_10.6.7.iso in the first log ;)
comment:6 by , 13 years ago
Replying to Hachiman:
- it happens on on EFI boot, or while Mac goest starting?
- Does it make any difference whether 64-bit MacOS guest is selected?
Thanks for your quick feedback. Actually, when the 64 bits mode is enabled, OSX on the guest starts just fine. Thanks for this clue ;) To answer your first question, the VM crashes on EFI, just before the mac boot process. No text is thrown on the console, not even the VirtualBox's starting page.
comment:7 by , 13 years ago
Replying to Hachiman:
Replying to milan.opa:
You should read more carefully !
Ok, MacOs guest is important selection, which on general PC could require addition configuration to start just EFI shell. I've also have noticed OSX_10.6.7.iso in the first log ;)
Yeah, I admit, that's how I bummped into the problem in the first place. :) I run several VM's (for testing purposes only), and was curious to see a Java app I built lately running on Mac (not any more) :)
When started digging it turned out that the problem repeats on any initial OS selection.
There is one thing I didn't mention...before upgrading to 4.1.16, I was using 4.1.14. I first tried EFI boot on that version, but it didn't work either. The problem, though, was different. The VBox initial LOGO did show up but few seconds later message poped out complaining about some EFI BIOS error...I don't remember well, and since I deleted everything there is no log I can send...
comment:8 by , 13 years ago
priority: | blocker → major |
---|
Not working EFI support is a bug but surely not a blocker.
by , 13 years ago
Attachment: | 2012-05-30-08-35-07.097-VirtualBox-3750.log added |
---|
Log found in /home/user/Documents
comment:9 by , 13 years ago
I also get this, but on a Windows 7 (64bit) host. I'm using an unsupported configuration, but I'll attach a log just in case it's helpful when trying to track down the problem.
by , 13 years ago
Attachment: | 2012-06-23-08-41-22.114.VBox.log added |
---|
OS X 10.7.4 host w/OSX Snow Leopard Server guest log from Jean.
follow-up: 11 comment:10 by , 13 years ago
Just added my log, running OS X 10.7.4 (Mac Pro) host w/OSX Snow Leopard Server guest log. Not sure when it stopped working - haven't run this VM in a couple months. Downloaded VBox 4.1.18 r78361 this morning and this VM doesn't work anymore.
comment:12 by , 13 years ago
got same crash with efi.
how-to:
create new VM, finish wizard. go to settings, check efi. start -> crash.
tested win xp x86. full soft virtualization. vb version 4.1.18.78361
!!Assertion Failed!!
Expression: <NULL>
Location : /home/vbox/vbox-4.1.16/src/VBox/Devices/EFI/DevEFI.cpp(372) int efiIOPortWrite
Unexpected trap during early EFI bootstrap!!
related to #8604
between startup and crash have variable number of
Display::handleDisplayResize(): debug messages
comment:13 by , 13 years ago
My 2 cents:
x86 xp host v4.1.18 - vm crashed. Could not reproduce with EFI64.
Downgraded to vbox 4.1.12 - now EFI works.
cheers
follow-up: 15 comment:14 by , 13 years ago
Those of us hosting VirtualBox on Mountain Lion can't downgrade to 4.1.12. Any versions that doesn't panic the host OS also won't run any EFI-based client OS. This pretty much means VirtualBox is useless for hosting any version of OS X on top of Mountain Lion. Please raise the priority of this bug.
comment:15 by , 13 years ago
Replying to dgatwood:
Those of us hosting VirtualBox on Mountain Lion can't downgrade to 4.1.12. Any versions that doesn't panic the host OS also won't run any EFI-based client OS. This pretty much means VirtualBox is useless for hosting any version of OS X on top of Mountain Lion. Please raise the priority of this bug.
You don't need to downgrade anything, you may just use 64-bit EFI.
comment:16 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Most likely fixed in 4.3.x (many EFI fixes).
Last after-crash log file...