Opened 9 years ago

Closed 9 years ago

#5992 closed bug (fixed)

Virtualbox 3.1.8: Kernel Panic while installing Haiku

Reported by: Steffo Owned by: axeld
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/alpha2
Keywords: kernel panic, virtualbox Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

I tried two times to install Haiku R1 alpha2. The first time I've got a kernel panik while installing Haiku, the second time an unknown problem on the verge of finishing Haiku installation.

Enclosed you'll find two screenshot.

I'm using an iMac 24" Core2Duo 2.8 GHz (early 2008), ATI Radeon 2600 Pro.

Attachments (3)

kernel_panic.png (101.9 KB ) - added by Steffo 9 years ago.
unknown_problem.png (106.3 KB ) - added by Steffo 9 years ago.
Segment_Violation.png (119.7 KB ) - added by Steffo 9 years ago.

Download all attachments as: .zip

Change History (12)

by Steffo, 9 years ago

Attachment: kernel_panic.png added

by Steffo, 9 years ago

Attachment: unknown_problem.png added

comment:1 by Steffo, 9 years ago

Keywords: kernel panic virtualbox added

I tried two times to install Haiku R1 alpha2. The first time I've got a kernel panik while installing Haiku, the second time I've got an unknown problem on the verge of finishing Haiku installation.

Enclosed you'll find two screenshot.

I'm using an iMac 24" Core2Duo 2.8 GHz (early 2008), ATI Radeon 2600 Pro.

in reply to:  1 ; comment:2 by andreasf, 9 years ago

Platform: x86-64x86

Replying to Steffo:

the second time I've got an unknown problem on the verge of finishing Haiku installation.

The "unknown problem" is a Segment violation. If it happens again, the stack trace (bt) is usually of interest.

in reply to:  2 ; comment:3 by Steffo, 9 years ago

Replying to andreasf:

The "unknown problem" is a Segment violation. If it happens again, the stack trace (bt) is usually of interest.

How do I get the stack trace?

in reply to:  3 comment:4 by tangobravo, 9 years ago

Replying to Steffo:

Replying to andreasf:

The "unknown problem" is a Segment violation. If it happens again, the stack trace (bt) is usually of interest.

How do I get the stack trace?

Type "bt" (without the quotes) into the terminal window (after the "(gdb)" prompt) and press enter.

by Steffo, 9 years ago

Attachment: Segment_Violation.png added

comment:5 by Steffo, 9 years ago

OK, I attached a new screenshot with the stack trace.

comment:6 by stippi, 9 years ago

Thanks! The first problem could be a duplicate, I think it's a problem with the ATA bus_manager. Perhaps a problem with sharing interrupts. The second problem is pretty strange, never seen something like it myself and don't really know where that could be coming from.

comment:7 by Coldfirex, 9 years ago

Still a problem with a recent Haiku build and updated VirtualBox?

in reply to:  7 comment:8 by Steffo, 9 years ago

It works now with VirtualBox 4.0!

Replying to Coldfirex:

Still a problem with a recent Haiku build and updated VirtualBox?

comment:9 by korli, 9 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.