Bug 149014

Summary: xend stops responding after xm destroy
Product: [Fedora] Fedora Reporter: Robin Green <greenrd>
Component: xenAssignee: Rik van Riel <riel>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: sundaram
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-05 03:39:35 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Robin Green 2005-02-17 17:18:03 EST
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

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

How reproducible:

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 16:55:12 EST
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.