https://bugzilla.novell.com/show_bug.cgi?id=380982 User jfehlig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=380982#c372715 Summary: pygrub cannot boot kernel Product: openSUSE 11.0 Version: Alpha 3plus Platform: i686 OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jfehlig@novell.com QAContact: jsrain@novell.com CC: cgriffin@novell.com, lbendixs@novell.com, ijc@hellion.org.uk Depends on: 372715 Found By: --- +++ This bug was initially created as a clone of Bug #372715 +++ pygrub is a bootloader run within the control domain to boot paravirtualised guests. It is part of the xen-tools package. After installation of a SLES10 SP2 beta paravirtualised guest, pygrub is unable to boot it. The reason for this is that the kernel and initrd are put on the 2nd partition by the installer, but the installer does not mark this partition as "active". Since no partition is marked as active, on the next boot pygrub assumes that the kernel and ramdisk are in the first partition. Unfortunately, by default SLES10 SP2 uses that partition for swap space. The fix is for the installer to mark the partition containing the kernel and ramdisk as active. It can do this by writing 0x80 to an offset within the MBR. For partition 1 that offset is 446, for partition 2 it is 462, for partition 3 it is 478, and for partition 4 it is 494. -- 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.