Ticket #12405 (closed defect: fixed)
Kernel Panic - not syncing: fatal exception
| Reported by: | Lamishi | Owned by: | |
|---|---|---|---|
| Component: | VM control | Version: | VirtualBox 4.3.2 |
| Keywords: | kernel | Cc: | |
| Guest type: | other | Host type: | other |
Description
I have downloaded and installed PeopleSoft HCM 9.2 (HCMDB-85307) from PUM. When I started the Virtual box to run the first time, it is not booting. The scroll goes fast and the last message I see is
Kernel Panic - not syncing: fatal exception
Pid: 1, comm: swapper Tainted: G D W 2.6.32-400.28.1.el5uek #1 Call Trace:
I installed VB on Windows 7 64 bit laptop. The Virtual Image has Linux OS.
Attachments
-
VM_Error.doc
(142.0 KB) -
added by Lamishi 9 years ago.
- Screenshot and VB log file
Change History
Changed 9 years ago by Lamishi
-
attachment
VM_Error.doc
added
comment:1 follow-up: ↓ 3 Changed 7 years ago by frank
- Status changed from new to closed
- Resolution set to fixed
Please reopen if still relevant with VBox 5.0.8. And please never ever put the VBox.log file into a .doc document!
comment:2 Changed 6 years ago by Rashmi
Is this issue resolved. May I get the steps to resolve this issue. I am having same issue with Oracle Linux VM. Your quick response will be a great save.
comment:3 in reply to: ↑ 1 Changed 6 years ago by Rashmi
Replying to frank:
Please reopen if still relevant with VBox 5.0.8. And please never ever put the VBox.log file into a .doc document!
Hi Frank, may I know the resolution. Am getting same error while booting the Oracle Linux VM.
Thanks, Rashmi
comment:4 Changed 6 years ago by frank
Hi Rashmi, I'm not sure if this issue is really resolved. We've got only one report so far and no further comments. The original reporter used a very old version of VirtualBox. Therefore my comment that this ticket should be re-opened if it is still relevant with a recent version of VirtualBox (5.0.8 or later).
In that case, please do not forgot to attach a VBox.log file of such a VM session. Please attach the raw file. If the file is too big to be attached, compress it.
Screenshot and VB log file