Bug 212299 - The Domain-0 was hang after the VTI-Domain panic
Summary: The Domain-0 was hang after the VTI-Domain panic
Alias: None
Product: Fedora
Classification: Fedora
Component: xen
Version: 6
Hardware: ia64
OS: Linux
Target Milestone: ---
Assignee: Aron Griffis
QA Contact: Martin Jenner
Depends On:
TreeView+ depends on / blocked
Reported: 2006-10-26 04:58 UTC by yoshiro fujita
Modified: 2008-02-26 23:34 UTC (History)
5 users (show)

Clone Of:
Last Closed: 2008-02-26 23:34:29 UTC

Attachments (Terms of Use)
xen log (115.53 KB, application/octet-stream)
2006-10-26 05:10 UTC, yoshiro fujita
no flags Details

Description yoshiro fujita 2006-10-26 04:58:18 UTC
Description of problem:
The VTI-Domain is in panic when create/shutdown testing.
The Domain-0 was hang after the behavior above happened some times.

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

How reproducible:

Steps to Reproduce:
1.alternate between create/shutdown VTI-domain.
Actual results:
The Domain-0 was hang after the VTI-Domain panic.

Expected results:
both domains are stable.

Additional info:
see attached log.

Comment 1 yoshiro fujita 2006-10-26 05:10:09 UTC
Created attachment 139434 [details]
xen log

Comment 2 Matthew Miller 2007-04-06 18:10:27 UTC
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.

[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]

Comment 3 Red Hat Bugzilla 2007-07-25 00:01:11 UTC
change QA contact

Comment 4 Chris Lalancette 2008-02-26 23:34:29 UTC
This report targets FC6, which is now end-of-life.

Please re-test against Fedora 7 or later, and if the issue persists, open a new bug.


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