This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours

Bug 229723

Summary: "xm create" ignores pygrub-selected kernel
Product: [Fedora] Fedora Reporter: Stephen Tweedie <sct>
Component: xenAssignee: Daniel Berrange <berrange>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Martin Jenner <mjenner>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: bstein, katzj, triage, xen-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: bzcl34nup
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-06 21:13:18 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:

Description Stephen Tweedie 2007-02-22 17:42:05 EST
Description of problem:
If a user selects a non-default kernel from interactive pygrub on "xm create",
the default always still gets booted.

Version-Release number of selected component (if applicable):
xen-3.0.4-6.fc7

How reproducible:
100%

Steps to Reproduce:
1. xm create a guest
2. select a non-default kernel from the pygrub menu
  
Actual results:
Default kernel runs.

Expected results:
Selected kernel should run.

Additional info:
It looks like pygrub is being run by xend a second time, this time
non-interactively, so that the initially selected options get overwritten.
Comment 1 Red Hat Bugzilla 2007-07-24 20:06:14 EDT
change QA contact
Comment 2 Bug Zapper 2008-04-03 15:14:15 EDT
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
Comment 3 Bug Zapper 2008-05-06 21:13:17 EDT
This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp