VirtualBox

Ticket #2739 (closed defect: fixed)

Opened 5 years ago

Last modified 4 years ago

Fedora 10 (usually) panics on VBox 2.0.6 (under WinXP) - intermittent bug

Reported by: Rob Owned by:
Priority: critical Component: other
Version: VirtualBox 2.0.6 Keywords:
Cc: Guest type: other
Host type: other

Description

Fedora 10 usually (but not always) panics and will not boot when installed on VirtualBox 2.0.6 (running under WinXP), this is an intermittent bug. Usually it fails, rarely it works.

I have searched this website for other Tickets and the Forums for similar issues. I found none that were "identical". I searched the Internet and found a few other people had "similar" troubles.

I downloaded  http://fedora.mirror.iweb.ca/releases/10/Fedora/i386/iso/Fedora-10-i386-DVD.iso from  http://fedora.mirror.iweb.ca/releases/10/Fedora/i386/iso/ .

I have installed F10 previously (and had everything working well) by following these tips:

Problem with Fedora 10 on VirtualBox  http://www.my-guides.net/en/component/option,com_smf/Itemid,46/topic,94.msg142/topicseen,1/

Plymouth Graphical Boot  http://www.my-guides.net/en/content/view/125/26/1/12/#plymouth

Other people have "similar" but not "identical" complaints:

kernel panic when trying to boot Fedora 10 live in VirtualBox  http://linux.derkeiler.com/Mailing-Lists/Fedora/2008-09/msg02296.html

Fedora 10 fails to install  http://www.virtualbox.org/ticket/2680

The Bug in this report is shown in the attached screenshot. The message is: "Kernel panic - not syncing: Fatal exception in interrupt" .

_Sometimes_ when there is a problem booting I see a 'Debug Trace' then keeps scrolling on the screen and does not terminate with a message (at least not within 20 minutes), it just keeps 'tracing' and does not print the "Kernel panic" message.

_Sometimes_ Fedora 10 will start normally and work properly.

_Sometimes_ Fedora 10 will get as far as the "Graphical Bootscreen" completion but will not start X11 and the Gnome Desktop.

I can (_sometimes_) fix this Bug by toggling the "Extended Features" "Enable ACPI" to ON, booting and it will work (or fail), and then turning it OFF, booting and it will work (or fail).

I find that leaving the "Extended Features" "Enable ACPI" turned OFF is necessary for Installation. I only turn it ON, then OFF, to 'toggle it' and attempt to cause Fedora 10 to 'fix itself' and boot.

Fedora 10 _seems_ to be able to boot correctly, more often, if the "Initial Updates" are NOT downloaded (there is a popup prompting you to update _after_ you install from the DVD .iso) and once they are downloaded the _chance_ that it will boot is greatly reduced.

_Prior_ to downloading and installing the "Initial Updates" you need to leave the "Enable ACPI" turned OFF all the time or you will get the endless error messages (and rarely they will end with the "Kernel panic" message).

Thanks, Rob

Attachments

Fedora10-11-oops.gif Download (18.9 KB) - added by Rob 5 years ago.
Fedora 10 Kernel panic when booting
var_log_messages.gz Download (40.9 KB) - added by Rob 5 years ago.
/var/log/messages - After getting it to boot, here is my messages log - not helpful?
var_log_anaconda.syslog.gz Download (7.8 KB) - added by Rob 5 years ago.
/var/log/anaconda.syslog - After getting it to boot, here is my anaconda.syslog - helpful .

Change History

Changed 5 years ago by Rob

Fedora 10 Kernel panic when booting

Changed 5 years ago by Rob

/var/log/messages - After getting it to boot, here is my messages log - not helpful?

Changed 5 years ago by Rob

/var/log/anaconda.syslog - After getting it to boot, here is my anaconda.syslog - helpful .

comment:1 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Please reopen if this problem persists with VirtualBox 2.2.2.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use