On 01/10/2010 10:30 AM, Avi Kivity wrote:
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
On 01/11/2010 03:53 PM, Anthony Liguori wrote:
Anthony, can you take a look at this? Seems like a serious issue,
could find nothing obvious in vnc.c.
VNC_MAX_WIDTH and VNC_MAX_HEIGHT in vnc.h are currently defined to
2048. We do dirty tracking with a bitmap and that bitmap is currently
a
On Monday, January 11, 2010, 14:53:05, Anthony Liguori wrote:
2048 is bigger than any physical screen that I know of so I assume this
is a multiple monitor scenario.
30 TFTs have resolution 2560x1600.
Speaking of large resolutions, I just tried 2360x1770 (the largest
offered by VMWare VGA
On 01/11/2010 04:30 PM, Avi Kivity wrote:
VNC_MAX_WIDTH and VNC_MAX_HEIGHT in vnc.h are currently defined to
2048. We do dirty tracking with a bitmap and that bitmap is
currently a fixed size.
2048 is bigger than any physical screen that I know of so I assume
this is a multiple monitor
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
