Bug 739134 - GRUB 2 has extraneous menu entries after installing Xen
Summary: GRUB 2 has extraneous menu entries after installing Xen
Status: CLOSED DUPLICATE of bug 738085
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-16 15:40 UTC by W. Michael Petullo
Modified: 2011-09-21 02:28 UTC (History)
4 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2011-09-21 02:28:27 UTC


Attachments (Terms of Use)

Description W. Michael Petullo 2011-09-16 15:40:14 UTC
Description of problem:
I have been testing Fedora 16 Beta RC1's ability to boot Linux in Xen Domain 0. I have found that, in the presence of the Xen hypervisor, grub2-mkconfig creates several extraneous menu entries

Version-Release number of selected component (if applicable):
grub2-1.99-6.fc16.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Install Fedora Beta RC1
2. Install Xen
3. Update to grub2-1.99-6.fc16.x86_64
4. Run grub2-mkconfig -o /boot/grub2/grub.cfg
  
Actual results:
When I reboot, I get the following menu entries:

Fedora Linux, with Linux 3.1.0-0.rc6.git0.0.fc16.x86_64
Fedora Linux, with Linux 3.1.0-0.rc6.git0.0.fc16.x86_64 (recovery mode)
Xen 4.1
Xen 4.1.1
Xen syms-4.1.1
Xen xen

The Xen entries use sub-entries, one for regular and one for recovery mode. Xen.4.1 -> Fedora Linux, with Linux 3.1.0-0.rc6.git0.0.fc16.x86_64 boots fine.

Expected results:
The menu should contain:

Fedora Linux, with Linux 3.1.0-0.rc6.git0.0.fc16.x86_64
Fedora Linux, with Linux 3.1.0-0.rc6.git0.0.fc16.x86_64 (recovery mode)
Xen 4.1.1

Additional info:

Comment 1 Fedora Admin XMLRPC Client 2011-09-16 19:08:38 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Jerry Amundson 2011-09-21 02:28:27 UTC

*** This bug has been marked as a duplicate of bug 738085 ***


Note You need to log in before you can comment on or make changes to this bug.