Bug 462021
| Summary: | vnc fails to connect to qemu-kvm started manually | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kevin Constantine <kevin.constantine> |
| Component: | qemu | Assignee: | David Woodhouse <dwmw2> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | CC: | berrange, clalance, dwmw2, gilboad, katzj, virt-maint |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-07-14 16:56:31 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: | |||
|
Description
Kevin Constantine
2008-09-11 23:18:55 UTC
libvirt does not manage virtual machines you start directly. If you want virtual machines to be seen & managed by libvirt, then you must start them with libvirt The fact that libvirt doesn't see the domain doesn't really concern me. The crux of my question/bug report is that qemu-kvm doesn't seem to connect the guest domain back to the host domain's vnc socket. I see that the host is listening on the proper vnc port, but connections from a client hang. Is libvirt responsible for hooking the guest to the host? or is that done by kvm? Thanks! I believe this bug should filed against qemu itself (and not against kvm/qemu-kvm), hence I report it. I'm seeing the same under F9, using both qemu and qemu-kvm. (both running on x86_64 hardware). First connect to vnc socket works just. However, once you disconnect from the VNC, subsequent reconnect attempt usually time out. I'll attempt to get a strace once I hit this bug again. - Gilboa s/hence I report it/hence I reopened the bug/g - Gilboa This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |