All of lore.kernel.org
 help / color / mirror / Atom feed
From: nicolas prochazka <prochazka.nicolas@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qxl : no mouse cursor with sdl2/gtk UI
Date: Tue, 19 Jan 2016 15:59:15 +0100	[thread overview]
Message-ID: <CADdae-g-srYx5aGYzDp4YD0DMEqZCNPZ02Aqic6xeQmYcj1j0Q@mail.gmail.com> (raw)
In-Reply-To: <1453210308.18326.83.camel@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 599 bytes --]

hello,
however it "s working perfectly under windows81
Regards,
Nicolas


2016-01-19 14:31 GMT+01:00 Gerd Hoffmann <kraxel@redhat.com>:

> On Mo, 2016-01-18 at 21:11 +0100, nicolas prochazka wrote:
> > hello,
> >
> > my  vm is starting with libvirt xml definition file.
> >
> >
> > Qemu 2.4.0
> >
> > using sdl2|gtk  ui     ( not using spice client)
>
> > Qxl video card is necessary for dual monitor configuration under
> > windows OS .
>
> Dual monitor will work with spice only.  You need the spice client and
> spice agent in the guest to have functional mouse input.
>
> cheers,
>   Gerd
>
>
>

[-- Attachment #2: Type: text/html, Size: 1048 bytes --]

  reply	other threads:[~2016-01-19 14:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 20:11 [Qemu-devel] qxl : no mouse cursor with sdl2/gtk UI nicolas prochazka
2016-01-19 13:31 ` Gerd Hoffmann
2016-01-19 14:59   ` nicolas prochazka [this message]
2016-01-20  7:00     ` Gerd Hoffmann
2016-01-20 14:20       ` nicolas prochazka
2016-01-21  8:03         ` Gerd Hoffmann
2016-01-21  9:41           ` nicolas prochazka
2016-01-21  9:54             ` Gerd Hoffmann
2016-01-21 10:38               ` nicolas prochazka
2016-01-21 10:57                 ` Gerd Hoffmann
2016-01-21 11:16                   ` nicolas prochazka
2016-01-25 12:54                     ` nicolas prochazka
2016-01-25 16:49                       ` nicolas prochazka

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=CADdae-g-srYx5aGYzDp4YD0DMEqZCNPZ02Aqic6xeQmYcj1j0Q@mail.gmail.com \
    --to=prochazka.nicolas@gmail.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 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.