[Qemu-devel] [Bug 1843151] Re: Regression: QEMU 4.1.0 qxl and KMS resoluiton only 4x10

[James Harvey]

Bisection is not going well at all with this code base!

Before your last reply, I started, and the first between 4.0.0 and 4.1.0
is aae6500972 which fails compilation:

==========

...
  CC      stubs/pci-host-piix.o
  CC      stubs/ram-block.o
  CC      stubs/ramfb.o
  CC      stubs/fw_cfg.o
  CC      stubs/semihost.o
  CC      qemu-keymap.o
  CC      util/filemonitor-stub.o

Warning, treated as error:
/build/qemu-bisect/src/qemu/docs/interop/bitmaps.rst:202:Could not lex 
literal_block as "json". Highlighting skipped.
  CC      ui/input-keymap.o
  CC      contrib/elf2dmp/main.o
  CC      contrib/elf2dmp/addrspace.o
  CC      contrib/elf2dmp/download.o
  CC      contrib/elf2dmp/pdb.o
  CC      contrib/elf2dmp/qemu_elf.o
  CC      contrib/ivshmem-client/ivshmem-client.o
  CC      contrib/ivshmem-client/main.o
  CC      contrib/ivshmem-server/ivshmem-server.o

==========

I tried just marking it as good and hoping it was a more recent
regression, instead of even doing a skip, but efa85a4d1a fails with the
same error.  I double checked that 4.0.0 and 4.1.0 still get past that
spot for me, and they do.

I tried your suggestion, be812c0, but that compiled with this error:

==========

  CC      crypto/cipher.o
  CC      crypto/tlscreds.o
  CC      crypto/tlscredsanon.o
