All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benedikt Morbach <benedikt.morbach@googlemail.com>
To: qemu-devel@nongnu.org
Cc: kraxel@redhat.com
Subject: Re: [Qemu-devel] Mousegrab broken with vfio in 2.1.0 (was: [PATCH 00/25] qemu gtk ui overhaul)
Date: Thu, 07 Aug 2014 23:58:23 +0200	[thread overview]
Message-ID: <1407448703.22670.1.camel@googlemail.com> (raw)
In-Reply-To: <1407363732.4938.2.camel@googlemail.com>

On Thu, 2014-08-07 at 00:22 +0200, Benedikt Morbach wrote:
> I think one of those gtk patches broke mouse/keyboard grab for my
> Windows 8 vfio/vga-passthrough setup in 2.1.0 and I was instructed on
> IRC to report that here.
> 
> With 2.0.0 I got a black qemu window with "This VM has no graphic
> display device", which I could click on to get a mouse grab.
> With 2.1.0 I just get the qemu monitor window.
> If I press Ctrl-Alt-g or use the corresponding menu entry, the gtk
> window grabs the input devices and the titlebar changes to "press
> Ctrl-Alt-g to release grab", but none of the input reaches the vm.
> 
> I tried all of {gtk3, sdl} x {usb-mouse, usb-tablet}:
> With gtk3, none worked.
> With sdl usb-tablet worked, but I haven't figured out how to do an
> actual mouse grab. (maybe related to me passing "-vga none"?)
> 
> If I drop the "-vga none" I can get a mouse-grab, but the passed-through
> gpu won't work, so this is no option for me.
> 
> If needed I can produce some logs with both 2.0 and 2.1, but I don't
> know what options I should pass to qemu to make those useful.
> 
> Here is how I start qemu:
> qemu-system-x86_64
>     -enable-kvm -M q35  -cpu host,hv-time,kvm=off -vga none
>     -m 8192 -smp 2,sockets=1,cores=2,threads=1
>     -bios /usr/share/qemu/bios.bin
>     -device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1
>     -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on
>     -device vfio-pci,host=01:00.1,bus=root.1,addr=00.1
>     -drive file=/mnt/images/Win8.raw,id=disk,format=raw,if=virtio
>     -device ich9-intel-hda,bus=pcie.0,addr=1b.0,id=sound0
>     -device hda-micro,id=sound0-codec0,bus=sound0.0,cad=0 
>     -net bridge -net nic,model=virtio
>     -rtc base=localtime
>     -usb
>     -usbdevice mouse
>     -usbdevice keyboard

I have now bisected this down to:

commit ed1132e41a31ded554adc542ddf043714f05b9d0                                                                                                                                                                                                

    gtk: support multiple gfx displays

    Each display gets its own tab.  Tab switching continues to work like it
    did, just the hotkeys of the vte consoles changes in case a secondary
    display is present as it will get ctrl-alt-2 assigned and the vtes are
    shifted by one.

  reply	other threads:[~2014-08-07 21:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06 22:22 [Qemu-devel] Mousegrab broken with vfio in 2.1.0 (was: [PATCH 00/25] qemu gtk ui overhaul) Benedikt Morbach
2014-08-07 21:58 ` Benedikt Morbach [this message]
2014-08-13  1:19   ` [Qemu-devel] [PATCH] fix gtk interface for vfio + vga=none (was: Mousegrab broken with vfio in 2.1.0) Benedikt Morbach
2014-08-25 13:51 ` [Qemu-devel] Mousegrab broken with vfio in 2.1.0 (was: [PATCH 00/25] qemu gtk ui overhaul) Gerd Hoffmann

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=1407448703.22670.1.camel@googlemail.com \
    --to=benedikt.morbach@googlemail.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.