Bug 181750

Summary:	enabling xen group should still install non-xen kernel
Product:	[Fedora] Fedora	Reporter:	Alexandre Oliva <oliva>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-02-20 20:28:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alexandre Oliva 2006-02-16 06:49:00 UTC

Description of problem:
If you select the xen package group, you end up without a non-xen kernel to boot
from.  I don't think this is appropriate; I'd rather get both to choose from,
lest the xen kernel not be able to boot at all, while a subsequent update might.

I'm not even sure the xen-hypervisor kernel should boot up by default.

Version-Release number of selected component (if applicable):
anaconda-10.92.4-1

How reproducible:
Every time

Steps to Reproduce:
1.Select the `xen' package group in the installer
2.Install
3.Try another install, with kickstart, and request the `kernel' package
  
Actual results:
After 2., the non-xen kernel was not even installed.  After 3, it is, but is not
the default.

Expected results:
Non-xen kernel should probably be installed, and should still be the default
unless requested otherwise.

Additional info:

Comment 1 Jeremy Katz 2006-02-20 20:28:44 UTC


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