From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [ kvm-Bugs-2907597 ] qemu vnc server clips at 2560x1600
Date: Sun, 10 Jan 2010 18:30:46 +0200 [thread overview]
Message-ID: <4B4A00B6.9070600@redhat.com> (raw)
In-Reply-To: <E1NU0ce-0008Ho-Em@665xhf1.ch3.sourceforge.com>
On 01/10/2010 06:26 PM, SourceForge.net wrote:
> 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.
>
>
Anthony, can you take a look at this? Seems like a serious issue, could
find nothing obvious in vnc.c.
> ----------------------------------------------------------------------
>
>
>> Comment By: Avi Kivity (avik)
>>
> Date: 2010-01-10 18:26
>
> Message:
> Confirmed with vncviewer and vinagre, so unlikely to be a client problem.
>
> ----------------------------------------------------------------------
>
> Comment By: Avi Kivity (avik)
> Date: 2010-01-10 16:17
>
> Message:
> The cropping is 512 pixels wide, the correct area is 2048 pixels wide, so
> it does look like some kind of limit.
>
> ----------------------------------------------------------------------
>
> Comment By: SourceForge Robot (sf-robot)
> Date: 2009-12-28 04:20
>
> Message:
> This Tracker item was closed automatically by the system. It was
> previously set to a Pending status, and the original submitter
> did not respond within 14 days (the time period specified by
> the administrator of this Tracker).
>
> ----------------------------------------------------------------------
>
> Comment By: Matthew Colyer (mcsoccer)
> Date: 2009-12-17 05:18
>
> Message:
> The blocks do not show up when run in SDL mode. So I believe the problem is
> still somehow related to the VNC server.
>
> ----------------------------------------------------------------------
>
> Comment By: Avi Kivity (avik)
> Date: 2009-12-13 12:29
>
> Message:
> Does it work well with SDL? Maybe the problem is not vnc related.
>
> ----------------------------------------------------------------------
>
> You can respond by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2907597&group_id=180599
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
error compiling committee.c: too many arguments to function
next parent reply other threads:[~2010-01-10 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1NU0ce-0008Ho-Em@665xhf1.ch3.sourceforge.com>
2010-01-10 16:30 ` Avi Kivity [this message]
2010-01-11 13:53 ` [Qemu-devel] Re: [ kvm-Bugs-2907597 ] qemu vnc server clips at 2560x1600 Anthony Liguori
2010-01-11 14:30 ` Avi Kivity
2010-01-11 16:25 ` Avi Kivity
2010-01-11 14:57 ` Jernej Simončič
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=4B4A00B6.9070600@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--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).