Description of problem: I have add "on_crash = rename-restart" to the pv guest config file. After guest crashed, restart xend will causes losing running guest. Version-Release number of selected component (if applicable): kernel-xen-2.6.18-231.el5 xen-3.0.3-117.el5 How reproducible: 100% Steps to Reproduce: 1.create a PV guest with "on_crash = rename-restart" [host]#xm cr pv-32-rhel5u5.cfg 2.using "xm list" to watch guest state: [host]# xm li Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 32768 32 r----- 859.7 xen-pv-guest-rhel5 4 511 4 -b---- 22.0 3.vnc to guest, make it crash. [guest]# echo c > /proc/sysrq-trigger 4.Using "xm list" to watch guest state: [host]# xm li Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 32768 32 r----- 944.1 xen-pv-guest-rhel5 5 511 4 -b---- 20.0 xen-pv-guest-rhel5-1 4 511 1 ----c- 41.0 5.Restart xend. [host]# service xend restart 6.Using "xm list" to watch guest state: [host]# xm li Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 32768 32 r----- 1013.0 xen-pv-guest-rhel5 4 511 1 ----c- 41.0 Actual results: 1. After step6, running guest is disappear. Expected results: 1. After step6, running guest should work well. Additional info:
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