Bug 192969 - pygrub crashes if grub.conf has no default=N line
Summary: pygrub crashes if grub.conf has no default=N line
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xen   
(Show other bugs)
Version: 5
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 192971
TreeView+ depends on / blocked
 
Reported: 2006-05-24 15:40 UTC by Rik van Riel
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version: 5.0.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-03-27 02:52:42 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Rik van Riel 2006-05-24 15:40:03 UTC
Description of problem:

# xm create -c rhel4pv
Using config file "/etc/xen/rhel4pv".
Traceback (most recent call last):
  File "/usr/bin/pygrub", line 258, in ?
    curses.wrapper(run_main)
  File "/usr/lib/python2.4/curses/wrapper.py", line 44, in wrapper
    return func(stdscr, *args, **kwds)
  File "/usr/bin/pygrub", line 214, in run_main
    sel = main(cf)
  File "/usr/bin/pygrub", line 164, in main
    selected = cf.default
  File "/usr/lib/python2.4/site-packages/grub/GrubConf.py", line 193, in
_get_default
    return self._default
AttributeError: 'GrubConfigFile' object has no attribute '_default'
Error: Boot loader didn't return any data!

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

xen-3.0.2-0.FC5.1

Steps to reproduce:
1. install fully virtualized guest
2. install paravirtualized kernel inside it
3. remove default=1 line from grub.conf
4. try to boot the domain in paravirt, get above error message
5. boot the domain in HVM mode, normal grub works fine
6. edit grub.conf add back default=0 line
7. now pygrub is happy again

Comment 2 Jeremy Katz 2007-03-27 02:52:42 UTC
This was fixed long ago


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