Bug 526900 - Suggestion: host-independent VNC
Summary: Suggestion: host-independent VNC
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virt-manager
Version: unspecified
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Berrangé
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-02 12:52 UTC by jbrackinshaw
Modified: 2010-03-16 17:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-16 19:19:16 UTC
Embargoed:


Attachments (Terms of Use)

Description jbrackinshaw 2009-10-02 12:52:15 UTC
When migrating a guest from one host to another, the VNC connection is dropped.
This is because the VNC connection is tied to the host.

It would be good to allow the vnc console to work during a live
migration, e.g. by broadcasting the vnc session or by sending it to a
management host to which clients connect to.

Comment 1 Cole Robinson 2009-11-16 19:19:16 UTC
This is outside the scope of virt-manager. If you want this behavior, the easiest thing to do would be to set up a VNC server inside the VM. Otherwise I think you would need to file a feature request with upstream qemu, then get the requisite support in libvirt (basically, a LARGE amount of work for something the user can manually configure).

Closing as CANTFIX.


Note You need to log in before you can comment on or make changes to this bug.