Bug 149014 - xend stops responding after xm destroy
Summary: xend stops responding after xm destroy
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xen
Version: 3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Rik van Riel
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-02-17 22:18 UTC by Robin Green
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-09-05 07:39:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Robin Green 2005-02-17 22:18:03 UTC
Description of problem:
If I destroy a domain with xm destroy, a subsequent xm list command will hang.
Sometimes it is necessary to use xm destroy, because xm shutdown doesn't always
work.

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

How reproducible:
Often

Steps to Reproduce:
1. xm create -c foo
2. CTRL+] to detach from domain foo
3. xm destroy foo
4. xm list
  
Actual results:
xm list hangs

Expected results:
xm list should list domains

Additional info:
All kernels used are the latest kernels (2.6.10-1.1142_FC4) from fedora
development, with my floating-point-workaround patch applied.

Sometimes, service xend restart doesn't make xend work again either, so I have
to reboot the machine.

Comment 1 Rik van Riel 2005-02-23 21:55:12 UTC
I have seen this bug too, but it seems to have gone away with
xen-2-20050222, which should be in rawhide in a few days.  Please move
this bug back to ASSIGNED state if it pops up again in the future.


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