[Bug 481354] New: Factory doesn't boot in VirtualBox anymore
https://bugzilla.novell.com/show_bug.cgi?id=481354 Summary: Factory doesn't boot in VirtualBox anymore Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Blocker Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: poeml@novell.com QAContact: qa@suse.de Found By: --- Every Factory image upgraded yesterday or the day before ceased to work for me, and the current images out there fail in the same way. They all stop with a black screen at the time where the kernel should be loading (or starting to be loaded maybe). VirtualBox aborts and says "aborted". It doesn't seem to be a quirk in VirtualBox, and not a bug in the handling of the snapshots I had accumulated (which was my first suspicion). It didn't change anything to start with a fresh harddisk without snapshots. Other images I have around (FreeBSD, Ubuntu, ArchLinux, 11.1) work. I played with VirtualBox config options, to no avail. Reinstalling the bootloader didn't help. I booted a rescue system, recreated the initial ramdisk, and noticed that mkinitrd includes about 87 modules into the initial ramdisk, which seems weird. (It gives an initrd 13 megs in size, uncompressed). I wondered why the initrd is just a simple gzipped cpio archive, I had expected something fancier, but maybe this is the way things are done today. I later was able to boot the system with an 11.1 kernel, with an initrd created with 11.1 mkinitrd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=481354 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=481354#c1 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |poeml@novell.com --- Comment #1 from Stephan Kulow <coolo@novell.com> 2009-03-03 03:57:51 MST --- the initrd is gzipped cpio since about forever. Does failsafe boot? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=481354 User poeml@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=481354#c2 Peter Poeml <poeml@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|poeml@novell.com | --- Comment #2 from Peter Poeml <poeml@novell.com> 2009-03-03 04:00:57 MST --- No, it didn't work either. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=481354 User jdd@dodin.org added comment https://bugzilla.novell.com/show_bug.cgi?id=481354#c3 Jean-Daniel Dodin <jdd@dodin.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdd@dodin.org --- Comment #3 from Jean-Daniel Dodin <jdd@dodin.org> 2009-03-03 10:53:41 MST --- same here, and still no other kernel (zypper up says: nothing to do). I could boot with the only kernel I found on the factory cd, that is the one named vmlinuz-xen and it's initrd-xen many time ago there where kernel problems I though now updates could let a default kernel stay. The crash occurs very early in the process. I can boot with the grub console, it crashes at "probing EDD", nearly immediatly when pressing boot -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=481354 User jdd@dodin.org added comment https://bugzilla.novell.com/show_bug.cgi?id=481354#c4 --- Comment #4 from Jean-Daniel Dodin <jdd@dodin.org> 2009-03-03 11:12:33 MST --- note: the pae kernel, installed from YaST, boots (with the correct option in virtualbox) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=481354 User poeml@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=481354#c5 --- Comment #5 from Peter Poeml <poeml@novell.com> 2009-03-03 11:57:49 MST --- Interesting - I had tried the VirtualBox pae option, but not the pae kernel (I had only one kernel on the system unfortunately). I can confirm the pae kernel works here, too (with the option). (Thanks for finding out!)
I though now updates could let a default kernel stay
"could" is the magic word, it is now *possible*, but it's not actually *done*. Factory expects from its users that they want to spend considerable time in training their recovery abilities, or that kernel updates never break, which is both rather unlikely IMO... ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=481354 User jdd@dodin.org added comment https://bugzilla.novell.com/show_bug.cgi?id=481354#c6 --- Comment #6 from Jean-Daniel Dodin <jdd@dodin.org> 2009-03-03 12:44:07 MST --- I found the pae kernel seraching any other kernel with YaST. I noticed that even if YaST installed the new kernel, it didn't cnange the default (the new kernel is install together with the old one) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=481354 User poeml@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=481354#c7 --- Comment #7 from Peter Poeml <poeml@novell.com> 2009-03-04 14:42:10 MST --- Created an attachment (id=277169) --> (https://bugzilla.novell.com/attachment.cgi?id=277169) VirtualBox log, with a successful log snippet added for comparison It just occured to me that VirtualBox has a log file. What it logs looks rather unconspicious to me, though. With the PAE kernel booting, this isn't a blocker for me anymore. But maybe for other people. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=481354 User chrubis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=481354#c8 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chrubis@novell.com Component|Kernel |YaST2 AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | QAContact|qa@suse.de |jsrain@novell.com --- Comment #8 from Cyril Hrubis <chrubis@novell.com> 2009-03-19 09:37:51 MST --- Well not sure where this problem came from, lets yast people have a look. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=481354 User schoppehaller@vr-web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=481354#c9 --- Comment #9 from Daniel Fuhrmann <schoppehaller@vr-web.de> 2009-03-19 09:56:52 MST --- The newest update (netinstallcd build 035) solved this problem for me. I could update my installation with the netiso. In the factory-list this thread was also solved. Do you still want to search why this happend? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=481354 User jdd@dodin.org added comment https://bugzilla.novell.com/show_bug.cgi?id=481354#c10 --- Comment #10 from Jean-Daniel Dodin <jdd@dodin.org> 2009-03-19 11:14:40 MST --- if you want. But what can I do? my instal boots, now :-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=481354 User mantel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=481354#c11 Hubert Mantel <mantel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |mantel@novell.com Info Provider| |poeml@novell.com --- Comment #11 from Hubert Mantel <mantel@novell.com> 2009-03-23 06:28:48 MST --- If one kernel works and another not, this sounds like a kernel issue to me, not a YaST bug. But judging from comments #9 and #10, it seems the problem is already fixed. Can you confirm that? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=481354 User jdd@dodin.org added comment https://bugzilla.novell.com/show_bug.cgi?id=481354#c12 --- Comment #12 from Jean-Daniel Dodin <jdd@dodin.org> 2009-03-23 12:47:31 MST --- seems to work, now, don't know why. But it's obviously a boot problem, so grub or kernel related jdd -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=481354 User snwint@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=481354#c13 Steffen Winterfeldt <snwint@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|poeml@novell.com | Resolution| |FIXED --- Comment #13 from Steffen Winterfeldt <snwint@novell.com> 2009-04-01 04:32:07 MDT --- I'll close the bug as the reported issue seems to be gone. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com