All of lore.kernel.org
 help / color / mirror / Atom feed
From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2907597 ] qemu vnc server clips at 2560x1600
Date: Wed, 02 Dec 2009 16:57:48 +0000	[thread overview]
Message-ID: <E1NFsWS-0003Ma-8e@g45xhf1.ch3.sourceforge.com> (raw)

Bugs item #2907597, was opened at 2009-12-02 16:57
Message generated for change (Tracker Item Submitted) made by mcsoccer
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2907597&group_id=180599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: qemu
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Matthew Colyer (mcsoccer)
Assigned to: Nobody/Anonymous (nobody)
Summary: qemu vnc server clips at 2560x1600

Initial Comment:
So I am running using the VESA driver to run an Ubuntu 9.10 guest at 2560x1600 (I had to modify the xserver-video-vesa package to remove an internal screen limit of 2048x2048 in the xorg vesa driver) and everything works great except that the qemu vnc server appears to clip at this resolution. The problem goes away if I run 1900x1200 and it doesn't change if I run 16bit depth or 24bit depth.

I have attached two screenshots, the first is vncing directly into qemu (which exhibits the problem) and the second is vncing to a vnc server I have running in the guest which doesn't have the problem.

I poked around in vnc.c and couldn't see any limits but I feel like its a buffer limit of some kind.

Also if you look very closely at the first image you can see that the first row is drawn correctly all the way across but subsequent rows are not.

If you need more information doesn't hesitate to ask.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2907597&group_id=180599

             reply	other threads:[~2009-12-02 16:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 16:57 SourceForge.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-13 10:29 [ kvm-Bugs-2907597 ] qemu vnc server clips at 2560x1600 SourceForge.net
2009-12-17  3:18 SourceForge.net
2009-12-28  2:20 SourceForge.net
2010-01-10 14:14 SourceForge.net
2010-01-10 14:17 SourceForge.net
2010-01-10 16:26 SourceForge.net
2010-01-10 16:30 ` Avi Kivity
2010-01-11 13:53   ` Anthony Liguori
2010-01-11 14:30     ` Avi Kivity
2010-01-11 16:25       ` Avi Kivity
2010-01-11 10:19 SourceForge.net
2010-01-11 16:17 SourceForge.net
2010-02-10 21:54 SourceForge.net

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=E1NFsWS-0003Ma-8e@g45xhf1.ch3.sourceforge.com \
    --to=noreply@sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.