Bug 112751 - yast/bootload adds wrong XEN entry when asked for new proposal
Summary: yast/bootload adds wrong XEN entry when asked for new proposal
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 2
Hardware: Other SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-24 16:05 UTC by Michael Scherer
Modified: 2005-08-25 10:41 UTC (History)
0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Scherer 2005-08-24 16:05:39 UTC 
After installation of beta2 (incl. xen-tools + kernel) no bootentry at all was
found in grub/menu.lst.
Starting "yast bootloader" and do "Propose new configuration" adds the following
XEN entry:

###Don't change this comment - YaST2 identifier: Original name: xen###
title S10-B2 [XEN]
    root (hd0,5)
    kernel /boot/xen.gz dom0_mem=458752
    module /boot/vmlinuz-xen root=/dev/hda6 selinux=0    resume=/dev/hda7 
splash=silent showopts
    module /boot/initrd

Following entries are wrong:
1.) kernel -> /boot/xen-3.gz
2.) module -> /boot/initrd-xen
Comment 1 Martin Lasarsch 2005-08-25 10:41:33 UTC 
looks like its fixed in beta3, i have: 
 
kernel xen.gz (link to xen-3.0.gz -> xen-3.0_06315-2.gz) 
module /boot/initrd-xen (link to initrd-2.6.13-rc6-git13-4-xen)