Red Hat Bugzilla – Bug 211621
kernel-xen shows up in a surprising place
Last modified: 2007-11-30 17:07:35 EST
I was trying to install RHEL5-Client as a xen guest, and had to
customize the package list to make sure that the kernel-xen is included.
a) It would be good if anaconda knew that it runs in a xen vm, and automatically
picks the right kernel
b) the kernel-xen package does not show up in "Virtualization" where I looked
for it, but in "Uncategorized/Miscellaneous packages"
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
The kernel-xen package is in comps.xml twice. Once in the "Miscellaneous
Included Packages" group and once in the "Virtualization" group. Jeremy can
explain why this is the case.
(In reply to comment #0)
> a) It would be good if anaconda knew that it runs in a xen vm, and automatically
> picks the right kernel
The right thing does happen here -- if you have a case where it doesn't, please
show me :) But I've done lots of PV installs with the right thing happening...
> b) the kernel-xen package does not show up in "Virtualization" where I looked
> for it, but in "Uncategorized/Miscellaneous packages"
Miscellaneous packages shouldn't even be visible as a group...
(In reply to comment #2)
> The kernel-xen package is in comps.xml twice. Once in the "Miscellaneous
> Included Packages" group and once in the "Virtualization" group. Jeremy can
> explain why this is the case.
It's in the virt group so that if you're installing a dom0 (and thus select that
you want virt), you get the xen kernel installed.
It's in miscallvars because otherwise, you'd have to have a virt installation
key to install. Which isn't what is wanted. The entire existence of
miscallvars is just a hack due to the how and why of RHEL tree composes not
sucking in all the packages and making them available to everyone.
Matthias, can you verify in a recent tree the problems you reported?
When I last tried an install on Tuesday, the tree was not installable due to
anaconda choking on _getNodes or something...
So I couldn't verify it, no.
Can you try again with a more recent tree?
I'd much rather see qa verify this - they are doing tons of installs anyway,
whereas I would have to interrupt my regular duties just for doing a test install...
Moving to NEEDINFO from myself so that I remember to test.
I'm not seeing any oddities with the latest trees (20070118.nightly) kernel-xen
actually isn't even appearing in package selection (being selected behind the
scenes) and the miscellaneous grouping isn't visible in either Client nor Server.