Mailinglist Archive: opensuse-bugs (7304 mails)
| < Previous | Next > |
[Bug 481354] New: Factory doesn't boot in VirtualBox anymore
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Tue, 3 Mar 2009 01:40:55 -0700 (MST)
- Message-id: <bug-481354-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
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@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: poeml@xxxxxxxxxx
QAContact: qa@xxxxxxx
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.
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@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: poeml@xxxxxxxxxx
QAContact: qa@xxxxxxx
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.
| < Previous | Next > |