Bug 481825 - Allow virt-viewer connect to non-libvirt managed guests
Allow virt-viewer connect to non-libvirt managed guests
Status: CLOSED WONTFIX
Product: Virtualization Tools
Classification: Community
Component: virt-viewer (Show other bugs)
unspecified
All Linux
low Severity medium
: ---
: ---
Assigned To: Daniel Berrange
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-27 13:16 EST by Mark McLoughlin
Modified: 2010-03-16 13:17 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-01-27 13:23:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
virt-viewer-0.0.3-no-libvirt.patch (5.93 KB, patch)
2009-01-27 13:16 EST, Mark McLoughlin
no flags Details | Diff

  None (edit)
Description Mark McLoughlin 2009-01-27 13:16:26 EST
Created attachment 330133 [details]
virt-viewer-0.0.3-no-libvirt.patch

If you're hacking on qemu-kvm and running guests without using libvirt, it'd be really nice to use virt-viewer instead of other vnc viewers which don't have e.g. "Send Ctrl-Alt-F1" etc.

Attaching a simple patch to add that
Comment 1 Daniel Berrange 2009-01-27 13:23:50 EST
This "Send Key" functionality should be added to Vinagre instead. I don't want to complicate virt-viewer with extra codepaths for non-libvirt usage, when there is already a VNC client that is supposed to be targetted at these use cases. Going forward, virt-viewer is being re-factored to be entirely driven off libvirt event notifications and a new libvirt-gtk library, so supporting non-libvirt based usage is just not practical.

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