Bug 652150
| Summary: | Restart xend causes losing running guest after crash with "on_crash=rename-restart" | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | YangGuang <gyang> | ||||||||
| Component: | xen | Assignee: | Miroslav Rezanina <mrezanin> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 5.6 | CC: | jzheng, leiwang, mrezanin, mshao, xen-maint, yuzhou | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | xen-3.0.3-126.el5 | Doc Type: | Bug Fix | ||||||||
| Doc Text: |
Previously, when the "rename-restart" option was set as a reaction to a guest termination and the xend daemon was restarted after the guest crashed, xend lost track of the new guest instance. This bug has been fixed, and all guests are now visible via xend after the daemon restart.
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2011-07-21 09:15:43 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: | |||||||||||
| Bug Blocks: | 514499 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
YangGuang
2010-11-11 06:55:51 UTC
Created attachment 459665 [details]
configuration file of pv guest
Created attachment 459729 [details]
dmesg info
Created attachment 459730 [details]
xend.log
Testing shows that rename is not properly propagated to hv so after restart, all rename data are only in xenstore but xend reload old infos from hv. Fix built into xen-3.0.3-126.el5 reproduced the bug on xen-3.0.3-117.el5 and verified the bug on xen-3.0.3-126.el5. on xen-3.0.3-126.el5 Steps: 1.create a PV guest with "on_crash = rename-restart" 2.vnc to guest, make it crash. 3. Using "xm list" to watch guest state: # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 5929 4 r----- 41.0 RHEL6.1-64-PV 2 1023 1 -b---- 15.2 RHEL6.1-64-PV-1 1 1023 1 ----c- 12.2 4.Restart xend. 5. check the guest state again: # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 5929 4 r----- 41.7 RHEL6.1-64-PV 2 1023 1 -b---- 15.2 RHEL6.1-64-PV-1 1 1023 1 ----c- 12.2 So Change the status to VERIFIED.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Previously, when the "rename-restart" option was set as a reaction to a guest termination and the xend daemon was restarted after the guest crashed, xend lost track of the new guest instance. This bug has been fixed, and all guests are now visible via xend after the daemon restart.
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/RHBA-2011-1070.html 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/RHBA-2011-1070.html |