Bug 615187
| Summary: | Call trace in rhel6 PV guest after doing "xm save" failure. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | XinSun <xinsun> | ||||||||
| Component: | kernel | Assignee: | Xen Maintainance List <xen-maint> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 6.0 | CC: | drjones, gyang, leiwang, llim, minovotn, mshao, pbonzini, xen-maint, yuzhang | ||||||||
| Target Milestone: | rc | Keywords: | TestOnly | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2011-04-20 12:36:19 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: | 497080 | ||||||||||
| Bug Blocks: | 523117 | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 432303 [details]
xend.log
Created attachment 432305 [details] rhel6-pv-latest rhel6 tree: http://download.englab.nay.redhat.com/pub/rhel/rel-eng/RHEL6.0-20100707.4/6.0/Server/i386/ question to reporter or xen user space guys: do RHEL5 guests recover from failed saves fine? I try this on rhel5 pv guest, when doing save failure on rhel5.5 pv guest, this guest can run normally and I can do other operation in this guest. Retest it again, this issue occurs on i386 platfrom. Andrew: Yeah, now it does. From the xend.log I was seeing "errno 28" which is failure because of low disk space which is change because for me I saw "errno 0" for RHEL-5 i386 guest. Nevertheless, the RHEL-5 i386 guest I tested was working successfully when resumed from the failed save (at least according to my testing). This was tested on x86_64 RHEL-5 host. Also, the "arch/x86/xen/enlighten.c:169" in the call trace is present only in the recent pv-ops kernels like you told me... Could what's present on line 169 in this file of RHEL-6 kernel then? Thanks, Michal It looks like we may need to fix this in the rhel6 kernel, possible also a change in the rhel5 HV. In any respect it's too late for 6.0 to fix this as it's an error path and not a critical blocker. Moving to kernel component and slating for 6.1. Drew This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release. This would be fixed by suspend cancellation, we are not going to fix it in the guest. *** This bug has been marked as a duplicate of bug 618569 *** |
Created attachment 432302 [details] rhel6-call_trace.txt Description of problem: After doing rhel6 pv guest save failure, rhel6 pv guest will call trace and hang. Version-Release number of selected component (if applicable): xen-3.0.3-114.el5 kernel-xen-2.6.18-206.el5 How reproducible: Always Steps to Reproduce: 1.Create the rhel6 pv guest: xm create rhel6-pv-latest -c 2.save this guest to small disk: xm save rhel6-pv-latest /mnt/save_fail Actual results: There is call trace in rhel6 PV guest and guest will hang. Expected results: Rhel6 PV guest will run normal and you can operate this guest all the time. Additional info: Please see the attachment: rhel6_call_trace.txt xend.log rhel6-pv-latest.txt (guest config file)