GTK display problems with plain QEMU

[Ordspilleren]

Hello,

When trying to run GVT-g with DMA_BUF directly from QEMU (Windows Guest), I get the following output from QEMU. I am using GTK display:
qemu-system-x86_64: vfio_region_write(3f1a954f-efe9-4be5-b9b4-0a0b8c599907:region0+0x2230, 0x10120119,4) failed: Bad address

And this output in dmesg:

[ 3917.549659] gvt: vgpu(1) Invalid FORCE_NONPRIV write 83a8 at offset 24ec
[ 3917.815792] gvt: vgpu 1: srm access to non-render register (21f0)
[ 3917.815794] gvt: vgpu 1: MI_STORE_REGISTER_MEM handler error
[ 3917.815794] gvt: vgpu 1: cmd parser error
[ 3917.815795] 0x0 
[ 3917.815795] 0x24 

[ 3917.815797] gvt: vgpu 1: scan wa ctx error
[ 3917.815798] GVT Internal error  for the guest
[ 3917.815799] Now vgpu 1 will enter failsafe mode.
[ 3917.815800] gvt: vgpu 1: failed to submit desc 0
[ 3917.815800] gvt: vgpu 1: fail submit workload on ring 0
[ 3917.815801] gvt: vgpu 1: fail to emulate MMIO write 00002230 len 4

I have tried with both the 25.20.100.6326 and 25.20.100.6577 drivers, none of them work.
Running Arch Linux with the 4.20.13 kernel and QEMU 3.1.0.

Any idea what the problem could be? It works fine in Libvirt with SPICE.

[Ordspilleren]

Just a small update. I switched the VM to the Q35 chipset and I no longer get the above errors. The VM can boot fully if I use VNC with gl=on instead of GTK with gl=on. It seems that GTK display is now the culprit, but I get no useful errors upon crash.

EDIT: I got it working in Libvirt by overriding the default display with GTK. Now the question is: What does Libvirt do that QEMU doesn't that makes this work?

[ChristophSchmidpeter]

@Ordspilleren: As I cannot start the VM with libvirt because of #81: Could you attach your VM.xml file please? That may be helpful to me.

[TerrenceXu]

@Ordspilleren Can you upgraded host kernel to 5.0 and try again?

[Ordspilleren]

@Ordspilleren Can you upgraded host kernel to 5.0 and try again?

I am running 5.0 now, it still doesn't work. QEMU with VNC or SPICE works, GTK doesn't.

[ivanstepanovftw]

Same for me

$ sudo ./qemu.sh
qemu-system-x86_64: vfio_region_write(55207785-ec09-4e42-af93-f3d083293ede:region0+0x2230, 0xe7fc8119,4) failed: Bad address
$ qemu-system-x86_64 --version
QEMU emulator version 3.1.92 (v4.0.0-rc2-11-g10546e09e1-dirty)
Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
$ uname -r
5.1.0-1-MANJARO

dmesg.log
qemu.sh
cpuinfo.txt

[amon-ra]

Just a small update. I switched the VM to the Q35 chipset and I no longer get the above errors. The VM can boot fully if I use VNC with gl=on instead of GTK with gl=on. It seems that GTK display is now the culprit, but I get no useful errors upon crash.

EDIT: I got it working in Libvirt by overriding the default display with GTK. Now the question is: What does Libvirt do that QEMU doesn't that makes this work?

Can you post your working config? I have the same error in libvirt.

Thanks in advice