Bug 1353528
Summary: | virt-manager can hang if remote host goes down | ||
---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | Dr. David Alan Gilbert <dgilbert> |
Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | berrange, crobinso, dgilbert, dhgutteridge, gscrivan, rbalakri, victortoso, virt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-28 20:30:27 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: |
Description
Dr. David Alan Gilbert
2016-07-07 11:41:01 UTC
Likely some hang to do with the remote host going down... I'd think the libvirt connection KeepAlive APIs would break things off if it hangs, but maybe there's some way we can get stuck, I'll need to try to reproduce I can intermittently reproduce this issue with a local VM that has a habit of hanging. Sometimes this also causes virt-manager to become unresponsive indefinitely; I cannot use it to control the host, so I have to kill the underlying qemu process. (This is with virt-manager 1.4.1 on Fedora 25.) I don't have any sample logs on hand, nor have I attached a gdb session. I did try to profile the qemu process kernel side, since this is the underlying cause, but haven't come up with anything useful. (Frankly, of late, I've avoided that particular VM image in frustration.) (I meant to write "I cannot use it to control the VM", of course. Ahem.) Hi David, this could be a deadlock in spice-gtk which has a fix in the mailing list [0]. I notice that you are on f24, could you check using spice-gtk from this scratch build works for you? https://koji.fedoraproject.org/koji/taskinfo?taskID=20070259 If one wants to give it a try on f25 -> f27, should be doable with this other scratch-build: https://koji.fedoraproject.org/koji/taskinfo?taskID=20070247 [0] https://lists.freedesktop.org/archives/spice-devel/2017-June/038343.html (In reply to Victor Toso from comment #4) > Hi David, this could be a deadlock in spice-gtk which has a fix in the > mailing list [0]. I notice that you are on f24, could you check using > spice-gtk from this scratch build works for you? Sorry for the delay; I hadn't had time to look at this until recently. I'm running Fedora 26 now, with spice-gtk 0.34, which I see from the Git change log has the referenced fix included. I haven't been able to duplicate virt-manager hangs since I began testing earlier this week. (I have still been able to duplicate the VM freezing, though that happens less frequently and requires more time with equivalent loads, which I chalk up to a much newer version of QEMU.) Since last report makes it sound like virt-manager hangs are fixed, I'm closing this. If there's still issues, please open new bugs against spice-gtk |