| Summary: | Host got call trace when using kexec to start a new kernel in host with kvm guest running on iscsi disk | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Qunfang Zhang <qzhang> |
| Component: | kernel | Assignee: | Red Hat Kernel Manager <kernel-mgr> |
| Status: | CLOSED NOTABUG | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.8 | CC: | gleb, jasowang, juzhang, michen, qcai |
| Target Milestone: | rc | Flags: | gleb:
needinfo+
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-26 08:55:04 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Qunfang Zhang
2011-12-26 06:05:37 UTC
Please test kdump not kexec directly by using a modified kdump.conf with a dump target. We don't support kexec direct reboot. If you tried the above and the problem occurred, please re-open it. (In reply to comment #1) > Please test kdump not kexec directly by using a modified kdump.conf with a dump > target. We don't support kexec direct reboot. We do not support it only on virt or on real HW too? What is the reason we do not support it? It is very useful to quickly reboot machines with very slow BIOS. Let me re-clarify. kexec() syscall is supported but as I said it is hard to get it right manually on different machines due to complicated arguments required, while kdump will take care of those arguments right automatically. The use case you described is not really what customers/partners will use AFAICT, so it is more of a convenience debugging feature for kernel hackers similar to kgdb, kernel-debug variants which is just a lower-priority for engineering resource-wise. But again, if kdump works not kexec directly, then it is likely that it is because of the arguments were not get right. |