From: Peter Lieven <lieven-lists@dlhnet.de>
To: Serge Hallyn <serge.hallyn@ubuntu.com>, Peter Lieven <pl@kamp.de>
Cc: Doug Smythies <dsmythies@telus.net>,
Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] vnc regression with -vga vmware
Date: Mon, 17 Mar 2014 16:01:04 +0100 [thread overview]
Message-ID: <53270E30.4080400@dlhnet.de> (raw)
In-Reply-To: <20140317141012.GE7725@sergelap>
I found 2 issues:
- with vmware VGA the server surface and the client desktop size are out of sync for some time
at a resolution change. the server surface gets updates for x coordinates that are out of bound
for the client.
- the max width of the client (2360) is not dividable by 16 (VNC_DIRTY_PIXELS_PER_BIT).
I will try to fix this in ui/vnc but we should definetly look for the root cause.
Peter
On 17.03.2014 15:10, Serge Hallyn wrote:
> It does happen then as well (I suppose), but after X is done setting
> up, it happens every time I try to connect.
>
> Quoting Peter Lieven (pl@kamp.de):
>> Serge,
>>
>> can you confirm this happens at a resolution change?
>>
>> Peter
>>
>> On 17.03.2014 14:44, Gerd Hoffmann wrote:
>>> On Fr, 2014-03-14 at 11:06 -0500, Serge Hallyn wrote:
>>>> Hi,
>>>>
>>>> upstream git HEAD appears to have regressed with -vga vmware -vnc.
>>>>
>>>> If I run
>>>>
>>>> ./qemu-system-x86_64 -enable-kvm -vnc :1 -m 1024 -cdrom ~/trusty-desktop-amd64.iso -vga vmware
>>>>
>>>> then tightvncviewer gives me:
>>>>
>>>> Connected to RFB server, using protocol version 3.8
>>>> No authentication needed
>>>> Authentication successful
>>>> Desktop name "QEMU"
>>>> VNC server default format:
>>>> 32 bits per pixel.
>>>> Least significant byte first in each pixel.
>>>> True colour: max red 255 green 255 blue 255, shift red 16 green 8
>>>> blue 0
>>>> Using default colormap which is TrueColor. Pixel format:
>>>> 32 bits per pixel.
>>>> Least significant byte first in each pixel.
>>>> True colour: max red 255 green 255 blue 255, shift red 16
>>>> green 8 blue 0
>>>> Same machine: preferring raw encoding
>>>> Rect too large: 16x4 at (2352, 1766)
>>>>
>>>> gvncviewer simply says 'Disconnected from server'.
>>>>
>>>> It works fine if I don't use -vga vmware.
>>>>
>>>> I bisected it to commit 12b316d: ui/vnc: optimize dirty bitmap tracking
>>> Peter, that is yours, any idea what this is?
>>>
>>> cheers,
>>> Gerd
>>>
>>>
>>
>> --
>>
>> Mit freundlichen Grüßen
>>
>> Peter Lieven
>>
>> ...........................................................
>>
>> KAMP Netzwerkdienste GmbH
>> Vestische Str. 89-91 | 46117 Oberhausen
>> Tel: +49 (0) 208.89 402-50 | Fax: +49 (0) 208.89 402-40
>> pl@kamp.de | http://www.kamp.de
>>
>> Geschäftsführer: Heiner Lante | Michael Lante
>> Amtsgericht Duisburg | HRB Nr. 12154
>> USt-Id-Nr.: DE 120607556
>>
>> ...........................................................
>>
next prev parent reply other threads:[~2014-03-17 15:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 16:06 [Qemu-devel] vnc regression with -vga vmware Serge Hallyn
2014-03-17 13:44 ` Gerd Hoffmann
2014-03-17 13:49 ` Peter Lieven
2014-03-17 14:01 ` Peter Lieven
2014-03-17 14:10 ` Serge Hallyn
2014-03-17 15:01 ` Peter Lieven [this message]
2014-03-17 15:19 ` Serge Hallyn
2014-03-17 15:29 ` Peter Lieven
2014-03-17 17:35 ` Serge Hallyn
2014-03-17 17:36 ` Peter Lieven
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=53270E30.4080400@dlhnet.de \
--to=lieven-lists@dlhnet.de \
--cc=dsmythies@telus.net \
--cc=kraxel@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=serge.hallyn@ubuntu.com \
/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.