diff options
Diffstat (limited to '')
22 files changed, 1410 insertions, 0 deletions
diff --git a/results/classifier/108/other/163 b/results/classifier/108/other/163 new file mode 100644 index 00000000..c7a4a45d --- /dev/null +++ b/results/classifier/108/other/163 @@ -0,0 +1,16 @@ +other: 0.975 +semantic: 0.508 +device: 0.469 +socket: 0.378 +network: 0.369 +debug: 0.345 +boot: 0.253 +performance: 0.241 +vnc: 0.191 +PID: 0.187 +graphic: 0.126 +files: 0.049 +permissions: 0.038 +KVM: 0.009 + +SPICE session's connection_id's are not unique diff --git a/results/classifier/108/other/1630527 b/results/classifier/108/other/1630527 new file mode 100644 index 00000000..a56e45e8 --- /dev/null +++ b/results/classifier/108/other/1630527 @@ -0,0 +1,33 @@ +device: 0.911 +files: 0.697 +socket: 0.624 +graphic: 0.600 +debug: 0.530 +vnc: 0.484 +PID: 0.482 +network: 0.468 +semantic: 0.433 +permissions: 0.383 +boot: 0.371 +performance: 0.345 +other: 0.214 +KVM: 0.112 + +qemu/hw/i386/amd_iommu.c:188: possible bad shift ? + +qemu/hw/i386/amd_iommu.c:188]: (error) Shifting 32-bit value by 64 bits is undefined behaviour + +Source code is + + uint64_t mask = ((1 << length) - 1) << bitpos; + +Maybe better code + + uint64_t mask = ((1ULL << length) - 1) << bitpos; + +Thanks for reporting this bug! Looks like this has already been fixed by this commit here: +http://git.qemu.org/?p=qemu.git;a=commitdiff;h=1d5b128cbeeab638f772e + + +Released with v2.8 + diff --git a/results/classifier/108/other/1631 b/results/classifier/108/other/1631 new file mode 100644 index 00000000..cf092d94 --- /dev/null +++ b/results/classifier/108/other/1631 @@ -0,0 +1,32 @@ +device: 0.737 +graphic: 0.621 +boot: 0.603 +performance: 0.397 +PID: 0.271 +semantic: 0.231 +network: 0.214 +socket: 0.197 +debug: 0.185 +vnc: 0.180 +permissions: 0.179 +files: 0.128 +other: 0.098 +KVM: 0.017 + +[8.0.0] Host MacOS 13.3.1 – does not work or works incorrectly +Description of problem: +WINXP x86 - freezes before logging in on ARM macOS 13.3.1 host + +WINXP x86 - works but slowly x86_64 macOS 13.3.1 host + +Fedora 37 x86_64 - freezes after start on ARM macOS 13.3.1 host + +Fedora 37 x86_64 - freezes after selecting grub boot option + +**On qemu 7.2.1 all works perfectly!!!** +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/results/classifier/108/other/1631625 b/results/classifier/108/other/1631625 new file mode 100644 index 00000000..03a43fc1 --- /dev/null +++ b/results/classifier/108/other/1631625 @@ -0,0 +1,36 @@ +device: 0.614 +graphic: 0.376 +semantic: 0.312 +performance: 0.153 +socket: 0.119 +PID: 0.101 +network: 0.081 +KVM: 0.077 +debug: 0.064 +files: 0.038 +vnc: 0.038 +boot: 0.031 +other: 0.031 +permissions: 0.018 + +target-mips/dsp_helper.c: two possible bad shifts + +target-mips/dsp_helper.c:3480:1: error: V629 Consider inspecting the '0x01 << (size + 1)' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. + +Source code is + + temp = temp & ((0x01 << (size + 1)) - 1); + +If size >= 32, then better code might be + + temp = temp & ((0x01UL << (size + 1)) - 1); + +target-mips/dsp_helper.c:3509:1: error: V629 Consider inspecting the '0x01 << (size + 1)' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. + +Duplicate + +Fix has been committed: +http://git.qemu.org/?p=qemu.git;a=commitdiff;h=e6e2784cacd4cfec149 + +Released with version 2.8 + diff --git a/results/classifier/108/other/1631773 b/results/classifier/108/other/1631773 new file mode 100644 index 00000000..8b205160 --- /dev/null +++ b/results/classifier/108/other/1631773 @@ -0,0 +1,32 @@ +device: 0.831 +socket: 0.662 +network: 0.539 +vnc: 0.472 +files: 0.455 +semantic: 0.412 +graphic: 0.406 +debug: 0.288 +PID: 0.261 +other: 0.242 +boot: 0.222 +KVM: 0.213 +performance: 0.163 +permissions: 0.150 + +hw/dma/pl080.c:354: possible typo ? + +hw/dma/pl080.c:354:1: warning: V578 An odd bitwise operation detected: s->conf & (0x2 | 0x2). Consider verifying it. + +Source code is + + if (s->conf & (PL080_CONF_M1 | PL080_CONF_M1)) { + +Maybe better code + + if (s->conf & (PL080_CONF_M1 | PL080_CONF_M2)) { + +Thanks for reporting the issue, patch has now been included here: +http://git.qemu.org/?p=qemu.git;a=commitdiff;h=04bb79d1f519ae190a + +Released with version 2.8. + diff --git a/results/classifier/108/other/1632 b/results/classifier/108/other/1632 new file mode 100644 index 00000000..2821e5ea --- /dev/null +++ b/results/classifier/108/other/1632 @@ -0,0 +1,505 @@ +graphic: 0.910 +semantic: 0.899 +other: 0.890 +vnc: 0.887 +PID: 0.879 +socket: 0.865 +KVM: 0.852 +permissions: 0.850 +debug: 0.830 +device: 0.830 +boot: 0.811 +performance: 0.767 +network: 0.761 +files: 0.682 + +Porting support for GVM/AEHD to qemu 8.0 +Description of problem: +I'm trying to find reason why changes work fine with qemu 7.1 but it doesn't work with qemu 7.2 and 8.0. Could you recommend me point where I should investigate this bug/error when using GVM acceleration. I know it is not part of official QEMU and somebody is also working on that [topic ](https://gitlab.com/qemu-project/qemu/-/issues/1558). + + +``` +GVM is operational +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized)Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) + +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized)Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) + +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized)Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) + +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized)Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) + +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized)Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) + +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized)Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) + +** +ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized)Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) + +Bail out! ERROR:../util/qemu-thread-win32.c:207:qemu_sem_post: assertion failed: (sem->initialized) +``` +Steps to reproduce: +1. Checkout my fork with this branch [qemu-8.0-gvm](https://gitlab.com/MateuszKrawczuk/qemu/-/tree/qemu-8.0-gvm) +2. Build on windows using mingw64 +3. Try launch with using GVM acceleration +Additional information: +``` +./configure --enable-sdl --enable-gtk --enable-whpx --target-list=x86_64-softmmu +Using './build' as the directory for build output +ln: nie udało się utworzyć dowiązania symbolicznego 'x86_64-softmmu/qemu-system-x86_64.exe': No such file or directory +The Meson build system +Version: 0.61.5 +Source dir: C:/Users/AMD-RYZEN-PC/qemu +Build dir: C:/Users/AMD-RYZEN-PC/qemu/build +Build type: native build +Project name: qemu +Project version: 8.0.0 +C compiler for the host machine: cc -m64 -mcx16 (gcc 12.2.0 "cc (Rev10, Built by MSYS2 project) 12.2.0") +C linker for the host machine: cc -m64 -mcx16 ld.bfd 2.40 +Host machine cpu family: x86_64 +Host machine cpu: x86_64 +Program scripts/symlink-install-tree.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/symlink-install-tree.py) +Program sh found: YES (C:\Users\AMD-RYZEN-PC\scoop\apps\msys2\2023-03-18\usr\bin/sh.EXE) +C++ compiler for the host machine: c++ -m64 -mcx16 (gcc 12.2.0 "c++ (Rev10, Built by MSYS2 project) 12.2.0") +C++ linker for the host machine: c++ -m64 -mcx16 ld.bfd 2.40 +Program python3 found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe) +Program bzip2 found: YES (C:\Users\AMD-RYZEN-PC\scoop\apps\msys2\2023-03-18\mingw64\bin/bzip2.EXE) +Program iasl found: NO +Compiler for C supports link arguments -Wl,-z,relro: NO +Compiler for C supports link arguments -Wl,-z,now: NO +Compiler for C supports link arguments -Wl,--no-seh: YES +Compiler for C supports link arguments -Wl,--nxcompat: YES +Compiler for C supports link arguments -Wl,--dynamicbase: YES +Compiler for C supports link arguments -Wl,--high-entropy-va: YES +Compiler for C++ supports link arguments -Wl,--warn-common: YES +Program cgcc found: NO +Library m found: YES +Run-time dependency threads found: YES +Library util found: NO +Program midl found: NO +Program widl found: YES +Library pathcch found: YES +Library ws2_32 found: YES +Library winmm found: YES +Windows resource compiler: GNU windres (GNU Binutils) 2.40 +Has header "WinHvPlatform.h" : YES +Has header "WinHvEmulation.h" : YES +Run-time dependency appleframeworks found: NO (tried framework) +Found pkg-config: C:\Users\AMD-RYZEN-PC\scoop\apps\msys2\2023-03-18\mingw64\bin/pkg-config.EXE (1.8.0) +Run-time dependency gio-2.0 found: YES 2.76.1 +Program C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/gdbus-codegen found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/gdbus-codegen.exe) +Run-time dependency gio-unix-2.0 found: NO (tried pkgconfig) +Run-time dependency pixman-1 found: YES 0.42.2 +Run-time dependency zlib found: YES 1.2.13 +Has header "libaio.h" : NO +Run-time dependency liburing found: NO (tried pkgconfig) +Run-time dependency libnfs found: NO (tried pkgconfig) +Has header "attr/xattr.h" : NO +Run-time dependency appleframeworks found: NO (tried framework) +Run-time dependency appleframeworks found: NO (tried framework) +Run-time dependency libseccomp found: NO (tried pkgconfig) +Has header "cap-ng.h" : NO +Run-time dependency xkbcommon found: NO (tried pkgconfig) +Run-time dependency slirp found: YES 4.7.0 +Has header "libvdeplug.h" : NO +Run-time dependency jack found: NO (tried pkgconfig) +Run-time dependency sndio found: NO (tried pkgconfig) +Run-time dependency spice-protocol found: NO (tried pkgconfig) +Run-time dependency spice-server found: NO (tried pkgconfig) +Library rt found: NO +Run-time dependency libiscsi found: NO (tried pkgconfig) +Run-time dependency libzstd found: YES 1.5.5 +Run-time dependency virglrenderer found: YES 0.9.1 +Run-time dependency blkio found: NO (tried pkgconfig) +Run-time dependency libcurl found: NO (tried pkgconfig) +Run-time dependency ncurses found: NO (tried pkgconfig) +Run-time dependency ncursesw found: YES 6.4.20230211 +Has header "brlapi.h" : NO +Run-time dependency sdl2 found: YES 2.26.5 +Run-time dependency sdl2_image found: YES 2.6.3 +Library rados found: NO +Has header "rbd/librbd.h" : NO +Run-time dependency glusterfs-api found: NO (tried pkgconfig) +Run-time dependency libssh found: NO (tried pkgconfig) +Has header "bzlib.h" : YES +Library bz2 found: YES +Has header "lzfse.h" : NO +Has header "sys/soundcard.h" : NO +Has header "dsound.h" : YES +Run-time dependency epoxy found: YES 1.5.10 +Has header "epoxy/egl.h" with dependency epoxy: YES +Run-time dependency gbm found: NO (tried pkgconfig) +Run-time dependency gnutls found: NO (tried pkgconfig) +Run-time dependency gnutls found: NO (tried pkgconfig) +libgcrypt-config found: NO need ['>=1.8'] +Run-time dependency libgcrypt found: NO (tried config-tool) +Run-time dependency nettle found: NO (tried pkgconfig) +Run-time dependency gmp found: YES 6.2.1 +Run-time dependency gtk+-3.0 found: YES 3.24.38 +Run-time dependency gtk+-x11-3.0 found: NO (tried pkgconfig) +Run-time dependency vte-2.91 found: NO (tried pkgconfig) +Run-time dependency libpng found: YES 1.6.39 +Run-time dependency libjpeg found: YES 2.1.5.1 +Has header "sasl/sasl.h" : NO +Has header "security/pam_appl.h" : NO +Has header "snappy-c.h" : NO +Has header "lzo/lzo1x.h" : YES +Library lzo2 found: YES +Has header "numa.h" : NO +Library ibumad found: NO +Has header "rdma/rdma_cma.h" : NO +Library ibverbs found: NO +Run-time dependency xencontrol found: NO (tried pkgconfig) +Library xenstore found: NO +Library xenctrl found: NO +Library xendevicemodel found: NO +Library xenforeignmemory found: NO +Library xengnttab found: NO +Library xenevtchn found: NO +Library xentoolcore found: NO +Run-time dependency libcacard found: NO (tried pkgconfig) +Run-time dependency u2f-emu found: NO (tried pkgconfig) +Run-time dependency canokey-qemu found: NO (tried pkgconfig) +Run-time dependency libusbredirparser-0.5 found: NO (tried pkgconfig) +Run-time dependency libusb-1.0 found: YES 1.0.26 +Run-time dependency libpmem found: NO (tried pkgconfig) +Run-time dependency libdaxctl found: NO (tried pkgconfig) +Run-time dependency libkeyutils found: NO (tried pkgconfig) +Checking for function "gettid" : NO +Run-time dependency libselinux found: NO (tried pkgconfig) +Run-time dependency fuse3 found: NO (tried pkgconfig) +Run-time dependency libbpf found: NO (tried pkgconfig) +Run-time dependency libdw found: NO (tried pkgconfig) +Checking for function "pthread_fchdir_np" : NO +Has header "sys/epoll.h" : NO +Has header "linux/magic.h" : NO +Has header "valgrind/valgrind.h" : NO +Has header "linux/btrfs.h" : NO +Has header "libdrm/drm.h" : NO +Has header "pty.h" : NO +Has header "sys/disk.h" : NO +Has header "sys/ioccom.h" : NO +Has header "sys/kcov.h" : NO +Has header "afunix.h" : YES +Checking for function "close_range" : NO +Checking for function "accept4" : NO +Checking for function "clock_adjtime" : NO +Checking for function "dup3" : NO +Checking for function "fallocate" : NO +Checking for function "posix_fallocate" : NO +Checking for function "posix_memalign" : NO +Checking for function "_aligned_malloc" : YES +Checking for function "valloc" : NO +Checking for function "memalign" : NO +Checking for function "ppoll" : NO +Checking for function "preadv" : NO +Checking for function "pthread_fchdir_np" : NO (cached) +Checking for function "sendfile" : NO +Checking for function "setns" : NO +Checking for function "syncfs" : NO +Checking for function "sync_file_range" : NO +Checking for function "timerfd_create" : NO +Checking for function "copy_file_range" : NO +Checking for function "getifaddrs" : NO +Checking for function "openpty" with dependency -lutil: NO +Checking for function "strchrnul" : NO +Checking for function "system" : YES +Header <sys/epoll.h> has symbol "epoll_create1" : NO +Header <linux/falloc.h> has symbol "FALLOC_FL_PUNCH_HOLE" : NO +Header <linux/falloc.h> has symbol "FALLOC_FL_ZERO_RANGE" : NO +Has header "linux/fiemap.h" : NO +Checking for function "getrandom" : NO +Header <sys/inotify.h> has symbol "inotify_init" : NO +Header <sys/inotify.h> has symbol "inotify_init1" : NO +Header <sys/prctl.h> has symbol "PR_SET_TIMERSLACK" : NO +Header <linux/rtnetlink.h> has symbol "IFLA_PROTO_DOWN" : NO +Header <sys/sysmacros.h> has symbol "makedev" : NO +Header <getopt.h> has symbol "optreset" : NO +Header <netinet/in.h> has symbol "IPPROTO_MPTCP" : NO +Checking whether type "struct sigevent" has member "sigev_notify_thread_id" : NO +Checking whether type "struct stat" has member "st_atim" : NO +Checking for type "struct iovec" : NO +Checking for type "struct utmpx" : NO +Checking for type "struct mmsghdr" : NO +Header <linux/vm_sockets.h> has symbol "AF_VSOCK" : NO +Has header "vscoordint.h" : NO +Checking if "_lock_file and _unlock_file" : links: YES +Checking if "mingw setjmp and longjmp" : links: NO +Program scripts/minikconf.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/minikconf.py) +Configuring x86_64-softmmu-config-target.h using configuration +Configuring x86_64-softmmu-config-devices.mak with command +Reading depfile: C:/Users/AMD-RYZEN-PC/qemu/build/meson-private/x86_64-softmmu-config-devices.mak.d +Configuring x86_64-softmmu-config-devices.h using configuration +Program scripts/make-config-poison.sh found: YES (sh C:/Users/AMD-RYZEN-PC/qemu/scripts/make-config-poison.sh) +Run-time dependency capstone found: NO (tried pkgconfig) +Library fdt found: NO +Configuring config-host.h using configuration +Program scripts/hxtool found: YES (sh C:/Users/AMD-RYZEN-PC/qemu/scripts/hxtool) +Program scripts/shaderinclude.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/shaderinclude.py) +Program scripts/qapi-gen.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/qapi-gen.py) +Program scripts/qemu-version.sh found: YES (sh C:/Users/AMD-RYZEN-PC/qemu/scripts/qemu-version.sh) +Program scripts/decodetree.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/decodetree.py) +Program ../scripts/modules/module_block.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/block/../scripts/modules/module_block.py) +Program ../scripts/block-coroutine-wrapper.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/block/../scripts/block-coroutine-wrapper.py) +Program scripts/modinfo-collect.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/modinfo-collect.py) +Program scripts/modinfo-generate.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/modinfo-generate.py) +Program nm found: YES +Program scripts/undefsym.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/undefsym.py) +Program scripts/feature_to_c.sh found: YES (sh C:/Users/AMD-RYZEN-PC/qemu/scripts/feature_to_c.sh) +Compiler for C supports link arguments -fstack-protector-all: YES +Compiler for C supports link arguments -fstack-protector-strong: YES +Compiler for C supports link arguments -Wl,--add-stdcall-alias: YES +Compiler for C supports link arguments -Wl,--enable-stdcall-fixup: YES +Library ole32 found: YES +Library oleaut32 found: YES +Library shlwapi found: YES +Library uuid found: YES +Library intl found: YES +Program windmc found: YES +Program windres found: YES +Program wixl found: NO +Configuring 50-edk2-i386-secure.json using configuration +Configuring 50-edk2-x86_64-secure.json using configuration +Configuring 60-edk2-aarch64.json using configuration +Configuring 60-edk2-arm.json using configuration +Configuring 60-edk2-i386.json using configuration +Configuring 60-edk2-x86_64.json using configuration +Program qemu-keymap found: NO +Program sphinx-build found: NO +Program diff found: YES (C:\Users\AMD-RYZEN-PC\scoop\apps\msys2\2023-03-18\usr\bin/diff.EXE) +Program dbus-daemon found: NO +Found CMake: C:\Users\AMD-RYZEN-PC\scoop\shims/cmake.EXE (3.26.3) +WARNING: CMake Toolchain: Failed to determine CMake compilers state +Run-time dependency gvnc-1.0 found: NO (tried pkgconfig and cmake) +Run-time dependency sysprof-capture-4 found: NO (tried pkgconfig and cmake) +Program initrd-stress.sh found: YES (sh C:/Users/AMD-RYZEN-PC/qemu/tests/migration/initrd-stress.sh) +Program xgettext found: YES (C:\Users\AMD-RYZEN-PC\scoop\apps\msys2\2023-03-18\mingw64\bin/xgettext.EXE) +Program scripts/nsis.py found: YES (C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/nsis.py) +Build targets in project: 516 + +qemu 8.0.0 + + Directories + Install prefix : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu + BIOS directory : share/ + firmware path : share/qemu-firmware + binary directory : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu/. + library directory : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu/lib + module directory : lib/ + libexec directory : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu/libexec + include directory : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu/include + config directory : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu/etc + local state directory : queried at runtime + Doc directory : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu/share/doc + Build directory : C:/Users/AMD-RYZEN-PC/qemu/build + Source path : C:/Users/AMD-RYZEN-PC/qemu + GIT submodules : ui/keycodemapdb meson tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 dtc + + Host binaries + git : git + make : make + python : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe (version: 3.10) + sphinx-build : NO + gdb : /mingw64/bin/gdb-multiarch + iasl : NO + genisoimage : + wixl : NO + smbd : NO + + Configurable features + Documentation : NO + system-mode emulation : YES + user-mode emulation : NO + block layer : YES + Install blobs : YES + module support : NO + fuzzing support : NO + Audio drivers : dsound sdl + Trace backends : log + D-Bus display : NO + QOM debugging : NO + vhost-kernel support : NO + vhost-net support : NO + vhost-user support : NO + vhost-user-crypto support : NO + vhost-user-blk server support: NO + vhost-vdpa support : NO + build guest agent : YES + + Compilation + host CPU : x86_64 + host endianness : little + C compiler : cc -m64 -mcx16 + Host C compiler : cc -m64 -mcx16 + C++ compiler : c++ -m64 -mcx16 + CFLAGS : -g -O2 + CXXFLAGS : -g -O2 + QEMU_CFLAGS : -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-pie -no-pie -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fno-common -fwrapv -Wundef -Wwrite-strings -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wmissing-format-attribute -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong + QEMU_CXXFLAGS : -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-pie -no-pie -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fno-common -fwrapv -Wundef -Wwrite-strings -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wmissing-format-attribute -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong + QEMU_LDFLAGS : -fstack-protector-strong -Wl,--no-seh -Wl,--nxcompat -Wl,--dynamicbase -Wl,--high-entropy-va -Wl,--warn-common + profiler : NO + link-time optimization (LTO) : NO + PIE : NO + static build : NO + malloc trim support : NO + membarrier : NO + debug stack usage : NO + mutex debugging : NO + memory allocator : system + avx2 optimization : YES + avx512bw optimization : YES + avx512f optimization : NO + gprof : NO + gcov : NO + thread sanitizer : NO + CFI support : NO + strip binaries : NO + sparse : NO + mingw32 support : YES + + Cross compilers + x86_64 : cc + + Targets and accelerators + KVM support : NO + GVM support : YES + HAX support : YES + HVF support : NO + WHPX support : YES + NVMM support : NO + Xen support : NO + Xen emulation : NO + TCG support : YES + TCG backend : native (x86_64) + TCG plugins : NO + TCG debug enabled : NO + target list : x86_64-softmmu + default devices : YES + out of process emulation : NO + vfio-user server : NO + + Block layer support + coroutine backend : win32 + coroutine pool : YES + Block whitelist (rw) : + Block whitelist (ro) : + Use block whitelist in tools : NO + VirtFS support : NO + Live block migration : YES + replication support : YES + bochs support : YES + cloop support : YES + dmg support : YES + qcow v1 support : YES + vdi support : YES + vvfat support : YES + qed support : YES + parallels support : YES + FUSE exports : NO + VDUSE block exports : NO + + Crypto + TLS priority : NORMAL + GNUTLS support : NO + libgcrypt : NO + nettle : NO + AF_ALG support : NO + rng-none : NO + Linux keyring : NO + + Dependencies + SDL support : YES + SDL image support : YES 2.6.3 + GTK support : YES + pixman : YES 0.42.2 + VTE support : NO + slirp support : YES 4.7.0 + libtasn1 : NO + PAM : NO + iconv support : YES + curses support : YES + virgl support : YES 0.9.1 + blkio support : NO + curl support : NO + Multipath support : NO + PNG support : YES 1.6.39 + VNC support : YES + VNC SASL support : NO + VNC JPEG support : YES 2.1.5.1 + DirectSound support : YES + JACK support : NO + brlapi support : NO + vde support : NO + netmap support : NO + l2tpv3 support : NO + Linux AIO support : NO + Linux io_uring support : NO + ATTR/XATTR support : NO + RDMA support : NO + PVRDMA support : NO + fdt support : internal + libcap-ng support : NO + bpf support : NO + spice protocol support : NO + rbd support : NO + smartcard support : NO + U2F support : NO + libusb : YES 1.0.26 + usb net redir : NO + OpenGL support (epoxy) : YES 1.5.10 + GBM : NO + libiscsi support : NO + libnfs support : NO + QGA VSS support : YES + seccomp support : NO + GlusterFS support : NO + TPM support : NO + libssh support : NO + lzo support : YES + snappy support : NO + bzip2 support : YES + lzfse support : NO + zstd support : YES 1.5.5 + NUMA host support : NO + capstone : NO + libpmem support : NO + libdaxctl support : NO + libudev : NO + FUSE lseek : NO + selinux : NO + libdw : NO + + User defined options + Native files : config-meson.cross + bindir : + prefix : C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/qemu + werror : true + b_pie : false + gtk : enabled + qemu_suffix : + sdl : enabled + vfio_user_server : disabled + whpx : enabled + +Found ninja-1.11.1 at C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/usr/bin/ninja.exe +Running postconf script 'C:/Users/AMD-RYZEN-PC/scoop/apps/msys2/2023-03-18/mingw64/bin/python3.exe C:/Users/AMD-RYZEN-PC/qemu/scripts/symlink-install-tree.py' +``` diff --git a/results/classifier/108/other/1633 b/results/classifier/108/other/1633 new file mode 100644 index 00000000..496c9772 --- /dev/null +++ b/results/classifier/108/other/1633 @@ -0,0 +1,83 @@ +other: 0.780 +device: 0.745 +graphic: 0.724 +permissions: 0.705 +semantic: 0.701 +boot: 0.699 +performance: 0.689 +PID: 0.689 +debug: 0.660 +vnc: 0.645 +KVM: 0.644 +socket: 0.603 +network: 0.599 +files: 0.551 + +[8.0.0] Broken icount support on RISC-V +Description of problem: +After https://gitlab.com/qemu-project/qemu/-/commit/5a4ae64cac49564354cd6f17598840e4af70e4f5 was merged, RISC-V VMs no longer run with -icount 1 specified in the QEMU arguments. Reverting this commit resolves the issue. +Steps to reproduce: +1. Download preinstalled Ubuntu 22.04.2 image from [here](https://cdimage.ubuntu.com/releases/22.04.2/release/ubuntu-22.04.2-preinstalled-server-riscv64+unmatched.img.xz) +2. Download uboot from [here](http://security.ubuntu.com/ubuntu/pool/main/u/u-boot/u-boot-qemu_2022.01+dfsg-2ubuntu2.3_all.deb) +3. Extract both. +4. Run with the command-line specified above. +Additional information: +Reading Ubuntu wiki describing how to run RISC-V VMs can help: https://wiki.ubuntu.com/RISC-V/QEMU + +Full output: + +``` +% qemu-system-riscv64 \ +-machine virt -nographic -m 2048 -smp 4 \ +-kernel u-boot/qemu-riscv64_smode/uboot.elf \ +-device virtio-net-device,netdev=eth0 -netdev user,id=eth0 \ +-drive file=ubuntu-22.04.2-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio -icount 1 + +OpenSBI v1.2 + ____ _____ ____ _____ + / __ \ / ____| _ \_ _| + | | | |_ __ ___ _ __ | (___ | |_) || | + | | | | '_ \ / _ \ '_ \ \___ \| _ < | | + | |__| | |_) | __/ | | |____) | |_) || |_ + \____/| .__/ \___|_| |_|_____/|____/_____| + | | + |_| + +Platform Name : riscv-virtio,qemu +Platform Features : medeleg +Platform HART Count : 4 +Platform IPI Device : aclint-mswi +Platform Timer Device : aclint-mtimer @ 10000000Hz +Platform Console Device : uart8250 +Platform HSM Device : --- +Platform PMU Device : --- +Platform Reboot Device : sifive_test +Platform Shutdown Device : sifive_test +Firmware Base : 0x80000000 +Firmware Size : 236 KB +Runtime SBI Version : 1.0 + +Domain0 Name : root +Domain0 Boot HART : 0 +Domain0 HARTs : 0*,1*,2*,3* +Domain0 Region00 : 0x0000000002000000-0x000000000200ffff (I) +Domain0 Region01 : 0x0000000080000000-0x000000008003ffff () +Domain0 Region02 : 0x0000000000000000-0xffffffffffffffff (R,W,X) +Domain0 Next Address : 0x0000000080200000 +Domain0 Next Arg1 : 0x00000000bfe00000 +Domain0 Next Mode : S-mode +Domain0 SysReset : yes + +Boot HART ID : 0 +Boot HART Domain : root +Boot HART Priv Version : v1.12 +Boot HART Base ISA : rv64imafdch +Boot HART ISA Extensions : time,sstc +Boot HART PMP Count : 16 +Boot HART PMP Granularity : 4 +Boot HART PMP Address Bits: 54 +Boot HART MHPM Count : 16 +Boot HART MIDELEG : 0x0000000000001666 +Boot HART MEDELEG : 0x0000000000f0b509 +qemu-system-riscv64: Bad icount read +``` diff --git a/results/classifier/108/other/1633508 b/results/classifier/108/other/1633508 new file mode 100644 index 00000000..65fb0995 --- /dev/null +++ b/results/classifier/108/other/1633508 @@ -0,0 +1,65 @@ +network: 0.849 +device: 0.837 +PID: 0.773 +performance: 0.759 +semantic: 0.752 +permissions: 0.710 +socket: 0.658 +other: 0.653 +graphic: 0.613 +debug: 0.613 +boot: 0.572 +files: 0.506 +vnc: 0.474 +KVM: 0.127 + +libvirt cannot hot insert interfaces to qemu + +When attempting to hot insert an interface using Ubuntu 16.04.1, I get the following +$ virsh attach-interface --domain gluster1 --type direct \ +> --source test0 --model virtio \ +> --mac 2a:b6:b0:dc:c7:c4 --config --live +error: Failed to attach interface +error: internal error: unable to execute QEMU command 'getfd': No file descriptor supplied via SCM_RIGHTS + +test0 exists: +$ ip link show test0 +35: test0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 + link/ether aa:8c:65:2e:79:61 brd ff:ff:ff:ff:ff:ff + +Just in case I did it wrong with direct, I did network +$ virsh net-list + Name State Autostart Persistent +---------------------------------------------------------- + default active yes yes + mgmtnet0 active yes yes + +$ virsh attach-interface --domain gluster1 --type network \ +> --source default --model virtio \ +> --mac 2a:b6:b0:dc:c7:c4 --config --live +error: Failed to attach interface +error: internal error: unable to execute QEMU command 'getfd': No file descriptor supplied via SCM_RIGHTS + + +This seems to be an old bug, but is still present. Other relevant information: +$ qemu-system-x86_64 --version +QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.5), Copyright (c) 2003-2008 Fabrice Bellard +$ virsh -v +1.3.1 + +This looks like a libvirt bug at a first glance. Have you tried to report it to the libvirt project? (See https://libvirt.org/bugs.html ) ... also, can you re-create the bug with the very latest upstream version of libvirt and qemu, or does it only occur with an (older?) version of Ubuntu? + +That seems to be the Libvirt of Ubuntu in Xenial. + +In the past similar issues were uncommon configs or changed behavior on updates that triggered apparmor or SELinux protection. + +=> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1747442 +=> https://bugzilla.redhat.com/show_bug.cgi?id=731243 + +It could as well be some variant of bug 1677398. + +If you are still affected by this, could you check: +1. if it also happens on newer libvirt versions e.g. do a trial run in the most recent Ubuntu +2. if it does could you check dmesg in your setup for related apparmor denials? + + diff --git a/results/classifier/108/other/1634726 b/results/classifier/108/other/1634726 new file mode 100644 index 00000000..22572789 --- /dev/null +++ b/results/classifier/108/other/1634726 @@ -0,0 +1,63 @@ +network: 0.781 +vnc: 0.725 +device: 0.696 +PID: 0.687 +graphic: 0.590 +semantic: 0.587 +socket: 0.543 +performance: 0.524 +debug: 0.449 +boot: 0.339 +KVM: 0.318 +files: 0.312 +other: 0.280 +permissions: 0.248 + +qemu "make test" fails in iov.c with "undefined reference" on aarch64 on Ubuntu 16.04 + +I'm building the master tree on a multicore ARMv8 machine running Ubuntu 16.04. The build worked just fine, using the simple directions in the README file and "make -j 64" to do the build. + +Next, I did "make test", and got this: + +emv@armv8hello:~/src/qemu/qemu/build$ make test +make -C tests/tcg test +make[1]: Entering directory '/mnt/src/qemu/qemu/build/tests/tcg' + CC test_path.o + LINK test_path +test_path.o: In function `qemu_iovec_is_zero': +/home/emv/src/qemu/qemu/util/iov.c:365: undefined reference to `buffer_is_zero' +collect2: error: ld returned 1 exit status +/home/emv/src/qemu/qemu/rules.mak:105: recipe for target 'test_path' failed +make[1]: *** [test_path] Error 1 +make[1]: Leaving directory '/mnt/src/qemu/qemu/build/tests/tcg' +Makefile:498: recipe for target 'test' failed +make: *** [test] Error 2 + +I expected "make test" to complete with no errors. + +uname -a: +Linux armv8hello.local.lan 4.4.0-38-generic #57-Ubuntu SMP Wed Sep 7 10:19:14 UTC 2016 aarch64 aarch64 aarch64 GNU/Linux + +emv@armv8hello:~/src/qemu/qemu$ more VERSION +2.7.50 + +You want 'make check' to run the self-tests. 'make test' is a bunch of broken old stuff :-( + + +Ah, perhaps this bug should be renamed, "remove make test target". + +While I'm noting things, "make check" builds OK on this system, complaining only about kvm. My next goal is "make docker-test". + +"make docker-test" fails repeatedly with + +Pulling repository docker.io/library/qemu +docker: Error: image library/qemu:debian-bootstrap not found. +See 'docker run --help'. +Pulling repository docker.io/library/qemu +docker: Error: image library/qemu:fedora not found. +See 'docker run --help'. + +etc. + +"make test" has been removed, so I'll mark this as fixed now. + diff --git a/results/classifier/108/other/1635 b/results/classifier/108/other/1635 new file mode 100644 index 00000000..2c338c8f --- /dev/null +++ b/results/classifier/108/other/1635 @@ -0,0 +1,52 @@ +performance: 0.864 +graphic: 0.645 +device: 0.466 +PID: 0.281 +other: 0.226 +permissions: 0.216 +semantic: 0.177 +socket: 0.168 +files: 0.126 +vnc: 0.122 +debug: 0.082 +network: 0.074 +boot: 0.059 +KVM: 0.005 + +Slow graphics output under aarch64 hvf (no dirty bitmap tracking) +Description of problem: +When using a display adapter such as `bochs-display` (which, yes, I realize is not the ideal choice for an aarch64 guest, but it works fine under TCG and KVM, so bear with me) under `hvf` acceleration on an M1 Mac, display output is slow enough to be measured in seconds-per-frame. + +The issue seems to stem from each write to the framebuffer memory resulting in a data abort, while the expected behavior is that only one such write results in a data abort exception, which is handled by marking the region dirty and then subsequent writes do not yield exceptions until the display management in QEMU resets the dirty flag. Instead, every pixel drawn causes the VM to trap, and performance is degraded. +Steps to reproduce: +1. Start an aarch64 HVF guest with the `bochs-display` display adapter. +2. Observe performance characteristics. +3. +Additional information: +I reported this issue on IRC around a year ago, and was provided with a patch by @agraf which I have confirmed works. That patch was shared on the `qemu-devel` mailing list in February, 2022, with a response from @pm215: https://lists.gnu.org/archive/html/qemu-devel/2022-02/msg00609.html + +As a quick summary, the patch takes this snippet from the i386 HVF target: + +https://gitlab.com/qemu-project/qemu/-/blob/master/target/i386/hvf/hvf.c#L132-138 + +And applies a variation of it to the ARM target when handling a data abort exception, before this assert: + +https://gitlab.com/qemu-project/qemu/-/blob/master/target/arm/hvf/hvf.c#L1381 + +Something to the effect of: + +```c + if (iswrite) { + uint64_t gpa = hvf_exit->exception.physical_address; + hvf_slot *slot = hvf_find_overlap_slot(gpa, 1); + + if (slot && slot->flags & HVF_SLOT_LOG) { + memory_region_set_dirty(slot->region, 0, slot->size); + hv_vm_protect(slot->start, slot->size, HV_MEMORY_READ | + HV_MEMORY_WRITE | HV_MEMORY_EXEC); + break; + } + } +``` + +I am reporting this issue now as I updated my git checkout with the release of QEMU 8.0.0 and was surprised to find that the patch had never made it upstream and the issue persists. diff --git a/results/classifier/108/other/1635695 b/results/classifier/108/other/1635695 new file mode 100644 index 00000000..5ae2cd1a --- /dev/null +++ b/results/classifier/108/other/1635695 @@ -0,0 +1,28 @@ +device: 0.908 +boot: 0.852 +other: 0.814 +graphic: 0.678 +semantic: 0.674 +PID: 0.550 +network: 0.500 +debug: 0.468 +performance: 0.455 +permissions: 0.408 +vnc: 0.392 +files: 0.391 +socket: 0.373 +KVM: 0.083 + +ovmf + smp + hyper-v + windows 7: doesn't work + +- using ovmf +- enable smp (>1 processors/cores) +- enable hyper-v features (eg. -cpu Haswell,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff) +- try to boot or install windows 7 x64 + +Result: black screen and hangs + +Sigh, the Windows bug that keeps on giving. And, users avoiding libvirt and sticking with the QEMU command line, despite the fact that using libvirt & its tools would save them from this bug. + +Anyway, this report is a duplicate of <https://bugs.launchpad.net/qemu/+bug/1593605>; please read that one for the background. Closing this one as invalid (just like the other one). Thanks. + diff --git a/results/classifier/108/other/1636126 b/results/classifier/108/other/1636126 new file mode 100644 index 00000000..6b94b316 --- /dev/null +++ b/results/classifier/108/other/1636126 @@ -0,0 +1,71 @@ +graphic: 0.833 +performance: 0.791 +debug: 0.787 +permissions: 0.786 +semantic: 0.759 +other: 0.742 +boot: 0.723 +files: 0.720 +socket: 0.715 +PID: 0.701 +device: 0.699 +network: 0.670 +vnc: 0.602 +KVM: 0.448 + +qemu-system-arm segfaults on "smulbb r7, r5, r5" + +I'll attach a binary that runs fine with qemu-system-arm V2.2.0 but V2.7.0 segfaults. +By stepping through with gdb I found that the segfaults happens when executing the line "smulbb r7, r5, r5" (where r7=0x1, r5=0x12). +I'll also attach a debugger screenshot. + +call and output: + +/opt/qemu-system-arm -M integratorcp -cpu cortex-m3 -semihosting -nographic -monitor null -serial null -no-reboot -kernel 0MFW_SafetyFunctions_ParameteruP1_CUNIT.elf + +------------ CUnit_MFW_SafetyFunctions_Parameter ------------ + + + CUnit - A Unit testing framework for C - Version 2.1-0 + http://cunit.sourceforge.net/ + + +Suite: Suite_MFW_SafetyFunctions_Parameter + Test: MFW_SafetyFunctions_Parameter_PositionLimiter ... Segmentation fault (core dumped) + + + +in the screenshot one can see the assembler line that fails + +Hi. This command line: + +/opt/qemu-system-arm -M integratorcp -cpu cortex-m3 ... + +is wrong. The integratorcp board is not a Cortex-M3 and trying to stick one into it produces something that is not likely to work very well. Please can you either (a) using a board that's expected to support a Cortex-M3, like the lm3s6965evb or lm3s811evb, or (b) using the integratorcp's default CPU if that's what your guest code is supposed to run on. This sort of frankenstein combination is not supported... + +That said, your problem here is that the SMULBB instruction is part of the M profile DSP extension, which is not implemented in the Cortex-M3 (it first appears in the -M4). Not UNDEFing on the DSP instructions in our Cortex-M3 model was a bug in QEMU v2.2 which we have subsequently fixed. + +You should build your guest code to target the CPU you're trying to run it on. + + +Hi Peter! + +Thank you for your help, it works fine with "-M integratprcp -cpu cortex-m4" but I might choose another board as you suggested. +I didn't have in mind that we switched to M4 instruction set. + +Where do I get the information that integratorcp is not good for cortex-M3? +Or better question: where do I get information which machine is good for it? +Actually "-M help" doesn't give me any with M3 (already tried "none" and "virt" without success). +On the other hand I see all cortex variants in the output of "-M integratorcp -cpu help" so I had a good feeling about it... + + + +You're right that we don't document this at all (and the board models don't have any way of restricting the set of things that '-cpu help' lists to only what they support). As a rule of thumb, for any ARM board except 'virt' don't try to use anything except the default CPU. They all model embedded boards which don't have any kind of support for unplugging and replugging CPUs. + +The particular problem with trying to use cortex-m3 on the integratorcp is that there is no NVIC on the integratorcp so if you try to do anything involving the M3's interrupt controller it is likely to blow up or otherwise misbehave. + +Our two M3 boards are the lm3s6965evb and lm3s811evb (they're Stellaris boards). + + +Tried to run cortex-M4 command on M3. + diff --git a/results/classifier/108/other/1636770 b/results/classifier/108/other/1636770 new file mode 100644 index 00000000..f7f88257 --- /dev/null +++ b/results/classifier/108/other/1636770 @@ -0,0 +1,41 @@ +graphic: 0.824 +device: 0.767 +performance: 0.679 +semantic: 0.672 +other: 0.642 +permissions: 0.569 +files: 0.546 +debug: 0.533 +vnc: 0.488 +network: 0.470 +boot: 0.442 +socket: 0.439 +PID: 0.379 +KVM: 0.229 + +mouse wheel works only with -usbdevice tablet + +2.7.0 + +tested with windows 10 + +As a test I tried using the wheel mouse on Mac OS 10.4 running in qemu-system-ppc. Scrolling sort of works. It also causes the mouse pointer to move up or down. That is definitely some kind of error. + +Where the problem could be: +Guest operating system +USB mouse emulation +Front-end + +I'm going to rule out "Guest operating system". I think it could be the emulated USB mouse or the front-end. Maybe even a combination of the two. + +I tried using Windows in QEMU and oddly enough both Windows XP and Windows 2000 did not have a working mouse. Both guests had "-usb -device usb-mouse" in their QEMU command-line. Using usb_del to remove the USB mouse made the mouse in the guest work again. The scroll wheel did work. WordPad's window did scroll, but the mouse pointer also moved up and down just like in Mac OS 10.4. Just to note I am using the Cocoa front-end. I'm guessing you are using SDL. + +The emulated mouse does need some fixing. + +The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to +"Incomplete" now. +If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Thank you and sorry for the inconvenience. + + +[Expired for QEMU because there has been no activity for 60 days.] + diff --git a/results/classifier/108/other/1637 b/results/classifier/108/other/1637 new file mode 100644 index 00000000..5bd0aa64 --- /dev/null +++ b/results/classifier/108/other/1637 @@ -0,0 +1,16 @@ +device: 0.840 +performance: 0.660 +graphic: 0.655 +debug: 0.579 +permissions: 0.220 +boot: 0.219 +other: 0.214 +vnc: 0.201 +semantic: 0.196 +PID: 0.184 +network: 0.164 +socket: 0.081 +files: 0.054 +KVM: 0.044 + +Crash when executing `ucomiss` instructions emulating an x86-64 CPU on an AArch64 host diff --git a/results/classifier/108/other/1637447 b/results/classifier/108/other/1637447 new file mode 100644 index 00000000..47f8fa2a --- /dev/null +++ b/results/classifier/108/other/1637447 @@ -0,0 +1,32 @@ +vnc: 0.903 +network: 0.884 +device: 0.865 +socket: 0.784 +performance: 0.699 +semantic: 0.673 +graphic: 0.616 +files: 0.586 +boot: 0.494 +PID: 0.354 +debug: 0.333 +other: 0.319 +permissions: 0.296 +KVM: 0.295 + +VNC/RFB: QEMU reports incorrect name (length) + +If the name of a machine (as set with the -name argument) has a length longer than 1024, (RFB) VNC clients will not receive a correct RFB ServerInit message. + +I suspect this is the problem: + +https://github.com/qemu/qemu/blob/master/ui/vnc.c#L2463 + +The return value of snprintf is used as the value for the name-length field in the ServerInit message. +This is problematic for names that were truncated to 1024, as the length will now be bigger than the actual name. + +I think a quick fix would be to simply report min(size,1024) to the client... + +The right fix here is to switch to use g_strdup_printf and avoid a fixed length stack buffer entirely. + +Fix has been committed: http://git.qemu.org/?p=qemu.git;a=commitdiff;h=97efe4f961dcf5a0126 + diff --git a/results/classifier/108/other/1637511 b/results/classifier/108/other/1637511 new file mode 100644 index 00000000..785091d1 --- /dev/null +++ b/results/classifier/108/other/1637511 @@ -0,0 +1,45 @@ +KVM: 0.903 +graphic: 0.741 +other: 0.712 +semantic: 0.630 +device: 0.587 +performance: 0.556 +network: 0.520 +socket: 0.491 +permissions: 0.483 +PID: 0.478 +files: 0.382 +boot: 0.348 +debug: 0.347 +vnc: 0.192 + +Armitage crashes KVM guest with Kali2016.2 for QXL video + +I recently got a strange bug which seems to be related to qemu-kvm and QXL. I came here via the hints of the KVM web-site for KVM/qemu bug tracking. But, I am not sure whether this is the right bug-tracker at all. Please advise me if I placed the report wrongly. + +I installed Kali2016.2 as a KVM guest on a Opensuse Leap 42.1 host (fully updated). The KVM guest machine was configured to use a spice display and QXL video. Everything OK with the installation with the exception of one major application with a Java interface - Armitage. + +Armitage is correctly configured and starts (with some minor Java errors) and opens its interface (msf console, target window etc.) Trying to open the 2 specific menu points "Hosts" or "Attack" in the menu bar leads to something very strange: The screen flickers, then the whole login session is stopped and a standard login window opens. This happens independently of the setting for the type of Armitage target window (graphical or table like) + +Why do I report this bug here? +Because it happens with the QXL graphical video interface ONLY - not with video=vga or vmvga ! Neither does the bug occur when Armitage is started in a ssh (-X) session from the host. + +So, it is closely related to qemu-kvm AND QXL and the Java interaction with both. + +I really wonder what in the world can make 2 specific menu points of a Java application crash a KVM guest and restart a login shell in Kali only when QXL is used? + +qemu-kvm version : 2.3.1 +Kernel version of OS LEAP 42.1: Linux 4.1.31-30-default + +I have described the bug also to the Kali people - see https://bugs.kali.org/view.php?id=3698 + +Please inform me what further data are required - if this is relevant in this bug-tracker at all. + +If it's related to QXL, you should likely rather report this bug to the Spice people instead of QEMU. See https://www.spice-space.org/support.html for more information. + +Is this still an issue with the latest version? Did you ever report it to the Spice project? + +Can be closed - did not happen in later versions + +Ok, thanks for your answer, so I'm closing this ticket now. + diff --git a/results/classifier/108/other/1637693 b/results/classifier/108/other/1637693 new file mode 100644 index 00000000..b0646eea --- /dev/null +++ b/results/classifier/108/other/1637693 @@ -0,0 +1,68 @@ +permissions: 0.785 +device: 0.774 +KVM: 0.766 +debug: 0.759 +performance: 0.740 +boot: 0.733 +network: 0.728 +semantic: 0.723 +PID: 0.717 +other: 0.700 +files: 0.696 +graphic: 0.677 +vnc: 0.658 +socket: 0.629 + +QEMU not able to create vm with pflash and UEFI bios + +Running Fedora 24 with the virt-preview repo on QEMU Version 2.7.0 and libvirt version 2.2.0. Tried to install a windows 10 vm with the OVMF bios and this error happens every time, it didnt happen when using the stable version of qemu for fedora 24. + +libvirtError: internal error: qemu unexpectedly closed the monitor: 2016-10-29T04:07:29.678518Z qemu-system-x86_64: -drive file=/usr/share/edk2/aarch64/QEMU_EFI-pflash.raw,if=pflash,format=raw,unit=0,readonly=on: oversized backing file, pflash segments cannot be mapped under 00000000ff800000 + +Any ideas? + +Seems to work when using virt-install to do a manual uefi install + +This happens because the ArmVirtQemu firmware binary (== UEFI for aarch64 guests) is passed to qemu-system-x86_64. + +Normally such errors are not caught at QEMU startup time (similarly to the misconfiguration when you try to boot an aarch64 ISO in an x86_64 guest -- normally you would only notice the problem within the guest); however, in this case, the size of the ArmVirtQemu fw binary (64MB) is above the size that qemu-system-x86_64 permits for firmware binaries. (The pflash chip sizes and their limits are different per target.) That's why QEMU errs out early. + +I think this might be related to: + +https://bugzilla.redhat.com/show_bug.cgi?id=1295146 +https://www.redhat.com/archives/libvir-list/2016-October/msg00045.html + +I'll make the subscribers in that RHBZ aware of this issue. + +Zach if you can still reproduce, can you provide the libvirt XML and the associated qemu command line from /var/lib/libvirt/qemu/$VMNAME.log for the working (virt-install) config and the non-working (virt-manager) config? + +Hello Cole sorry i didnt get to you sooner, there doesnt seem to be a log anywhere in that specified area but here is the working xml https://u.teknik.io/hp3jG.xml. I did update everything to the latest version and it still does it (with the addition of a new thing where it says my cpu isnt compatible http://pastebin.com/5i7EdHza). I cant seem to find the virt-manager xml config/virt-install. + +This is all for PCI passthrough at the end of the day + +Alright found them sorry about that +Libvirt.conf : https://u.teknik.io/a0rWz.txt +qemu.conf: https://u.teknik.io/5Gd3Q.txt + +Similar report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860363 +> This sounds like you are using the x86_64 architecture, but an aarch64 (arm64) firmware. Install ovmf (package in Debian) and use that as a firmware if your goal is to run an x86_64 OS. + +(Your /usr/share/edk2/aarch64/QEMU_EFI-pflash.raw is for ARM aarch64, and qemu is x86_64 system, you can't run ARM firmware with x86_64 emulator) + +I had same "oversized backing file, pflash .." error message after installing qemu-efi package (https://packages.ubuntu.com/artful/qemu-efi) which is "UEFI firmware for 64-bit ARM virtual machines". + +It was fixed after purging qemu-efi (qemu-efi-aarch64) packages, installing ovmf package (https://packages.ubuntu.com/artful/ovmf) and restarting virt-manager. +New virtual machine was created with correct UEFI firmware: /usr/share/OVMF/OVMF_CODE.fd + +My machine xml has line with /usr/share/OVMF/OVMF_CODE.fd +<domain type='kvm'> +... +<os> +... +<loader readonly='yes' type='pflash'>/usr/share/OVMF/OVMF_CODE.fd</loader>" + +This should be solved by now, minimally by the firmware auto-selection feature. Regarding libvirt commits, see <https://bugzilla.redhat.com/show_bug.cgi?id=1564270#c6> and <https://bugzilla.redhat.com/show_bug.cgi?id=1564270#c9>. Regarding virt-manager commits, the latest related commit I can see is 15a9502b7b7a ("details: Fix showing the firmware type in case of firmware auto selection", 2020-01-15). + + +Just a side note, once you tried to boot the vm with the wrong firmware, it will create an oversized nvram file that you must delete or else you will stil get the same error even after switching to the right firmware. + diff --git a/results/classifier/108/other/1638 b/results/classifier/108/other/1638 new file mode 100644 index 00000000..61cab376 --- /dev/null +++ b/results/classifier/108/other/1638 @@ -0,0 +1,34 @@ +boot: 0.903 +graphic: 0.873 +device: 0.787 +other: 0.702 +debug: 0.702 +semantic: 0.614 +permissions: 0.567 +PID: 0.526 +files: 0.481 +performance: 0.467 +vnc: 0.427 +KVM: 0.389 +network: 0.289 +socket: 0.267 + +BUG: Segmentation fault when -object memory-backend-file use readonly=on, prealloc=on together +Description of problem: +Segmentation Fault while booting VM. +Steps to reproduce: +1. set qemu boot params to `-object memory-backend-file,id=mem1,readonly=on,prealloc=on,mem-path=<any-img-file>,size=4G` +2. +3. +Additional information: +It might not be a bug, probably a feature. +The reason of this segfault is: +readonly would mmap the backend file using PROT_READ, make it readonly, +but the prealloc=on would touch_pages the memory mmaped by the file. +SO the segfault happens. + +But there is no docs about this segfault condition (the readonly and prealloc cannot be used together.) + +And maybe there is a way to solve this problem, I think. +Use mmap the memory backend file to PROT_READ|PROT_WRITE at the beginnning, after touch_pages, then mprotect the memory. +change the prot to readonly if required. diff --git a/results/classifier/108/other/1639 b/results/classifier/108/other/1639 new file mode 100644 index 00000000..e0b17301 --- /dev/null +++ b/results/classifier/108/other/1639 @@ -0,0 +1,16 @@ +device: 0.797 +performance: 0.716 +other: 0.643 +network: 0.500 +graphic: 0.496 +semantic: 0.319 +permissions: 0.297 +debug: 0.226 +files: 0.197 +PID: 0.114 +socket: 0.090 +boot: 0.067 +vnc: 0.048 +KVM: 0.025 + +No supported machine for loongson-3A4000 mips64el diff --git a/results/classifier/108/other/1639322 b/results/classifier/108/other/1639322 new file mode 100644 index 00000000..98124e7e --- /dev/null +++ b/results/classifier/108/other/1639322 @@ -0,0 +1,46 @@ +graphic: 0.864 +other: 0.706 +performance: 0.667 +debug: 0.610 +semantic: 0.572 +device: 0.552 +permissions: 0.515 +PID: 0.487 +network: 0.456 +files: 0.425 +vnc: 0.398 +socket: 0.369 +boot: 0.211 +KVM: 0.102 + +pasting into ppc64 serial console kills qemu + +- run qemu-system-ppc64 +- when X window appears press Ctrl+Alt+3 +- paste any text longer than 16 characters + + +qemu-system-ppc64: /home/abuild/rpmbuild/BUILD/qemu-2.6.1/hw/char/spapr_vty.c:40: vty_receive: Assertion `(dev->in - dev->out) < 16' failed. +Aborted (core dumped) + +Broken in SUSE Leap 42.2 and git 4eb28abd52d48657cff6ff45e8dbbbefe4dbb414 + +What user interface are you using? VNC? SDL? GTK? + +This is gtk interface. + +However, the function on line 40 os spapr_vty.c looks really insane. + +It asserts that it is not given more data to input in a ring buffer than is size of the buffer and then stuffs all the data in regardless of the amount of data already present. + +It should probably loop or one of its callers but I did not find a decent comparable piece of code to cut and paste whatever callbacks are needed for the other side to consume the bytes. + +OK, seems like you need to compile QEMU with CONFIG_VTE enabled (i.e. with the vte-devel packages installed before running configure) to get copy-n-paste support in the GTK interface, that's why I was initially not able to reproduce this issue. +Anyway, now I can trigger the assert(), too, and I've suggested a patch here: + +http://marc.info/?<email address hidden> + +FWIW, the crash should be fixed by this commit here: +http://git.qemu.org/?p=qemu.git;a=commitdiff;h=7bacfd7f7289192c83330 +(but we still need to fix the gtk side, too, to only send as much characters at once as the receiving side can take) + diff --git a/results/classifier/108/other/1639791 b/results/classifier/108/other/1639791 new file mode 100644 index 00000000..5e046e00 --- /dev/null +++ b/results/classifier/108/other/1639791 @@ -0,0 +1,48 @@ +device: 0.861 +KVM: 0.804 +graphic: 0.775 +vnc: 0.753 +debug: 0.747 +files: 0.739 +other: 0.687 +performance: 0.666 +semantic: 0.617 +PID: 0.592 +network: 0.586 +permissions: 0.582 +boot: 0.487 +socket: 0.398 + +early virtio console output is lost + +This is broken in git and reportedly in 2.5 through 2.7. + +Running a Linux kernel which includes a testsuite in initrd sometimes produces no output. + +Reportedly the console is sometimes not open when the early userspace tries to log output resulting in either the testsuite terminating early or not writing the output. + +Workaround patch is here: + +https://git.zx2c4.com/WireGuard/commit/?id=d2de8b0862a7fbb51a7f2f958d58f0efe4648259 + +reportedly you would get -EBADF there when no output is generated. + +Also this reportedly happens with virtio console only, not virtio serial port. + +It seems that the author of said testsuite did not report the problem so I write it down so it does not get lost. + +test (in bash): + +n=0 ; while [ $n -lt 100 ] && grep -m 1 -F "WireGuard Test Suite on Linux 4.8.6" <( /opt/qemu/bin/qemu-system-x86_64 -nodefaults -nographic -machine q35,accel=kvm -cpu host -smp 2 -m 64M -object rng-random,id=rng0,filename=/dev/urandom -device virtio-rng-pci,rng=rng0 -device virtio-serial,max_ports=2 -chardev stdio,id=stdio -device virtconsole,chardev=stdio -chardev file,id=status,path=result.txt -device virtserialport,chardev=status -monitor none -kernel wireguard-testing-harness-bzImage-e87cb2a7-145c-4985-907f-17e81fae329b -append "console=hvc0 initcall_debug=1 loglevel=7" ) ; do echo $n ; n=$(expr $n + 1) ; pkill -f wireguard ; done + +This typically does 10-20 iterations but sometimes tens of iterations run without issue. + + + +The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to +"Incomplete" now. +If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Thank you and sorry for the inconvenience. + + +[Expired for QEMU because there has been no activity for 60 days.] + diff --git a/results/classifier/108/other/1639983 b/results/classifier/108/other/1639983 new file mode 100644 index 00000000..c639de2b --- /dev/null +++ b/results/classifier/108/other/1639983 @@ -0,0 +1,48 @@ +graphic: 0.911 +device: 0.878 +network: 0.866 +semantic: 0.853 +other: 0.827 +debug: 0.827 +permissions: 0.816 +vnc: 0.802 +performance: 0.799 +files: 0.776 +socket: 0.750 +PID: 0.727 +boot: 0.669 +KVM: 0.409 + +e1000 EEPROM have bad checksum + +I am using qemu-system-i386 to emulate FreeDOS with e1000 nic card. + +I am using Intel PRODOS v.19.0 (latest version with E1000ODI.COM file). +E1000ODI.COM v.5.07 (140116) + +http://pclosmag.com/html/issues/201208/page11.html +Suggest that v.4.75 (120212) was/is working. +Oldest PRODOS available version seems now 18.5 (June 2013) which I have not tested yet. + +When running it, it detect: Slot 18, IRQ 11, Port C000. + +But complains: +EEPROM checksum was incorrect. + +Contact your services network supplier for a replacement. + +paul@paul89473:~$ qemu-system-i386 --version +QEMU emulator version 2.6.1 (Debian 1:2.6.1+dfsg-0ubuntu5), Copyright (c) 2003-2008 Fabrice Bellard +paul@paul89473:~$ + +I'm also seeing this issue with version 2.11. Currently Intel's oldest available is 18.4 and this version reports an invalid checksum. The E1000.dos file when loaded doesn't recognize the emulated NIC. + +I was able to get the e1000odi DOS driver to correctly detect the Intel e1000e once I added a PCIe bus, however the e1000 still reports a bad checksum as of this posting with the master branch. + +The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to +"Incomplete" now. +If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Thank you and sorry for the inconvenience. + + +[Expired for QEMU because there has been no activity for 60 days.] + |