Bug 513265 - virsh list may not output HVM domains
Summary: virsh list may not output HVM domains
Keywords:
Status: CLOSED DUPLICATE of bug 513604
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xen
Version: 5.4
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: 5.5
Assignee: Jiri Denemark
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-22 18:24 UTC by Marc Milgram
Modified: 2010-04-08 16:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-18 06:45:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Suggested patch (762 bytes, patch)
2009-07-22 18:24 UTC, Marc Milgram
no flags Details | Diff

Description Marc Milgram 2009-07-22 18:24:14 UTC
Created attachment 354763 [details]
Suggested patch

Description of problem:
 The `virsh list' command may not output running HVM domains after they reboot.

Version-Release number of selected component (if applicable):
 Kernel Version: 2.6.18-155.el5xen
 Related Package Version: xen-3.0.3-88.el5

How reproducible:
 1/50

Steps to Reproduce:
1. Create an HVM domain
2. Reboot it
3. Run `virsh list'
  
Actual results:
  Id Name                 State
 ----------------------------------
   0 Domain-0             running

Expected results:
  Id Name                 State
 ----------------------------------
   0 Domain-0             running
 297 vm1                  running


Additional info:
 This issue was fixed by the following changeset:
   19509: xend: fix leak of /local/domain/* in xenstore
   http://xenbits.xensource.com/xen-unstable.hg?rev/71077a0fd289

Comment 1 Jiri Denemark 2009-09-15 14:12:48 UTC
This issue looks very similar to bug 513604 and the same applies to the associated ITs. Could you confirm that? You can use virttest1 packages at http://people.redhat.com/jdenemar/xen/ to test it.

Thanks.

Comment 2 Marc Milgram 2009-09-17 19:43:28 UTC
Yes, this is a dup of bug 513604.  I was not able to reproduce the bug with the virttest1 packages.

Thanks Jiri.

Comment 3 Chris Lalancette 2009-09-18 06:45:09 UTC

*** This bug has been marked as a duplicate of bug 513604 ***

Comment 4 Paolo Bonzini 2010-04-08 15:47:05 UTC
This bug was closed during 5.5 development and it's being removed from the internal tracking bugs (which are now for 5.6).


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