|
Bugzilla – Full Text Bug Listing |
| Summary: | Factory doesn't boot in VirtualBox anymore | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Peter Poeml <poeml> |
| Component: | YaST2 | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Blocker | ||
| Priority: | P5 - None | CC: | chrubis, jdd, mantel, schoppehaller |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | VirtualBox log, with a successful log snippet added for comparison | ||
|
Description
Peter Poeml
2009-03-03 08:40:53 UTC
the initrd is gzipped cpio since about forever. Does failsafe boot? No, it didn't work either. 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 note: the pae kernel, installed from YaST, boots (with the correct option in virtualbox) 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... ;)
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) Created attachment 277169 [details]
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.
Well not sure where this problem came from, lets yast people have a look. 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? if you want. But what can I do? my instal boots, now :-( 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? seems to work, now, don't know why. But it's obviously a boot problem, so grub or kernel related jdd I'll close the bug as the reported issue seems to be gone. |