qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Heyi Guo <guoheyi@huawei.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] 答复:  Can't see mouse cursor on VNC viewer
Date: Thu, 22 Nov 2018 17:08:16 +0800	[thread overview]
Message-ID: <95db2c67-d3bd-1ab3-2f12-2adf218a3038@huawei.com> (raw)
In-Reply-To: <20181121082307.3fa3nd7cuu3canx4@sirius.home.kraxel.org>

Hi Gerd,

One more question: do you know any VNC client which supports rich cursor extension? We'd like to try such client to see the real effect.

Thanks,

Heyi


On 2018/11/21 16:23, Gerd Hoffmann wrote:
>    Hi,
>
>> and can’t see cursor either with “virtio-gpu”. Does that mean
>> virtio-gpu + VNC must rely on VNC client to draw the cursor image on
>> the screen?
> Yes.  virtio-gpu sends the cursor to the vnc client (via rich cursor
> extension) and expects the vnc client to show it.  So, if you ask your
> vnc client to not show the rich cursor the cursor is gone.  Solution:
> don't do that.
>
> stdvga has no hardware cursor support, so it is rendered to the
> framebuffer (by the guest).
>
> cirrus hardware cursor can't be mapped to rich cursor,
> so it is rendered to the framebuffer too (by qemu this time).
>
> cheers,
>    Gerd
>
>
>

  parent reply	other threads:[~2018-11-22  9:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20 12:37 [Qemu-devel] Can't see mouse cursor on VNC viewer Guoheyi
2018-11-20 15:23 ` Gerd Hoffmann
     [not found]   ` <B328F08581D714418202ABF306D3781C3B776FA6@dggeml509-mbx.china.huawei.com>
2018-11-21  8:23     ` [Qemu-devel] 答复: " Gerd Hoffmann
2018-11-21  8:54       ` Heyi Guo
2018-11-21 10:22         ` Gerd Hoffmann
2018-11-22  3:24           ` Heyi Guo
2018-11-22  9:08       ` Heyi Guo [this message]
2018-11-22 10:04         ` Gerd Hoffmann
2018-11-23  6:49           ` Heyi Guo

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=95db2c67-d3bd-1ab3-2f12-2adf218a3038@huawei.com \
    --to=guoheyi@huawei.com \
    --cc=kraxel@redhat.com \
    --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).