Bug 377126 - Current STABLE kernel doesn't boot in Virtualbox
Summary: Current STABLE kernel doesn't boot in Virtualbox
Status: RESOLVED DUPLICATE of bug 371997
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Factory
Hardware: i686 Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-04 10:31 UTC by Bernhard Walle
Modified: 2008-04-20 09:26 UTC (History)
0 users

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Oops in Virtualbox (48.23 KB, image/png)
2008-04-04 10:32 UTC, Bernhard Walle
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Walle 2008-04-04 10:31:49 UTC
I use the Virtualbox package from /work/src/done/STABLE (not checked in currently) on a Factory host (2.6.25-rc8-12-default, x86_64). With that configuration I'm unable to boot the test installation image with a 2.6.25-rc7-git2-11-default kernel from /mounts/machcd2/openSUSE-11.0-Alpha3-DVD-i386-Build00Irgendwas-DVD1.iso.

The problem is that the disk detection fails. See the attached screenshot for an oops. From that point the installer hangs.
Comment 1 Bernhard Walle 2008-04-04 10:32:36 UTC
Created attachment 206256 [details]
Oops in Virtualbox
Comment 2 Bernhard Walle 2008-04-04 10:33:36 UTC
I forgot to mention that 2.6.24 with Beta2 works without problems. So I assume a bug in the 2.6.25-rc* kernel.
Comment 3 Greg Kroah-Hartman 2008-04-04 21:26:53 UTC
strlen?  Ugh.  does this also happen with the vanilla 2.6.25-rc kernels we provide?
Comment 4 Bernhard Walle 2008-04-07 09:55:23 UTC
I get exactly the same error in a real machine (adalid.suse.de). So nothing VirtualBox-related.
Comment 5 Bernhard Walle 2008-04-07 17:18:11 UTC
(In reply to comment #3 from Greg Kroah-Hartman)
> does this also happen with the vanilla 2.6.25-rc kernels we provide?

Don't we trust our own patches now? :)

But I cannot test because that happens only in the installation system. I don't know how to build a custom installation system with another kernel (note that I have to rebuild the initrd because of the kernel module) or how to trigger the YaST HW probing code in a normal system.
Comment 6 Forgotten User qMyteedNxa 2008-04-19 23:05:45 UTC
most likely a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=371997
Comment 7 Bernhard Walle 2008-04-20 09:26:56 UTC
Roland, thanks for spotting this!

*** This bug has been marked as a duplicate of bug 371997 ***