Hi,
Error: kernel panic - not syncing fatal exception on startup/reboot.
Error happening after completing OLE instation and while rebooting linux server.
Environment:
64-bit Windows 8 laptop.
OLE version: 5.8.
OLE VM template: V31120 ISO file.
VirtualBox version: 4.2.10
Initally when I first bigin OLE installation I got an error as "VT-x/AMD-V hardware acceleration has been enabled, but is not operational. You 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot. "
In response to the above error I have modified the BIOS on my host system to enable "Virtualization technology". Then it enabled me to complete OLE instation. But after completion of the 1. OLE install, 2. Guestadditions and 3. yum update, the linux server reboot is failing with the following error: "kernel panic - not syncing fatal exception". I am stuck here for my peoplesoft installtion.
Note:
1. I have removed guestaddtions from the controller CDE when rebooting was keep failing.
2. Surprisingly once in a while linux server bootsup but as "guestadditions" was removed I am unable to use mouse and hence I am stuck there.
Despite above, primary issue is reboot/start failing.
Besides "kernel panic - not syncing fatal exception" resolution please help me how to add "guestadditoions" back on to Controller CDE from the backup.
appreciate your help.
Thanks espii.
kernel panic - not syncing fatal exception.
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: kernel panic - not syncing fatal exception.
Minimum information needed for assistance
viewtopic.php?f=24&t=48476
viewtopic.php?f=24&t=48476
-
- Posts: 2
- Joined: 2. Apr 2013, 16:29
- Primary OS: MS Windows 7
- VBox Version: OSE Mandriva
- Guest OSses: OLE - Linux
Re: kernel panic - not syncing fatal exception.
Issue resolved:
Go to your virtual machine -> Settings -> System
Then change Chipset from PIIX3 to ICH9 and enable "Enable IO APIC"
After that, your virtual machine will boot without any issue.
Thanks
espii
Go to your virtual machine -> Settings -> System
Then change Chipset from PIIX3 to ICH9 and enable "Enable IO APIC"
After that, your virtual machine will boot without any issue.
Thanks
espii
Re: kernel panic - not syncing fatal exception.
Thanks a ton espii. This resolved my issue
Re: kernel panic - not syncing fatal exception.
hey,
i have an issue regarding installation of kali linux using virtualbox but after i choose graphical intallation or any other method, it always shows me "end kernel panic - not syncing: fatal exception in interrupt"
i am currently using windows 10 32-bit
the VirtualBox version is 5.2.2
and the kali is 32-bit, 2017.3
please help
i have an issue regarding installation of kali linux using virtualbox but after i choose graphical intallation or any other method, it always shows me "end kernel panic - not syncing: fatal exception in interrupt"
i am currently using windows 10 32-bit
the VirtualBox version is 5.2.2
and the kali is 32-bit, 2017.3
please help
-
- Posts: 1
- Joined: 15. Dec 2017, 18:03
Re: kernel panic - not syncing fatal exception.
i have like your probleem !!! did you find the solution pls help me bro and tyruzilla wrote:hey,
i have an issue regarding installation of kali linux using virtualbox but after i choose graphical intallation or any other method, it always shows me "end kernel panic - not syncing: fatal exception in interrupt"
i am currently using windows 10 32-bit
the VirtualBox version is 5.2.2
and the kali is 32-bit, 2017.3
please help
-
- Posts: 1
- Joined: 1. Sep 2018, 05:02
- Primary OS: MS Windows 10
- VBox Version: OSE self-compiled
- Guest OSses: Oracle Linux
- Location: India
Re: kernel panic - not syncing fatal exception.
I'M facing the same issue (Kernal Panice-Not Syncing: Attempted to kill init!)
But this is only when I have started setting a shared storage between two VM Machines.(If I'M removing it it's working, actually here I'M setting the shared storage to practice ASM under RAC Environment).
Could you please help me...!!
Thanks
Sundeep
But this is only when I have started setting a shared storage between two VM Machines.(If I'M removing it it's working, actually here I'M setting the shared storage to practice ASM under RAC Environment).
Could you please help me...!!
Thanks
Sundeep
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: kernel panic - not syncing fatal exception.
Everyone here is a "me too", but no one bothered to read the "Minimum information needed for assistance". Specifically for the VM log file ("VBox.log.zip"), here's what you do:
- Start the VM. Not from a saved or paused state. Clean start.
- Take the steps required to generate/observe the error. Record the error message. EXACTLY. Post a screenshot if you have to.
- Shut down the VM (if it hasn't aborted by itself). Not saved or paused. Completely shut down. If you can't shut it down by normal means, close the VM window and select "Power off".
- Right-click on the VM in the VirtualBox Manager. Select "Show Log..."
- Save it (only the first VBox.log), ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 1
- Joined: 16. Sep 2018, 00:27
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: puppy linux, windows xp, misc BSD implementations
- Location: an island in Canada
Re: kernel panic - not syncing fatal exception.
kernel panic - not syncing: Fatal exception in interrupt.
Originally: Puppy Linux "slacko-6.3.0-32bit" on VirtualBox 5.1.28
Currently: Puppy Linux "slacko-6.3.1-32bit" on VirtualBox 5.2.18
I'd been saving the state for a very long time, and it was working. When I finally shut it down and tried to reboot, it failed.
Updated Virtualbox to 5.2.1 - still failing.
Created a new machine and updated PuppyLinux from 6.3.0 to 6.3.1 - still failing
Tried to change chipset as described above - still failing
Anyone know what do I need to do to make it work?
EDIT: works fine with older Debian (8.3.0 32bit i386) that I had hanging around. It's just Puppy Linux that it's having issues with.
Originally: Puppy Linux "slacko-6.3.0-32bit" on VirtualBox 5.1.28
Currently: Puppy Linux "slacko-6.3.1-32bit" on VirtualBox 5.2.18
I'd been saving the state for a very long time, and it was working. When I finally shut it down and tried to reboot, it failed.
Updated Virtualbox to 5.2.1 - still failing.
Created a new machine and updated PuppyLinux from 6.3.0 to 6.3.1 - still failing
Tried to change chipset as described above - still failing
Anyone know what do I need to do to make it work?
EDIT: works fine with older Debian (8.3.0 32bit i386) that I had hanging around. It's just Puppy Linux that it's having issues with.
- Attachments
-
- Puppy-Kernel-Panic-2018-09-15.zip
- Screenshot of final words, and log after failure.
- (72.19 KiB) Downloaded 214 times
--
Usenet was the both the start and the end of rational discourse on the internet. IMHO of course.
Usenet was the both the start and the end of rational discourse on the internet. IMHO of course.
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: kernel panic - not syncing fatal exception.
I am suspicious of the user of "Linux Other" as the OS version. Yes, I found advice online dating from 2012 to do this, but now is not 2012, and VirtualBox 5.2.18 does not necessarily behave the same way. Unfortunately there doesn't see to be a SlackWare template, and it seems to be a rather unique distro.