Bug 302211 - f8test2 xen guest will not boot after install
Summary: f8test2 xen guest will not boot after install
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel-xen
Version: 8
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Eduardo Habkost
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-09-23 15:07 UTC by Michael Carney
Modified: 2009-12-14 20:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-09 04:54:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
guest boot text w/ debug + initcall_debug on (19.62 KB, text/plain)
2007-09-23 15:07 UTC, Michael Carney
no flags Details

Description Michael Carney 2007-09-23 15:07:34 UTC
Description of problem: After a successful install of f8test2 on a F7 dom0, the
guest fails to boot.


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


How reproducible: Always.


Steps to Reproduce:
1. Install a f8test2 guest on a F7 dom0 using virt* tools w/ DistroManager.py
hack (/Fedora -> /Packages)
2. Reboot after successful installation.
3. Guest will not boot w/ nash SEG fault.
  
Actual results:
...
xen-vbd: registered block device major 202
blkfront: xvda: barriers enabled
 xvda: xvda1 xvda2 xvda3 xvda4 < xvda5 xvda6 xvda7 xvda8 >
nash received SIGSEGV!  Backtrace (7):
/bin/nash[0x8052fcd]
[0xdb4440]
/bin/nash[0x80522b6]
/bin/nash[0x8052e35]
/bin/nash[0x805352c]
/lib/i686/nosegneg/libc.so.6(__libc_start_main+0xe0)[0x6ae0f0]
/bin/nash[0x804ae31]

Expected results:
A booting guest.

Additional info: Guest booted with debug and initcall_debug turned on attached.

Comment 1 Michael Carney 2007-09-23 15:07:34 UTC
Created attachment 203471 [details]
guest boot text w/ debug + initcall_debug on

Comment 2 Michael Carney 2007-10-11 14:01:41 UTC
Seems to work ok in F8test3...


Comment 3 Bug Zapper 2008-11-26 07:50:35 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2009-01-09 04:54:29 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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