Bug 1598436
| Summary: | AttachDeviceFlags failed, killed by SIGSEGV (core dumped) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | amadev <m> | ||||||||
| Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | |||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | unspecified | CC: | laine, libvirt-maint, m, rbalakri | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2018-07-10 12:21:37 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
amadev
2018-07-05 13:10:26 UTC
Created attachment 1456765 [details]
strace
Created attachment 1456766 [details]
nova-compute.log
I see the error "libvirtError: End of file while reading data: Input/output error", but neither from libvirtd log nor strace log I could not find out what file libvirt is reading and why it is failed. (In reply to amadev from comment #3) > I see the error "libvirtError: End of file while reading data: Input/output > error", but neither from libvirtd log nor strace log I could not find out > what file libvirt is reading and why it is failed. Usually that just means that the qemu process has terminated while libvirt is still waiting for input on its QMP socket. A couple of comments: 1) we're 5 months beyond libvirt-4.0.0 upstream, so if you're wanting upstream to look into this bug, you should try to install the latest upstream libvirt (4.5.0 was just released) and see if the prolem persists. 2) since you're comfortable with strace, maybe you could attach gdb to the libvirtd process (after installing debuginfo, however that's done in Ubuntu - the following exercise is pointless without full debuginfo for all the files in libvirtd), perform the operation that triggers the segv, then when gdb breaks, enter the command "bt" and attach the results to this BZ. That output would be much more helpful than the strace output or libvirt debug logs, since it will show the exact line where the segv occurred. Laine, 1) Yes, update helped. Even more, I compiled libvirt from git sources v4.0.0 and problem disappeared. Probably it's related to some packaging issue. Sorry for distraction. 2) I tried gdb but it showed "No stack" on those binaries. |