Bug 525143
Summary: | Domain goes missing from xm list when rebooted | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | RHEL Program Management <pm-rhel> |
Component: | xen | Assignee: | Xen Maintainance List <xen-maint> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | urgent | ||
Version: | 5.4 | CC: | azarembo, berrange, bmason, clalance, drjones, jdenemar, jplans, llim, mmilgram, moshiro, myamazak, pbonzini, pm-eus, tao, xen-maint, xinsun |
Target Milestone: | rc | Keywords: | Regression, ZStream |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | xen-3.0.3-94.el5_4.1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-10-01 17:55:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 513604 | ||
Bug Blocks: |
Description
RHEL Program Management
2009-09-23 14:20:06 UTC
Fix built into xen-3.0.3-94.el5_4.1 Verify this on xen-3.0.3-94.el5_4.1, do follow steps: 1. Create a Fv/Pv domain 2. Reboot the domain by `xm reboot' 3. Wait for booting up the domain 4. Run `xm list' 5. Run 'virsh list --all' Especially, I do above steps on Fv domain and Pv domain for 25 times.Each time I can see this domain in the xm list. So this bug can not be reproduced on xen-3.0.3-94.el5_4.1. Please see the follow info: [root@dhcp-66-82-130 xen]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 3998 2 r----- 71826.0 rhel5u4_ia64_xenfv 31 1047 1 -b---- 72.8 [root@dhcp-66-82-130 xen]# virsh list --all Id Name State ---------------------------------- 0 Domain-0 running 31 rhel5u4_ia64_xenfv idle - fv_rh shut off - v7ia64 shut off So change status to verified. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2009-1472.html |