diff options
Diffstat (limited to 'results/classifier/118/VMM')
| -rw-r--r-- | results/classifier/118/VMM/1673 | 79 | ||||
| -rw-r--r-- | results/classifier/118/VMM/1687578 | 54 | ||||
| -rw-r--r-- | results/classifier/118/VMM/1946 | 58 | ||||
| -rw-r--r-- | results/classifier/118/VMM/2247 | 36 | ||||
| -rw-r--r-- | results/classifier/118/VMM/2512 | 75 | ||||
| -rw-r--r-- | results/classifier/118/VMM/2635 | 42 | ||||
| -rw-r--r-- | results/classifier/118/VMM/658152 | 54 |
7 files changed, 398 insertions, 0 deletions
diff --git a/results/classifier/118/VMM/1673 b/results/classifier/118/VMM/1673 new file mode 100644 index 00000000..ad55e1e0 --- /dev/null +++ b/results/classifier/118/VMM/1673 @@ -0,0 +1,79 @@ +VMM: 0.906 +ppc: 0.902 +hypervisor: 0.899 +performance: 0.891 +virtual: 0.881 +arm: 0.878 +vnc: 0.873 +peripherals: 0.870 +KVM: 0.859 +permissions: 0.854 +files: 0.854 +TCG: 0.853 +device: 0.848 +socket: 0.848 +debug: 0.848 +user-level: 0.846 +PID: 0.845 +graphic: 0.836 +risc-v: 0.831 +semantic: 0.826 +architecture: 0.824 +register: 0.817 +boot: 0.808 +network: 0.804 +kernel: 0.760 +assembly: 0.760 +x86: 0.718 +mistranslation: 0.712 +i386: 0.648 + +compilation of 8.0.0 FAILED: target/hexagon/idef-generated-emitter.indented.c on ubuntu 18.04 +Description of problem: +Cannot compile on ubuntu 18.04. +Steps to reproduce: +1. get 8.0.0 tarball or git clone/submodule... on a ubuntu 18.04 system (with a few more recent tools in ~/opt, such as python 3.9) +2. ./configure --prefix=$HOME/opt && make +3. It finishes with this strange error: FAILED: target/hexagon/idef-generated-emitter.indented.c +``` +... +[850/10154] Compiling C object target/hexagon/idef-parser.p/meson-generated_idef-parser.yy.c.o +[851/10154] Compiling C object target/hexagon/idef-parser.p/meson-generated_idef-parser.tab.c.o +[852/10154] Compiling C object target/hexagon/idef-parser.p/_home_pbourguignon_opt_src_qemu-8.0.0_target_hexagon_idef-parser_parser-helpers.c.o +[853/10154] Linking target target/hexagon/idef-parser +[854/10154] Generating target/hexagon/idef-generated-tcg with a custom command +[855/10154] Generating target/hexagon/indent with a custom command +FAILED: target/hexagon/idef-generated-emitter.indented.c +/home/pbourguignon/bin/indent -linux target/hexagon/idef-generated-emitter.c -o target/hexagon/idef-generated-emitter.indented.c +Indenting region... +Indenting region... done +Directory `/home/pbourguignon/opt/src/qemu-8.0.0/build/-linux target/hexagon/idef-generated-emitter.c -o target/hexagon/' does not exist; create? (y or n) Error reading from stdin +ninja: build stopped: subcommand failed. +Makefile:165: recipe for target 'run-ninja' failed +make[1]: *** [run-ninja] Error 1 +make[1]: Leaving directory '/home/pbourguignon/opt/src/qemu-8.0.0/build' +GNUmakefile:10: recipe for target 'all' failed +make: *** [all] Error 2 +``` +Additional information: +https://dpaste.org/Hr9Zq +``` +~/opt/src/qemu-git +16:15[pbourguignon@frprld7818008 :0.0 qemu-git ]$ ls ~/opt/bin +./ ecl-config* pydoc3@ run-avr* run-microblaze* +../ emacs@ pydoc3.9* run-bfin* run-mips* +2to3@ emacs-27.2* python@ run-bpf* run-mn10300* +2to3-3.9* emacsclient* python3@ run-cr16* run-moxie* +bundle* erb* python3-config@ run-cris* run-msp430* +bundler* etags* python3.9* run-d10v* run-or1k* +ccl* gcore* python3.9-config* run-erc32* run-ppc* +ccmake* gdb* racc* run-frv* run-pru* +cmake* gdb-add-index* rake* run-ft32* run-riscv* +cpack* gdbserver* rbs* run-h8300* run-rl78* +ctags* gem* rdbg* run-iq2000* run-rx* +ctest* idle3@ rdoc* run-lm32* run-sh* +curl* idle3.9* ri* run-m32c* run-v850* +curl-config* irb* ruby* run-m32r* sbcl* +ebrowse* pip3* run-aarch64* run-m68hc11* sis* +ecl* pip3.9* run-arm* run-mcore* typeprof* +``` diff --git a/results/classifier/118/VMM/1687578 b/results/classifier/118/VMM/1687578 new file mode 100644 index 00000000..48498ad6 --- /dev/null +++ b/results/classifier/118/VMM/1687578 @@ -0,0 +1,54 @@ +VMM: 0.926 +device: 0.919 +performance: 0.898 +virtual: 0.892 +ppc: 0.853 +graphic: 0.713 +risc-v: 0.678 +hypervisor: 0.678 +semantic: 0.664 +KVM: 0.637 +debug: 0.616 +architecture: 0.612 +mistranslation: 0.593 +x86: 0.590 +vnc: 0.545 +boot: 0.512 +i386: 0.492 +register: 0.470 +arm: 0.463 +network: 0.458 +PID: 0.402 +permissions: 0.393 +user-level: 0.369 +peripherals: 0.340 +socket: 0.340 +assembly: 0.338 +files: 0.239 +kernel: 0.234 +TCG: 0.130 + +when migrate vm, reboot in guest os, the guest os sometime hang + +qemu version:v2.9.0-rc5 release + +1.virsh migrate --live 165cf436-312f-47e7-90f2-f8aa63f34893 --copy-storage-inc qemu+ssh://10.59.163.38/system +2.run reboot in guest os, add reboot in /etc/rc.local +3.guest os hang sometime. + +strace output of qemu: + +ppoll([{fd=9, events=POLLIN}, {fd=8, events=POLLIN}, {fd=4, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=31, events=POLLIN}], 6, {0, 0}, NULL, 8) = 0 (Timeout) +ppoll([{fd=9, events=POLLIN}, {fd=8, events=POLLIN}, {fd=4, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=31, events=POLLIN}], 6, {0, 698000000}, NULL, 8) = 0 (Timeout) +poll([{fd=20, events=POLLOUT}], 1, 0) = 1 ([{fd=20, revents=POLLOUT|POLLHUP}]) +ppoll([{fd=9, events=POLLIN}, {fd=8, events=POLLIN}, {fd=4, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=31, events=POLLIN}], 6, {0, 999000000}, NULL, 8^C <unfinished ...> + +Hi, + What's the last thing the guest outputs before the hang? + Does it get back to the bios or does it hang before that? + Has the migration finished at that point or is it still going? + +Dave + +[Expired for QEMU because there has been no activity for 60 days.] + diff --git a/results/classifier/118/VMM/1946 b/results/classifier/118/VMM/1946 new file mode 100644 index 00000000..8cdb58dc --- /dev/null +++ b/results/classifier/118/VMM/1946 @@ -0,0 +1,58 @@ +VMM: 0.929 +performance: 0.903 +graphic: 0.867 +kernel: 0.861 +files: 0.810 +device: 0.803 +ppc: 0.782 +vnc: 0.752 +network: 0.738 +semantic: 0.735 +socket: 0.663 +PID: 0.620 +virtual: 0.619 +debug: 0.604 +register: 0.594 +KVM: 0.588 +user-level: 0.574 +hypervisor: 0.567 +permissions: 0.550 +architecture: 0.546 +risc-v: 0.538 +boot: 0.525 +arm: 0.462 +x86: 0.443 +mistranslation: 0.442 +i386: 0.433 +TCG: 0.389 +peripherals: 0.325 +assembly: 0.191 + +High CPU Load after QEMU 8.1.1 +Description of problem: +Since the update there is a massive CPU load and this affects the CPU load of the router. +The VMs are partially for about 3min sporadically not accessible. +The VMs themselves were not adjusted and I have in the console. + +Using the VMM, I was able to see the message recorded below. + +`watchdog:_ BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0]` + +I will also add some data like a XML file of a VM. +Additional information: + +[webproxy.log](/uploads/1d428f4c59b2397b9343a62dd8c4bce2/webproxy.log) + +[webproxy.xml](/uploads/04221c88956c49d76b4896dd8f6fd1f0/webproxy.xml) +[Host_Kernel.log](/uploads/f145bf599bf2003b89c17daaabb07143/Host_Kernel.log) + +Unfortunately I can't revert to the old QEMU version in the router OS but in the current state all my VM are not really 100% usable anymore. + +I would be very grateful if you could take a look at my case. + +many thanks in advance. + + + + +Paul diff --git a/results/classifier/118/VMM/2247 b/results/classifier/118/VMM/2247 new file mode 100644 index 00000000..34d5d489 --- /dev/null +++ b/results/classifier/118/VMM/2247 @@ -0,0 +1,36 @@ +VMM: 0.912 +device: 0.881 +network: 0.812 +graphic: 0.798 +virtual: 0.651 +socket: 0.641 +vnc: 0.595 +debug: 0.584 +boot: 0.534 +TCG: 0.507 +PID: 0.498 +arm: 0.450 +kernel: 0.448 +risc-v: 0.436 +files: 0.413 +mistranslation: 0.412 +user-level: 0.383 +semantic: 0.325 +i386: 0.318 +performance: 0.302 +x86: 0.282 +architecture: 0.261 +hypervisor: 0.259 +register: 0.231 +KVM: 0.221 +ppc: 0.188 +permissions: 0.127 +assembly: 0.108 +peripherals: 0.106 + +virsh qemu-monitor-command --hmp help information missing inject-nmi for watchdog_action +Description of problem: +watchdog_action missing inject-nmi which already supported in Commit [795dc6e4](https://gitlab.com/qemu-project/qemu/-/commit/795dc6e46d953d70b4b7ddd3f4956f8f4b9d8565) +Steps to reproduce: +1. virsh qemu-monitor-command <id> --hmp help |grep watchdog +2. change watchdog action to inject-nmi diff --git a/results/classifier/118/VMM/2512 b/results/classifier/118/VMM/2512 new file mode 100644 index 00000000..254c39f0 --- /dev/null +++ b/results/classifier/118/VMM/2512 @@ -0,0 +1,75 @@ +VMM: 0.819 +permissions: 0.797 +register: 0.796 +semantic: 0.792 +user-level: 0.790 +device: 0.790 +peripherals: 0.778 +graphic: 0.776 +risc-v: 0.772 +architecture: 0.768 +virtual: 0.767 +arm: 0.757 +debug: 0.750 +performance: 0.749 +hypervisor: 0.745 +mistranslation: 0.742 +assembly: 0.738 +x86: 0.718 +kernel: 0.714 +TCG: 0.713 +vnc: 0.708 +PID: 0.705 +files: 0.693 +ppc: 0.692 +boot: 0.674 +socket: 0.663 +network: 0.619 +KVM: 0.615 +i386: 0.548 + +macOS builds of target arm-softmmu broken +Description of problem: +Attempting to build for target `arm-softmmu` on macOS fails with errors: + +``` +[919/2786] Compiling C object libblock.a.p/block_file-posix.c.o +FAILED: libblock.a.p/block_file-posix.c.o +clang -Ilibblock.a.p -I. -I.. -Iqapi -Itrace -Iui -Iui/shader -Iblock -I/nix/store/vb7baj6dq2mvynfh6zmwxz57w83h7w0q-zlib-1.3.1-dev/include -I/nix/store/k1yzx1ykpwmhqvyr0j5fxvs9px7k92m7-glib-2.80.4-dev/include/glib-2.0 -I/nix/store/fm2kb8jvvc9s9nhi2gpr3jp6xxjxcvkq-glib-2.80.4/lib/glib-2.0/include -I/nix/store/k1yzx1ykpwmhqvyr0j5fxvs9px7k92m7-glib-2.80.4-dev/include -fcolor-diagnostics -Wall -Winvalid-pch -std=gnu11 -O2 -g -fstack-protector-strong -Wempty-body -Wendif-labels -Wexpansion-to-defined -Wformat-security -Wformat-y2k -Wignored-qualifiers -Winit-self -Wmissing-format-attribute -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wredundant-decls -Wstrict-prototypes -Wtype-limits -Wundef -Wvla -Wwrite-strings -Wno-gnu-variable-sized-type-not-at-end -Wno-initializer-overrides -Wno-missing-include-dirs -Wno-psabi -Wno-shift-negative-value -Wno-string-plus-int -Wno-tautological-type-limit-compare -Wno-typedef-redefinition -iquote . -iquote /Users/josh/workspace/qemu -iquote /Users/josh/workspace/qemu/include -iquote /Users/josh/workspace/qemu/host/include/aarch64 -iquote /Users/josh/workspace/qemu/host/include/generic -iquote /Users/josh/workspace/qemu/tcg/aarch64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fno-common -fwrapv -fno-pie -ftrivial-auto-var-init=zero -fzero-call-used-regs=used-gpr -MD -MQ libblock.a.p/block_file-posix.c.o -MF libblock.a.p/block_file-posix.c.o.d -o libblock.a.p/block_file-posix.c.o -c ../block/file-posix.c +../block/file-posix.c:1501:19: error: variable has incomplete type 'struct statfs' + struct statfs buf; + ^ +../block/file-posix.c:1501:12: note: forward declaration of 'struct statfs' + struct statfs buf; + ^ +../block/file-posix.c:1503:10: error: call to undeclared function 'fstatfs'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration] + if (!fstatfs(s->fd, &buf)) { + ^ +2 errors generated. +``` +Steps to reproduce: +1. nix-shell -p python3 ninja pkg-config glib +2. ./configure --target-list=arm-softmmu +3. make +Additional information: +The following patch fixes the issue (although I'm not sure whether this is the most appropriate fix): + +``` +diff --git a/block/file-posix.c b/block/file-posix.c +index ff928b5e85..6c78db3b0b 100644 +--- a/block/file-posix.c ++++ b/block/file-posix.c +@@ -44,10 +44,10 @@ + + #if defined(__APPLE__) && (__MACH__) + #include <sys/ioctl.h> +-#if defined(HAVE_HOST_BLOCK_DEVICE) +-#include <paths.h> + #include <sys/param.h> + #include <sys/mount.h> ++#if defined(HAVE_HOST_BLOCK_DEVICE) ++#include <paths.h> + #include <IOKit/IOKitLib.h> + #include <IOKit/IOBSD.h> + #include <IOKit/storage/IOMediaBSDClient.h> +``` diff --git a/results/classifier/118/VMM/2635 b/results/classifier/118/VMM/2635 new file mode 100644 index 00000000..80bbf99c --- /dev/null +++ b/results/classifier/118/VMM/2635 @@ -0,0 +1,42 @@ +VMM: 0.869 +graphic: 0.867 +ppc: 0.812 +device: 0.809 +files: 0.771 +architecture: 0.747 +network: 0.701 +PID: 0.696 +vnc: 0.690 +socket: 0.614 +register: 0.597 +kernel: 0.595 +performance: 0.569 +semantic: 0.568 +risc-v: 0.541 +boot: 0.517 +arm: 0.505 +virtual: 0.499 +mistranslation: 0.473 +debug: 0.467 +TCG: 0.433 +permissions: 0.419 +i386: 0.411 +x86: 0.380 +assembly: 0.372 +hypervisor: 0.321 +peripherals: 0.291 +user-level: 0.271 +KVM: 0.244 + +A use-after-free bug in pflash_cfi01 snapshot implementation +Description of problem: +The flash snapshot restore does not function correctly. Basically when you use “if=pflash,format=raw,unit=0,file=OVMF_VAR.fd", it crashes when trying to restore a snapshot. + +The root cause is: + +1. In system/runstate.c, function vm_state_notify loops through vm_change_state_head list and calls the callback function for each entry. +2. One of the callback function pointer points to function postload_update_cb in hw/block/pflash_cfi01.c. +3. In function postload_update_cb, it calls qemu_del_vm_change_state_handler in which the entry element memory is freed. +4. Note that, it is still running in the loop, the entry will be visited and get executed, the function pointer may point to a wide memory. +Additional information: + diff --git a/results/classifier/118/VMM/658152 b/results/classifier/118/VMM/658152 new file mode 100644 index 00000000..b339e150 --- /dev/null +++ b/results/classifier/118/VMM/658152 @@ -0,0 +1,54 @@ +VMM: 0.924 +x86: 0.896 +kernel: 0.896 +virtual: 0.896 +architecture: 0.883 +device: 0.868 +graphic: 0.826 +hypervisor: 0.824 +semantic: 0.812 +performance: 0.806 +ppc: 0.776 +PID: 0.768 +vnc: 0.767 +mistranslation: 0.725 +peripherals: 0.720 +network: 0.714 +user-level: 0.698 +files: 0.696 +socket: 0.676 +KVM: 0.657 +permissions: 0.646 +boot: 0.632 +register: 0.607 +arm: 0.563 +debug: 0.557 +risc-v: 0.551 +TCG: 0.502 +i386: 0.418 +assembly: 0.346 + +jp106 keyboard cannot input "_" key + +My environment are +cpu model = AMD Phenom II X2 545 +kvm version = Virtual Machine Manager 0.8.5 +host kernel version = vmlinuz-2.6.34.7-56.fc13.x86_64 +host kernel arch = x86_64 +guest you are using = CentOS-5.5, slackware-13.1 +qemu command = not use +I do not use -no-kvm-irqchip or -no-kvm-pit switch or -no-kvm switch. + +Report +I use jp106 keybord on host OS( Fedora Core 13), it work fine. +but I could not keyin "_" key on GestOS( CentOS-5.5, Slackware-13.1). +I change keybord but same result, so I reported a bug. + +A small patch to "qemu-0.15.0/ui/x_keymap.c" fixed this one: + http://patchwork.ozlabs.org/patch/38145/ +nm + +The following commit contains the patch that has been suggested in comment #1: +http://git.qemu.org/?p=qemu.git;a=commitdiff;h=33aa30cafcce053b83 +... so this issue should be fixed in recent versions of QEMU. + |