/build/qemu-bisect/src/qemu/block/gluster.c: In function 
‘qemu_gluster_co_pwrite_zeroes’:
/build/qemu-bisect/src/qemu/block/gluster.c:994:52: warning: passing argument 4 
of ‘glfs_zerofill_async’ from incompatible pointer type [-Wincompatible-pointer
-types]
  994 |     ret = glfs_zerofill_async(s->fd, offset, size, 
gluster_finish_aiocb, &acb);
      |                                                    ^~~~~~~~~~~~~~~~~~~~
      |                                                    |
      |                                                    void (*)(struct 
glfs_fd *, ssize_t,  void *) {aka void (*)(struct glfs_fd *, long int,  void *)}
In file included from /build/qemu-bisect/src/qemu/block/gluster.c:12:
/usr/include/glusterfs/api/glfs.h:993:73: note: expected ‘glfs_io_cbk’ {aka 
‘void (*)(struct glfs_fd *, long int,  struct glfs_stat *, struct glfs_stat *, 
void
 *)’} but argument is of type ‘void (*)(struct glfs_fd *, ssize_t,  void *)’ 
{aka ‘void (*)(struct glfs_fd *, long int,  void *)’}
  993 | glfs_zerofill_async(glfs_fd_t *fd, off_t length, off_t len, glfs_io_cbk 
fn,
      |                                                             
~~~~~~~~~~~~^~
/build/qemu-bisect/src/qemu/block/gluster.c: In function 
‘qemu_gluster_do_truncate’:
/build/qemu-bisect/src/qemu/block/gluster.c:1035:13: error: too few arguments 
to function ‘glfs_ftruncate’
 1035 |         if (glfs_ftruncate(fd, offset)) {
      |             ^~~~~~~~~~~~~~
In file included from /build/qemu-bisect/src/qemu/block/gluster.c:12:
/usr/include/glusterfs/api/glfs.h:768:1: note: declared here
  768 | glfs_ftruncate(glfs_fd_t *fd, off_t length, struct glfs_stat *prestat,
      | ^~~~~~~~~~~~~~
/build/qemu-bisect/src/qemu/block/gluster.c:1046:13: error: too few arguments 
to function ‘glfs_ftruncate’
 1046 |         if (glfs_ftruncate(fd, offset)) {
      |             ^~~~~~~~~~~~~~

==========

So, I looked at configure and saw a "--disable-glusterfs" option, and
tried it.  It still failed with:

==========

  GEN     it.mo
  GEN     bg.mo
  GEN     fr_FR.mo
  GEN     zh_CN.mo
  GEN     de_DE.mo
  GEN     hu.mo
  GEN     tr.mo
for obj in hu.mo tr.mo it.mo bg.mo fr_FR.mo zh_CN.mo de_DE.mo; do \
    base=$(basename $obj .mo); \
    install -d 
/build/qemu-bisect/pkg/qemu-bisect/usr/share/locale/$base/LC_MESSAGES; \
    install -m644 $obj 
/build/qemu-bisect/pkg/qemu-bisect/usr/share/locale/$base/LC_MESSAGES/qemu.mo; \
done
make[1]: Leaving directory '/build/qemu-bisect/src/build-full/po'
install -d -m 0755 "/build/qemu-bisect/pkg/qemu-bisect/usr/share/qemu/keymaps"
set -e; for x in da     en-gb  et  fr     fr-ch  is  lt  no  pt-br  sv ar      
de     en-us  fi  fr-be  hr     it  lv  nl         pl  ru     th de-ch  es     
fo  fr-ca  hu     ja  mk  pt  sl     tr bepo    cz; do \
        install -c -m 0644 /build/qemu-bisect/src/qemu/pc-bios/keymaps/$x 
"/build/qemu-bisect/pkg/qemu-bisect/usr/share/qemu/keymaps"; \
done
install -c -m 0644 /build/qemu-bisect/src/build-full/trace-events-all 
"/build/qemu-bisect/pkg/qemu-bisect/usr/share/qemu/trace-events-all"
for d in aarch64-softmmu alpha-softmmu arm-softmmu cris-softmmu hppa-softmmu 
i386-softmmu lm32-softmmu m68k-softmmu microblazeel-softmmu microblaze-softmmu 
mips64el-softmmu mips64-softmmu mipsel-softmmu mips-softmmu moxie-softmmu 
nios2-softmmu or1k-softmmu ppc64-softmmu ppc-softmmu riscv32-softmmu 
riscv64-softmmu s390x-softmmu sh4eb-softmmu sh4-softmmu sparc64-softmmu 
sparc-softmmu tricore-softmmu unicore32-softmmu x86_64-softmmu xtensaeb-softmmu 
xtensa-softmmu aarch64_be-linux-user aarch64-linux-user alpha-linux-user 
armeb-linux-user arm-linux-user cris-linux-user hppa-linux-user i386-linux-user 
m68k-linux-user microblazeel-linux-user microblaze-linux-user 
mips64el-linux-user mips64-linux-user mipsel-linux-user mips-linux-user 
mipsn32el-linux-user mipsn32-linux-user nios2-linux-user
or1k-linux-user ppc64abi32-linux-user ppc64le-linux-user ppc64-linux-user 
ppc-linux-user riscv32-linux-user riscv64-linux-user s390x-linux-user 
sh4eb-linux-user sh4-linux-user sparc32plus-linux-user sparc64-linux-user 
sparc-linux-user tilegx-linux-user x86_64-linux-user xtensaeb-linux-user 
xtensa-linux-user; do \
make --no-print-directory --quiet BUILD_DIR=/build/qemu-bisect/src/build-full 
TARGET_DIR=$d/ -C $d install || exit 1 ; \
        done
make: Leaving directory '/build/qemu-bisect/src/build-full'
rm: cannot remove 'qemu/block-gluster.so': No such file or directory

==========

All of these builds are in clean chroot environments, so they're
starting from source scratch builds without interference between
previous attempts.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1843151

Title:
  Regression: QEMU 4.1.0 qxl and KMS resoluiton only 4x10

Status in QEMU:
  New

Bug description:
  Host is Arch Linux.  linux 5.2.13, qemu 4.1.0.  virt-viewer 8.0.

  Guest is Arch Linux Sept 2019 ISO.  linux 5.2.11.

  Have replicated this both on a system using amdgpu and one using
  integrated ASPEED graphics.

  Downgrading from 4.1.0 to 4.0.0 works as usual, see:
  https://www.youtube.com/watch?v=NyMdcYwOCvY

  Going back to 4.1.0 reproduces, see:
  https://www.youtube.com/watch?v=H3nGG2Mk6i0

  4.1.0 displays fine until KMS kicks in.

  Using 4.1.0 with virtio-vga doesn't cause this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1843151/+subscriptions