From: Matthew Kent <mkent@magoazul.com>
To: qemu-devel@nongnu.org
Cc: kvm-devel@lists.sourceforge.net
Subject: [Qemu-devel] vnc improvement/bugfix patches from xen
Date: Wed, 01 Aug 2007 19:22:37 -0700 [thread overview]
Message-ID: <1186021357.6486.347.camel@fuego> (raw)
After some issues with qemu vnc I happened upon the patches xen carries
in xen-unstable.hg/tools/ioemu/patches/. After getting them to apply
cleanly they have vastly improved my experience with vnc.
I've taken these, omitted any that are xen specific or add extra
features to qemu, and made some patches that apply cleanly to the latest
qemu and kvm-33 sources.
http://magoazul.com/proj/qemu/from_xen-unstable.hg_7c5c3aa858cc/
They seem to resolve the following issues for me:
- having the vncviewer 4.1.2 die with:
Rect too big: 4260x16389 at 4259,4323 exceeds 720x400
Aborted
- having some odd stuck bits on the display when using the mouse via gdm
or vim
-> fixed by vnc-backoff-screen-scan/vnc-cleanup/vnc-fixes
- occasionally having the vnc server go into an infinite loop thus
screwing up the entire vm (verified with gdb)
-> fixed by vnc-protocol-fixes
- keypad not working
-> fixed by vnc-keypad-handling
[vnc-altgr-keysym/vnc-fix-text-display-shift-key not sure, included em
anyway]
Obviously I had *zero* hand in creating these patches and the original
authors deserve the credit, I'm merely providing them for anyone
experiencing the same issues. What I have done though is abused the
patched qemu and kvm installs pretty thoroughly with vnc over the past
week without issue.
Also, in the course of this I read the recent 'Merging QEMU-DM upstream'
slides from XenSummit by Anthony Liguori who I've seen on this list.
Wondering if this is ongoing and I just duplicated some work that's
already done? :)
--
Matthew Kent <mkent@magoazul.com>
http://magoazul.com
reply other threads:[~2007-08-02 2:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1186021357.6486.347.camel@fuego \
--to=mkent@magoazul.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).