diff options
Diffstat (limited to 'results/classifier/118/mistranslation')
30 files changed, 2095 insertions, 0 deletions
diff --git a/results/classifier/118/mistranslation/1100 b/results/classifier/118/mistranslation/1100 new file mode 100644 index 000000000..e61d86f61 --- /dev/null +++ b/results/classifier/118/mistranslation/1100 @@ -0,0 +1,61 @@ +mistranslation: 0.904 +user-level: 0.793 +risc-v: 0.402 +device: 0.389 +graphic: 0.381 +architecture: 0.356 +permissions: 0.314 +semantic: 0.307 +arm: 0.284 +VMM: 0.284 +register: 0.255 +performance: 0.194 +boot: 0.192 +PID: 0.158 +KVM: 0.150 +TCG: 0.146 +virtual: 0.143 +hypervisor: 0.129 +debug: 0.126 +network: 0.119 +socket: 0.097 +ppc: 0.082 +peripherals: 0.073 +vnc: 0.061 +files: 0.059 +kernel: 0.056 +assembly: 0.035 +x86: 0.005 +i386: 0.001 +-------------------- +user-level: 0.912 +device: 0.785 +risc-v: 0.401 +semantic: 0.222 +virtual: 0.156 +mistranslation: 0.116 +VMM: 0.036 +files: 0.014 +permissions: 0.014 +assembly: 0.011 +network: 0.009 +hypervisor: 0.007 +debug: 0.006 +arm: 0.006 +boot: 0.006 +TCG: 0.004 +PID: 0.004 +register: 0.003 +peripherals: 0.003 +graphic: 0.003 +kernel: 0.002 +architecture: 0.002 +ppc: 0.002 +socket: 0.002 +vnc: 0.002 +KVM: 0.001 +performance: 0.001 +x86: 0.000 +i386: 0.000 + +It riscv64 platform support user model?? diff --git a/results/classifier/118/mistranslation/1156 b/results/classifier/118/mistranslation/1156 new file mode 100644 index 000000000..f5e6aae6c --- /dev/null +++ b/results/classifier/118/mistranslation/1156 @@ -0,0 +1,61 @@ +mistranslation: 0.834 +device: 0.815 +performance: 0.581 +VMM: 0.478 +assembly: 0.455 +graphic: 0.452 +debug: 0.419 +architecture: 0.419 +arm: 0.408 +i386: 0.317 +x86: 0.243 +virtual: 0.236 +semantic: 0.202 +user-level: 0.141 +boot: 0.139 +network: 0.079 +hypervisor: 0.074 +TCG: 0.056 +permissions: 0.050 +ppc: 0.044 +files: 0.044 +register: 0.028 +risc-v: 0.024 +PID: 0.017 +socket: 0.017 +KVM: 0.017 +kernel: 0.016 +peripherals: 0.012 +vnc: 0.007 +-------------------- +assembly: 0.932 +VMM: 0.654 +virtual: 0.507 +KVM: 0.216 +kernel: 0.185 +debug: 0.114 +hypervisor: 0.105 +x86: 0.075 +network: 0.025 +files: 0.021 +user-level: 0.020 +performance: 0.015 +risc-v: 0.011 +semantic: 0.010 +architecture: 0.007 +boot: 0.006 +permissions: 0.005 +device: 0.005 +arm: 0.005 +peripherals: 0.004 +i386: 0.004 +mistranslation: 0.004 +PID: 0.003 +register: 0.003 +ppc: 0.003 +TCG: 0.003 +vnc: 0.002 +graphic: 0.001 +socket: 0.000 + +Incorrect implementation of vmsumudm instruction diff --git a/results/classifier/118/mistranslation/1178 b/results/classifier/118/mistranslation/1178 new file mode 100644 index 000000000..26eb110e2 --- /dev/null +++ b/results/classifier/118/mistranslation/1178 @@ -0,0 +1,61 @@ +mistranslation: 0.938 +device: 0.714 +risc-v: 0.663 +performance: 0.588 +architecture: 0.577 +graphic: 0.533 +semantic: 0.478 +permissions: 0.404 +network: 0.383 +debug: 0.365 +files: 0.356 +register: 0.356 +virtual: 0.304 +boot: 0.278 +arm: 0.260 +hypervisor: 0.204 +assembly: 0.162 +VMM: 0.127 +TCG: 0.124 +peripherals: 0.120 +ppc: 0.113 +PID: 0.111 +vnc: 0.096 +kernel: 0.094 +user-level: 0.094 +KVM: 0.069 +socket: 0.062 +i386: 0.028 +x86: 0.020 +-------------------- +assembly: 0.936 +risc-v: 0.456 +register: 0.107 +kernel: 0.037 +files: 0.030 +virtual: 0.026 +architecture: 0.016 +semantic: 0.013 +user-level: 0.012 +performance: 0.012 +device: 0.011 +debug: 0.011 +TCG: 0.011 +PID: 0.010 +peripherals: 0.007 +VMM: 0.006 +arm: 0.006 +x86: 0.005 +boot: 0.004 +ppc: 0.003 +network: 0.003 +hypervisor: 0.002 +graphic: 0.002 +KVM: 0.001 +socket: 0.001 +mistranslation: 0.001 +i386: 0.001 +vnc: 0.001 +permissions: 0.001 + +is that riscv64 `feq.s` only should consider the lowest 32-bits. diff --git a/results/classifier/118/mistranslation/130 b/results/classifier/118/mistranslation/130 new file mode 100644 index 000000000..ec9a8e5b6 --- /dev/null +++ b/results/classifier/118/mistranslation/130 @@ -0,0 +1,61 @@ +mistranslation: 0.997 +device: 0.753 +performance: 0.522 +network: 0.510 +graphic: 0.437 +semantic: 0.431 +arm: 0.371 +files: 0.361 +permissions: 0.345 +peripherals: 0.343 +debug: 0.340 +user-level: 0.336 +hypervisor: 0.259 +boot: 0.236 +register: 0.235 +risc-v: 0.206 +virtual: 0.186 +architecture: 0.181 +vnc: 0.147 +socket: 0.143 +ppc: 0.125 +i386: 0.122 +kernel: 0.095 +assembly: 0.074 +VMM: 0.057 +TCG: 0.054 +x86: 0.050 +PID: 0.039 +KVM: 0.026 +-------------------- +mistranslation: 0.969 +virtual: 0.392 +user-level: 0.191 +x86: 0.062 +files: 0.031 +network: 0.027 +semantic: 0.025 +assembly: 0.022 +register: 0.013 +device: 0.010 +peripherals: 0.006 +i386: 0.006 +debug: 0.006 +arm: 0.004 +ppc: 0.003 +boot: 0.003 +kernel: 0.003 +performance: 0.002 +hypervisor: 0.002 +TCG: 0.002 +PID: 0.002 +VMM: 0.001 +risc-v: 0.001 +architecture: 0.001 +socket: 0.001 +graphic: 0.001 +vnc: 0.000 +permissions: 0.000 +KVM: 0.000 + +QEmu translation is incorrect when using REX in combination with LAHF/SAHF diff --git a/results/classifier/118/mistranslation/1334 b/results/classifier/118/mistranslation/1334 new file mode 100644 index 000000000..40c51be26 --- /dev/null +++ b/results/classifier/118/mistranslation/1334 @@ -0,0 +1,61 @@ +mistranslation: 0.987 +graphic: 0.895 +device: 0.754 +performance: 0.678 +peripherals: 0.288 +debug: 0.272 +arm: 0.260 +semantic: 0.232 +user-level: 0.151 +architecture: 0.137 +network: 0.122 +PID: 0.119 +virtual: 0.099 +boot: 0.095 +ppc: 0.089 +permissions: 0.073 +hypervisor: 0.064 +VMM: 0.054 +assembly: 0.045 +register: 0.035 +vnc: 0.031 +TCG: 0.020 +socket: 0.016 +kernel: 0.011 +x86: 0.010 +files: 0.007 +risc-v: 0.006 +i386: 0.005 +KVM: 0.004 +-------------------- +virtual: 0.989 +user-level: 0.935 +hypervisor: 0.786 +files: 0.152 +debug: 0.060 +x86: 0.033 +semantic: 0.024 +register: 0.018 +device: 0.015 +VMM: 0.011 +boot: 0.005 +i386: 0.005 +KVM: 0.003 +performance: 0.003 +kernel: 0.003 +assembly: 0.003 +mistranslation: 0.003 +graphic: 0.002 +peripherals: 0.002 +TCG: 0.002 +ppc: 0.002 +architecture: 0.001 +network: 0.001 +arm: 0.001 +risc-v: 0.001 +PID: 0.001 +permissions: 0.001 +socket: 0.000 +vnc: 0.000 + +qemu-img map qcow2 image,but can't get right zero area diff --git a/results/classifier/118/mistranslation/1338 b/results/classifier/118/mistranslation/1338 new file mode 100644 index 000000000..5beb28f42 --- /dev/null +++ b/results/classifier/118/mistranslation/1338 @@ -0,0 +1,61 @@ +mistranslation: 0.908 +semantic: 0.698 +performance: 0.689 +graphic: 0.673 +device: 0.488 +virtual: 0.415 +user-level: 0.205 +i386: 0.199 +PID: 0.178 +x86: 0.128 +ppc: 0.103 +hypervisor: 0.097 +permissions: 0.096 +arm: 0.092 +peripherals: 0.087 +architecture: 0.080 +risc-v: 0.078 +vnc: 0.074 +network: 0.070 +debug: 0.068 +assembly: 0.064 +KVM: 0.063 +VMM: 0.063 +register: 0.061 +TCG: 0.058 +kernel: 0.048 +boot: 0.045 +socket: 0.023 +files: 0.015 +-------------------- +user-level: 0.938 +performance: 0.727 +virtual: 0.192 +peripherals: 0.126 +x86: 0.022 +files: 0.016 +device: 0.014 +i386: 0.011 +semantic: 0.010 +debug: 0.009 +network: 0.006 +boot: 0.002 +PID: 0.002 +assembly: 0.001 +graphic: 0.001 +mistranslation: 0.001 +ppc: 0.001 +permissions: 0.000 +VMM: 0.000 +TCG: 0.000 +hypervisor: 0.000 +kernel: 0.000 +architecture: 0.000 +arm: 0.000 +risc-v: 0.000 +KVM: 0.000 +vnc: 0.000 +socket: 0.000 +register: 0.000 + +Remove gprof diff --git a/results/classifier/118/mistranslation/1435101 b/results/classifier/118/mistranslation/1435101 new file mode 100644 index 000000000..64cae51be --- /dev/null +++ b/results/classifier/118/mistranslation/1435101 @@ -0,0 +1,70 @@ +mistranslation: 0.868 +graphic: 0.857 +device: 0.814 +boot: 0.810 +x86: 0.746 +performance: 0.729 +i386: 0.716 +user-level: 0.625 +architecture: 0.577 +semantic: 0.560 +files: 0.554 +permissions: 0.549 +kernel: 0.499 +vnc: 0.495 +ppc: 0.474 +PID: 0.444 +socket: 0.439 +register: 0.422 +peripherals: 0.387 +debug: 0.357 +TCG: 0.353 +risc-v: 0.325 +VMM: 0.315 +arm: 0.279 +network: 0.181 +assembly: 0.164 +virtual: 0.142 +hypervisor: 0.081 +KVM: 0.014 +-------------------- +i386: 0.992 +boot: 0.960 +x86: 0.947 +user-level: 0.903 +virtual: 0.169 +debug: 0.075 +TCG: 0.043 +hypervisor: 0.022 +files: 0.019 +network: 0.013 +performance: 0.009 +PID: 0.005 +device: 0.003 +socket: 0.003 +semantic: 0.003 +register: 0.002 +kernel: 0.002 +VMM: 0.002 +assembly: 0.002 +peripherals: 0.001 +architecture: 0.001 +vnc: 0.001 +permissions: 0.001 +graphic: 0.001 +ppc: 0.000 +risc-v: 0.000 +mistranslation: 0.000 +arm: 0.000 +KVM: 0.000 + +Windows, QEMU 2.2.50 fails to boot XP CD + +Running XP Pro SP3 host 32bit. When I launch qemu booting from CD, it fails to complete load, getting stuck at "Setup is starting Windows". It does not proceed past. I tried to disable floppy but still no go. Download older version 1.5.1-win32, 0.9.1, same problem. +qemu-system-i386w.exe -cdrom "d:\XP.ISO" -hda d:\xp.img -boot d +with -global isa-fdc.driveA=c or -no-fd-bootchk switches but no go. I see others have run into this problem as well but no real solutions. Some folks says turning off floppy works and I tried. + +Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays? + +[Expired for QEMU because there has been no activity for 60 days.] + diff --git a/results/classifier/118/mistranslation/1586229 b/results/classifier/118/mistranslation/1586229 new file mode 100644 index 000000000..348069054 --- /dev/null +++ b/results/classifier/118/mistranslation/1586229 @@ -0,0 +1,90 @@ +mistranslation: 0.976 +semantic: 0.911 +graphic: 0.895 +user-level: 0.878 +PID: 0.848 +device: 0.822 +performance: 0.812 +debug: 0.791 +permissions: 0.785 +register: 0.764 +boot: 0.747 +assembly: 0.701 +architecture: 0.692 +files: 0.644 +socket: 0.619 +ppc: 0.555 +network: 0.540 +x86: 0.537 +risc-v: 0.516 +arm: 0.487 +i386: 0.480 +kernel: 0.449 +hypervisor: 0.439 +virtual: 0.436 +peripherals: 0.411 +TCG: 0.377 +vnc: 0.361 +VMM: 0.357 +KVM: 0.322 +-------------------- +user-level: 0.983 +debug: 0.947 +x86: 0.892 +i386: 0.823 +boot: 0.219 +ppc: 0.040 +VMM: 0.027 +device: 0.016 +virtual: 0.015 +TCG: 0.014 +network: 0.011 +semantic: 0.011 +socket: 0.010 +files: 0.009 +PID: 0.005 +register: 0.005 +risc-v: 0.003 +performance: 0.002 +vnc: 0.002 +permissions: 0.002 +assembly: 0.002 +hypervisor: 0.002 +kernel: 0.001 +arm: 0.001 +graphic: 0.001 +mistranslation: 0.001 +peripherals: 0.001 +KVM: 0.000 +architecture: 0.000 + +seabios hell + +getting weird annoying seabios hell and not sure how to fix it. + +ok. + +there IS a SEA-BIOS. There IS a way in. + +-I found it by mistake.(and yall need to move the BIOS key...its in the wrong place) + +I was tryng to boot Yosemite to re-install. I mashed the key too early and it wanted to boot the hard drive. + +Apparently the bios loads AFTER the hard drive wants to boot, not BEFORE it.And it will ONLY load when booting a hard disk. + +..Booting hard disk...[mash F8 here but let go and wait] +eventually will want to load the OS and clear the screen[mash F8 again] + +--Youre in! + +Its tiny, like a mini award bios but youre in! +-Change anything HERE, though...and kiss booting a cd goodbye! + +Im trying to diagnose a black screen, seems related to seabios, not the vga driver. + +-mayhaps wants to boot hard disk but in fact its not bootable as the installer hung(and often unices install bootloader late in process)? + +I cant boot the disc to reinstall to tell. But I have a few dos iso lying around...hmmm. + +Sounds like your describing problems with SeaBIOS, not with QEMU. May I suggest to report this issues to the SeaBIOS project instead? See http://seabios.org/ + diff --git a/results/classifier/118/mistranslation/1590322 b/results/classifier/118/mistranslation/1590322 new file mode 100644 index 000000000..d95410860 --- /dev/null +++ b/results/classifier/118/mistranslation/1590322 @@ -0,0 +1,75 @@ +mistranslation: 0.992 +device: 0.699 +semantic: 0.662 +graphic: 0.418 +performance: 0.386 +peripherals: 0.380 +network: 0.252 +vnc: 0.161 +ppc: 0.156 +kernel: 0.146 +x86: 0.138 +virtual: 0.131 +user-level: 0.118 +i386: 0.115 +architecture: 0.110 +VMM: 0.099 +register: 0.096 +debug: 0.085 +risc-v: 0.083 +socket: 0.080 +boot: 0.076 +PID: 0.076 +hypervisor: 0.065 +arm: 0.064 +assembly: 0.057 +permissions: 0.044 +TCG: 0.038 +KVM: 0.028 +files: 0.027 +-------------------- +user-level: 0.906 +semantic: 0.803 +virtual: 0.147 +debug: 0.123 +TCG: 0.046 +peripherals: 0.037 +x86: 0.023 +files: 0.020 +device: 0.018 +hypervisor: 0.012 +network: 0.012 +performance: 0.011 +i386: 0.007 +graphic: 0.006 +kernel: 0.005 +mistranslation: 0.005 +register: 0.004 +boot: 0.003 +arm: 0.003 +socket: 0.003 +PID: 0.003 +ppc: 0.003 +permissions: 0.002 +VMM: 0.002 +architecture: 0.002 +risc-v: 0.001 +assembly: 0.001 +vnc: 0.001 +KVM: 0.000 + +mouse_button 0 takes back to initial position + +i wrote a python script to perform some drag function in the Qemu simulator. +mouse_move x , y +mouse_button 1 +mouse_move new_x,new_y +mouse_move 0 + + +The mouse_move 0 doesn't release the mouse in the position new_x,new_y instead it takes it back to the point x,y and then releases the mouse + +Did you mean "mouse_button 0" instead of "mouse_move 0" here? + +[Expired for QEMU because there has been no activity for 60 days.] + diff --git a/results/classifier/118/mistranslation/1662468 b/results/classifier/118/mistranslation/1662468 new file mode 100644 index 000000000..f93272777 --- /dev/null +++ b/results/classifier/118/mistranslation/1662468 @@ -0,0 +1,120 @@ +mistranslation: 0.882 +semantic: 0.725 +graphic: 0.641 +performance: 0.603 +device: 0.476 +hypervisor: 0.456 +architecture: 0.432 +kernel: 0.420 +ppc: 0.410 +register: 0.408 +socket: 0.400 +TCG: 0.325 +network: 0.320 +PID: 0.320 +debug: 0.320 +VMM: 0.298 +user-level: 0.293 +assembly: 0.288 +vnc: 0.284 +x86: 0.281 +files: 0.276 +i386: 0.270 +arm: 0.265 +peripherals: 0.257 +risc-v: 0.239 +permissions: 0.236 +virtual: 0.204 +boot: 0.192 +KVM: 0.188 +-------------------- +user-level: 0.869 +x86: 0.108 +virtual: 0.104 +TCG: 0.075 +files: 0.040 +debug: 0.036 +i386: 0.033 +kernel: 0.030 +VMM: 0.023 +PID: 0.018 +hypervisor: 0.017 +risc-v: 0.014 +device: 0.013 +ppc: 0.011 +arm: 0.008 +performance: 0.007 +semantic: 0.006 +network: 0.006 +boot: 0.006 +socket: 0.006 +register: 0.005 +vnc: 0.005 +peripherals: 0.002 +KVM: 0.002 +mistranslation: 0.001 +architecture: 0.001 +assembly: 0.001 +graphic: 0.001 +permissions: 0.001 + +[feature request] qemu-img convert should respond to control-T like dd + +Since qemu-img convert is a long-running operation, it would be nice if it reported progress in response to control-T (SIGINFO) to show progress information, much like dd, fsck, dump, cp, etc. + +That should be simple enough to implement considering we have this behavior already on SIGUSR1. Unfortunately, I wouldn't be able to test it because Linux apparently doesn't implement SIGINFO... + +Max + + +PS: By the way, thanks for the information. I didn't know about SIGINFO at all. Well, now I have mapped Ctrl-T to SIGUSR1 in my terminal emulator so I don't have to feel quite as inferior... + +On 02/08/17 00:22, Max Reitz wrote: +> That should be simple enough to implement considering we have this +> behavior already on SIGUSR1. Unfortunately, I wouldn't be able to test +> it because Linux apparently doesn't implement SIGINFO... +> +> Max +> +> +> PS: By the way, thanks for the information. I didn't know about SIGINFO at all. Well, now I have mapped Ctrl-T to SIGUSR1 in my terminal emulator so I don't have to feel quite as inferior... +> + +By that you may have lost the following Readline action: + + transpose-chars (C-t) + Drag the character before point forward over the charac- + ter at point, moving point forward as well. If point is + at the end of the line, then this transposes the two + characters before point. Negative arguments have no + effect. + +I'm sure you've been using that all the time... ;) + +Laszlo + + +On Tue, Feb 07, 2017 at 11:22:26PM -0000, Max Reitz wrote: +> That should be simple enough to implement considering we have this +> behavior already on SIGUSR1. Unfortunately, I wouldn't be able to test +> it because Linux apparently doesn't implement SIGINFO... +> +> Max +> +> +> PS: By the way, thanks for the information. I didn't know about SIGINFO at all. Well, now I have mapped Ctrl-T to SIGUSR1 in my terminal emulator so I don't have to feel quite as inferior... + +Christophe: In case you hadn't seen what Max is referring to on the +qemu-img man page: + + -p display progress bar (compare, convert and rebase commands + only). If the -p option is not used for a command that supports + it, the progress is reported when the process receives a + "SIGUSR1" signal. + +Does this do what you want? + + +Fix has been included in v2.10.0: +https://git.qemu.org/?p=qemu.git;a=commitdiff;h=262fbae692722d5c8b + diff --git a/results/classifier/118/mistranslation/1683084 b/results/classifier/118/mistranslation/1683084 new file mode 100644 index 000000000..474372c58 --- /dev/null +++ b/results/classifier/118/mistranslation/1683084 @@ -0,0 +1,76 @@ +mistranslation: 0.802 +graphic: 0.648 +semantic: 0.360 +network: 0.349 +device: 0.342 +user-level: 0.340 +performance: 0.237 +vnc: 0.227 +virtual: 0.204 +VMM: 0.185 +PID: 0.180 +ppc: 0.161 +socket: 0.160 +debug: 0.157 +files: 0.154 +permissions: 0.129 +register: 0.127 +risc-v: 0.120 +x86: 0.102 +hypervisor: 0.097 +i386: 0.086 +TCG: 0.076 +boot: 0.073 +arm: 0.065 +KVM: 0.062 +architecture: 0.061 +peripherals: 0.052 +assembly: 0.037 +kernel: 0.024 +-------------------- +network: 0.976 +user-level: 0.924 +virtual: 0.760 +debug: 0.470 +x86: 0.098 +i386: 0.023 +TCG: 0.017 +hypervisor: 0.011 +socket: 0.008 +arm: 0.007 +kernel: 0.002 +register: 0.001 +ppc: 0.001 +files: 0.001 +performance: 0.001 +semantic: 0.001 +device: 0.001 +risc-v: 0.001 +PID: 0.000 +assembly: 0.000 +vnc: 0.000 +graphic: 0.000 +VMM: 0.000 +architecture: 0.000 +KVM: 0.000 +boot: 0.000 +peripherals: 0.000 +mistranslation: 0.000 +permissions: 0.000 + +DNS server not working in QEMU usermode networking + +Nslookup is returning "unknown host". +I try to ping 10.0.2.3 and it fails. Pinging 10.0.2.2 and 10.0.2.15 works correctly. +Downloading files via wget using a static IP works well. + +Results of qemu monitor command "info network" included as an attachment. + +This bug was reported as a question on stack overflow: http://stackoverflow.com/questions/43308310/dns-server-not-working-in-qemu-usermode-networking. + +This bug exists on 2.8.0 and 2.9-rc3. + + + +User error, this is not a bug + diff --git a/results/classifier/118/mistranslation/1730101 b/results/classifier/118/mistranslation/1730101 new file mode 100644 index 000000000..fc1384877 --- /dev/null +++ b/results/classifier/118/mistranslation/1730101 @@ -0,0 +1,70 @@ +mistranslation: 0.925 +device: 0.893 +performance: 0.827 +boot: 0.815 +graphic: 0.810 +user-level: 0.727 +architecture: 0.650 +semantic: 0.623 +hypervisor: 0.618 +x86: 0.554 +network: 0.512 +risc-v: 0.511 +permissions: 0.505 +virtual: 0.497 +i386: 0.496 +register: 0.488 +PID: 0.429 +ppc: 0.416 +socket: 0.415 +vnc: 0.411 +debug: 0.401 +arm: 0.345 +peripherals: 0.342 +files: 0.319 +assembly: 0.250 +TCG: 0.245 +VMM: 0.198 +kernel: 0.094 +KVM: 0.047 +-------------------- +user-level: 0.974 +virtual: 0.821 +debug: 0.751 +boot: 0.439 +TCG: 0.080 +x86: 0.036 +performance: 0.034 +hypervisor: 0.021 +files: 0.010 +device: 0.007 +semantic: 0.006 +arm: 0.004 +risc-v: 0.004 +socket: 0.003 +i386: 0.003 +PID: 0.003 +network: 0.002 +graphic: 0.002 +vnc: 0.002 +ppc: 0.002 +VMM: 0.002 +kernel: 0.001 +architecture: 0.001 +register: 0.001 +assembly: 0.001 +permissions: 0.001 +peripherals: 0.001 +KVM: 0.000 +mistranslation: 0.000 + +The guest is only starting after its SDL window gets focus + +I’m using i3wm and have workspace assigning rules that make QEMU’s SDL window be assigned to a workspace I don’t really switch to. + +When I run start a guest machine, its SDL window is moved to that workspace (I never see it); but the machine freezes after displaying that black window. It only starts booting after I switch to the workspace and view the window. + +Which version of SDL have you been using here? SDL 1.2 or SDL 2.0? If you were using 1.2, could you please try with 2.0 instead? Support for 1.2 has been removed now. + +[Expired for QEMU because there has been no activity for 60 days.] + diff --git a/results/classifier/118/mistranslation/1777293 b/results/classifier/118/mistranslation/1777293 new file mode 100644 index 000000000..5d3db5cd1 --- /dev/null +++ b/results/classifier/118/mistranslation/1777293 @@ -0,0 +1,73 @@ +mistranslation: 0.920 +semantic: 0.716 +graphic: 0.516 +device: 0.344 +architecture: 0.304 +performance: 0.258 +i386: 0.242 +x86: 0.226 +user-level: 0.217 +virtual: 0.195 +hypervisor: 0.191 +permissions: 0.171 +debug: 0.123 +register: 0.107 +boot: 0.104 +network: 0.101 +vnc: 0.068 +PID: 0.062 +peripherals: 0.048 +kernel: 0.046 +assembly: 0.046 +ppc: 0.044 +arm: 0.044 +risc-v: 0.041 +VMM: 0.034 +TCG: 0.032 +files: 0.028 +socket: 0.025 +KVM: 0.018 +-------------------- +virtual: 0.901 +user-level: 0.897 +hypervisor: 0.409 +semantic: 0.114 +x86: 0.068 +TCG: 0.050 +register: 0.022 +kernel: 0.010 +performance: 0.010 +socket: 0.006 +files: 0.005 +PID: 0.004 +i386: 0.004 +ppc: 0.004 +debug: 0.004 +architecture: 0.003 +device: 0.002 +network: 0.002 +permissions: 0.001 +boot: 0.001 +assembly: 0.001 +VMM: 0.001 +arm: 0.001 +risc-v: 0.001 +graphic: 0.001 +mistranslation: 0.000 +vnc: 0.000 +peripherals: 0.000 +KVM: 0.000 + +[REQUEST] SHARING MEMORY WITH HOST + +Instead of a preallocated memory heap I would like for QEMU to share memory using shm. + +Example: Instead of using 16gb out of 32gb of ram to run Windows 10, there would be no option to allocate it, but to share the hosts resources; ie giving the host full access to the entire ram stack + + +I'm not a great programmer but I'm pretty sure QEMU's team could find this useful + +Sorry, but I have a hard to to imagine what you exactly mean here. Do you mean a possibility for one application in the guest and one in the host to share a piece of memory? Or do you mean that the operating systems in the host and guest should somehow share the memory (why?)? Or do you just look for a possibility to avoid that the guest has a lot of memory allocated to it when it does not need it? In the latter case, there is already virtio-balloon, so you should have a look at the virtio drivers if you need something like this. + +[Expired for QEMU because there has been no activity for 60 days.] + diff --git a/results/classifier/118/mistranslation/1849234 b/results/classifier/118/mistranslation/1849234 new file mode 100644 index 000000000..d184c9e51 --- /dev/null +++ b/results/classifier/118/mistranslation/1849234 @@ -0,0 +1,64 @@ +mistranslation: 0.910 +performance: 0.848 +device: 0.818 +graphic: 0.698 +boot: 0.655 +arm: 0.487 +semantic: 0.477 +network: 0.465 +ppc: 0.456 +files: 0.430 +permissions: 0.409 +peripherals: 0.385 +risc-v: 0.341 +debug: 0.208 +architecture: 0.201 +user-level: 0.173 +register: 0.169 +TCG: 0.146 +hypervisor: 0.098 +virtual: 0.085 +VMM: 0.071 +vnc: 0.054 +socket: 0.050 +PID: 0.048 +i386: 0.046 +x86: 0.033 +assembly: 0.031 +kernel: 0.009 +KVM: 0.002 +-------------------- +boot: 0.965 +user-level: 0.965 +virtual: 0.889 +hypervisor: 0.270 +debug: 0.175 +performance: 0.111 +kernel: 0.046 +device: 0.017 +x86: 0.015 +TCG: 0.014 +semantic: 0.010 +files: 0.010 +PID: 0.005 +socket: 0.004 +assembly: 0.003 +KVM: 0.003 +VMM: 0.002 +graphic: 0.002 +i386: 0.002 +register: 0.001 +network: 0.001 +architecture: 0.001 +arm: 0.001 +peripherals: 0.000 +mistranslation: 0.000 +risc-v: 0.000 +vnc: 0.000 +permissions: 0.000 +ppc: 0.000 + +Macos Catalina bug + +When I want to boot anything with qemu it just stops responding. + diff --git a/results/classifier/118/mistranslation/1903493 b/results/classifier/118/mistranslation/1903493 new file mode 100644 index 000000000..e223b073c --- /dev/null +++ b/results/classifier/118/mistranslation/1903493 @@ -0,0 +1,68 @@ +mistranslation: 0.964 +semantic: 0.867 +user-level: 0.836 +KVM: 0.756 +network: 0.749 +device: 0.719 +graphic: 0.693 +arm: 0.506 +performance: 0.450 +architecture: 0.440 +virtual: 0.413 +i386: 0.399 +peripherals: 0.364 +hypervisor: 0.364 +vnc: 0.360 +socket: 0.359 +kernel: 0.355 +boot: 0.286 +x86: 0.280 +debug: 0.277 +register: 0.270 +PID: 0.261 +assembly: 0.261 +VMM: 0.230 +TCG: 0.227 +risc-v: 0.219 +ppc: 0.216 +files: 0.205 +permissions: 0.143 +-------------------- +user-level: 0.977 +network: 0.971 +KVM: 0.847 +virtual: 0.520 +hypervisor: 0.289 +semantic: 0.155 +peripherals: 0.057 +x86: 0.036 +device: 0.025 +VMM: 0.017 +socket: 0.016 +kernel: 0.007 +risc-v: 0.007 +TCG: 0.006 +ppc: 0.005 +PID: 0.005 +register: 0.005 +files: 0.004 +vnc: 0.004 +architecture: 0.003 +i386: 0.003 +boot: 0.003 +arm: 0.003 +performance: 0.002 +permissions: 0.002 +assembly: 0.002 +debug: 0.002 +mistranslation: 0.001 +graphic: 0.001 + +About wireless network card bridging + +As a rookie, I don’t know if I should ask this question here. If it’s not right, I hope people who see it can help submit it to the right place. Qemu-kvm can add wireless network card bridging, after all, now you see that vbox and vmware can directly choose wireless network card bridging, and even hyper-v can be easily set up, arp proxy is too difficult for us rookies . I hope that qemu or other links can add a function to bridge the wireless network card, which can be directly set in virt-manager (for so many years, it seems that I can only use bridge-utils to bridge the Ethernet) + +Sorry, but at least I have a hard time to understand what you exactly are requesting here? Why should bridging via a wireless card on the host be much different to bridging via an ethernet interface on the host? Or do you expect to see a wireless network card in the guest? + +[Expired for QEMU because there has been no activity for 60 days.] + diff --git a/results/classifier/118/mistranslation/1913315 b/results/classifier/118/mistranslation/1913315 new file mode 100644 index 000000000..252e834e6 --- /dev/null +++ b/results/classifier/118/mistranslation/1913315 @@ -0,0 +1,141 @@ +mistranslation: 0.891 +semantic: 0.873 +user-level: 0.859 +graphic: 0.841 +permissions: 0.835 +virtual: 0.825 +register: 0.790 +debug: 0.785 +peripherals: 0.779 +risc-v: 0.774 +architecture: 0.765 +device: 0.762 +arm: 0.753 +assembly: 0.749 +ppc: 0.742 +hypervisor: 0.739 +TCG: 0.720 +x86: 0.692 +kernel: 0.688 +socket: 0.670 +performance: 0.664 +KVM: 0.660 +PID: 0.659 +vnc: 0.640 +network: 0.609 +boot: 0.600 +VMM: 0.587 +files: 0.587 +i386: 0.383 +-------------------- +x86: 0.980 +kernel: 0.944 +register: 0.902 +debug: 0.640 +hypervisor: 0.191 +virtual: 0.133 +VMM: 0.089 +TCG: 0.087 +assembly: 0.075 +semantic: 0.062 +performance: 0.039 +files: 0.034 +KVM: 0.028 +PID: 0.022 +device: 0.014 +risc-v: 0.013 +boot: 0.012 +architecture: 0.009 +socket: 0.006 +user-level: 0.005 +ppc: 0.003 +graphic: 0.003 +vnc: 0.002 +network: 0.002 +permissions: 0.002 +peripherals: 0.001 +mistranslation: 0.001 +i386: 0.001 +arm: 0.000 + +qemu-system-x86_64 crash: in memory_region_access_valid+0x13 + +Recently we started to get intermittent qemu crashes. There is catchsegv report: + +``` ++ qemu-system-x86_64 -m 77766M -smp 8 -nodefaults -nographic -no-reboot -fsdev local,id=root,path=/,security_model=none,multidevs=remap -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root -device virtio-rng-pci -serial mon:stdio -kernel /usr/src/tmp/kernel-image-rt-buildroot/boot/vmlinuz-4.19.165-rt-alt1.rt70 -initrd /usr/src/tmp/initramfs-4.19.165-rt-alt1.rt70.img -bios bios.bin -append 'console=ttyS0 mitigations=off nokaslr quiet panic=-1 no_timer_check' +*** signal 11 +Register dump: + + RAX: 0000000000000000 RBX: 0000034000000340 RCX: 0000000000000001 + RDX: 0000000000000004 RSI: 0000000000000300 RDI: 0000034000000340 + RBP: 0000000000000300 R8 : 0000000000000000 R9 : 0000034000000340 + R10: 0000000000000370 R11: 0000000000000002 R12: 0000000000000004 + R13: 0000000000000004 R14: 000055b473fef5e0 R15: 0000000000000002 + RSP: 00007fd7edffae90 + + RIP: 000055b4717ef653 EFLAGS: 00010206 + + CS: 0033 FS: 0000 GS: 0000 + + Trap: 0000000e Error: 00000004 OldMask: 7ffbfa77 CR2: 00000388 + + FPUCW: 0000037f FPUSW: 00000000 TAG: 00000000 + RIP: 00000000 RDP: 00000000 + + ST(0) 0000 0000000000000000 ST(1) 0000 0000000000000000 + ST(2) 0000 0000000000000000 ST(3) 0000 0000000000000000 + ST(4) 0000 0000000000000000 ST(5) 0000 0000000000000000 + ST(6) 0000 0000000000000000 ST(7) 0000 0000000000000000 + mxcsr: 1fa0 + XMM0: 00000000000000000000000000000000 XMM1: 00000000000000000000000000000000 + XMM2: 00000000000000000000000000000000 XMM3: 00000000000000000000000000000000 + XMM4: 00000000000000000000000000000000 XMM5: 00000000000000000000000000000000 + XMM6: 00000000000000000000000000000000 XMM7: 00000000000000000000000000000000 + XMM8: 00000000000000000000000000000000 XMM9: 00000000000000000000000000000000 + XMM10: 00000000000000000000000000000000 XMM11: 00000000000000000000000000000000 + XMM12: 00000000000000000000000000000000 XMM13: 00000000000000000000000000000000 + XMM14: 00000000000000000000000000000000 XMM15: 00000000000000000000000000000000 + +Backtrace: +qemu-system-x86_64(memory_region_access_valid+0x13)[0x55b4717ef653] +qemu-system-x86_64(memory_region_dispatch_write+0x48)[0x55b4717ef8c8] +qemu-system-x86_64(+0x69fdfc)[0x55b471851dfc] +qemu-system-x86_64(helper_le_stl_mmu+0x2c5)[0x55b471858995] +[0x7feaed070925] + +``` +QEMU release 5.2.0. + +The QEMU project is currently moving 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 the bug state to "Incomplete" now. + +If the bug has already been fixed in the latest upstream version of QEMU, +then please close this ticket as "Fix released". + +If it is not fixed yet and you think that this bug report here is still +valid, then you have two options: + +1) If you already have an account on gitlab.com, please open a new ticket +for this problem in our new tracker here: + + https://gitlab.com/qemu-project/qemu/-/issues + +and then close this ticket here on Launchpad (or let it expire auto- +matically after 60 days). Please mention the URL of this bug ticket on +Launchpad in the new ticket on GitLab. + +2) If you don't have an account on gitlab.com and don't intend to get +one, but still would like to keep this ticket opened, then please switch +the state back to "New" or "Confirmed" within the next 60 days (other- +wise it will get closed as "Expired"). We will then eventually migrate +the ticket automatically to the new system (but you won't be the reporter +of the bug in the new system and thus you won't get notified on changes +anymore). + +Thank you and sorry for the inconvenience. + + +[Expired for QEMU because there has been no activity for 60 days.] + diff --git a/results/classifier/118/mistranslation/1967 b/results/classifier/118/mistranslation/1967 new file mode 100644 index 000000000..6f005b050 --- /dev/null +++ b/results/classifier/118/mistranslation/1967 @@ -0,0 +1,61 @@ +mistranslation: 0.988 +device: 0.918 +network: 0.818 +performance: 0.729 +graphic: 0.645 +peripherals: 0.550 +arm: 0.543 +semantic: 0.500 +boot: 0.384 +register: 0.376 +files: 0.374 +virtual: 0.353 +permissions: 0.339 +socket: 0.319 +architecture: 0.303 +hypervisor: 0.297 +ppc: 0.268 +debug: 0.233 +x86: 0.181 +risc-v: 0.176 +i386: 0.157 +vnc: 0.129 +assembly: 0.083 +user-level: 0.077 +kernel: 0.075 +PID: 0.033 +VMM: 0.018 +KVM: 0.014 +TCG: 0.006 +-------------------- +network: 0.944 +mistranslation: 0.919 +virtual: 0.509 +permissions: 0.344 +user-level: 0.305 +debug: 0.153 +performance: 0.112 +x86: 0.105 +peripherals: 0.095 +assembly: 0.073 +semantic: 0.057 +device: 0.045 +i386: 0.030 +KVM: 0.017 +kernel: 0.012 +PID: 0.011 +hypervisor: 0.009 +files: 0.007 +vnc: 0.006 +boot: 0.005 +socket: 0.004 +ppc: 0.003 +register: 0.003 +arm: 0.002 +architecture: 0.002 +TCG: 0.002 +graphic: 0.002 +VMM: 0.001 +risc-v: 0.001 + +Guest SIGRTMIN remapped incorrectly diff --git a/results/classifier/118/mistranslation/227 b/results/classifier/118/mistranslation/227 new file mode 100644 index 000000000..b334108b8 --- /dev/null +++ b/results/classifier/118/mistranslation/227 @@ -0,0 +1,61 @@ +mistranslation: 0.993 +semantic: 0.934 +user-level: 0.491 +virtual: 0.444 +graphic: 0.386 +device: 0.329 +peripherals: 0.236 +VMM: 0.231 +files: 0.183 +vnc: 0.163 +assembly: 0.156 +ppc: 0.153 +arm: 0.150 +socket: 0.136 +performance: 0.133 +risc-v: 0.119 +register: 0.084 +architecture: 0.075 +permissions: 0.072 +PID: 0.069 +i386: 0.060 +boot: 0.060 +KVM: 0.054 +TCG: 0.050 +network: 0.040 +x86: 0.039 +hypervisor: 0.037 +debug: 0.028 +kernel: 0.015 +-------------------- +user-level: 0.932 +semantic: 0.916 +virtual: 0.693 +TCG: 0.376 +device: 0.129 +performance: 0.064 +network: 0.036 +peripherals: 0.034 +debug: 0.024 +ppc: 0.023 +VMM: 0.022 +files: 0.021 +register: 0.013 +PID: 0.010 +permissions: 0.007 +assembly: 0.007 +boot: 0.006 +mistranslation: 0.005 +KVM: 0.004 +x86: 0.003 +kernel: 0.003 +vnc: 0.003 +i386: 0.002 +architecture: 0.002 +risc-v: 0.001 +arm: 0.001 +socket: 0.001 +hypervisor: 0.001 +graphic: 0.000 + +meson: incomplete 'make help' diff --git a/results/classifier/118/mistranslation/244 b/results/classifier/118/mistranslation/244 new file mode 100644 index 000000000..98447380e --- /dev/null +++ b/results/classifier/118/mistranslation/244 @@ -0,0 +1,61 @@ +mistranslation: 0.961 +device: 0.771 +semantic: 0.751 +performance: 0.673 +architecture: 0.476 +virtual: 0.476 +graphic: 0.460 +network: 0.376 +peripherals: 0.310 +user-level: 0.299 +register: 0.264 +permissions: 0.237 +hypervisor: 0.197 +assembly: 0.193 +socket: 0.193 +risc-v: 0.169 +arm: 0.162 +files: 0.152 +vnc: 0.151 +debug: 0.148 +boot: 0.122 +i386: 0.070 +ppc: 0.067 +VMM: 0.058 +kernel: 0.052 +TCG: 0.043 +PID: 0.037 +KVM: 0.016 +x86: 0.015 +-------------------- +architecture: 0.906 +device: 0.845 +assembly: 0.461 +performance: 0.354 +virtual: 0.229 +semantic: 0.132 +files: 0.112 +permissions: 0.043 +debug: 0.035 +peripherals: 0.029 +kernel: 0.024 +register: 0.019 +network: 0.016 +user-level: 0.013 +hypervisor: 0.012 +mistranslation: 0.009 +boot: 0.007 +VMM: 0.006 +graphic: 0.002 +socket: 0.001 +PID: 0.001 +TCG: 0.001 +arm: 0.001 +vnc: 0.000 +KVM: 0.000 +risc-v: 0.000 +ppc: 0.000 +i386: 0.000 +x86: 0.000 + +MIPS MT dvpe does not regard VPEConf0.MVP diff --git a/results/classifier/118/mistranslation/2614 b/results/classifier/118/mistranslation/2614 new file mode 100644 index 000000000..79b1f839a --- /dev/null +++ b/results/classifier/118/mistranslation/2614 @@ -0,0 +1,61 @@ +mistranslation: 0.980 +user-level: 0.788 +device: 0.602 +virtual: 0.504 +semantic: 0.421 +network: 0.407 +register: 0.402 +debug: 0.290 +arm: 0.251 +files: 0.234 +ppc: 0.231 +permissions: 0.231 +graphic: 0.187 +TCG: 0.147 +PID: 0.136 +performance: 0.136 +VMM: 0.132 +boot: 0.129 +risc-v: 0.119 +i386: 0.077 +socket: 0.064 +x86: 0.046 +architecture: 0.046 +vnc: 0.036 +assembly: 0.028 +peripherals: 0.024 +KVM: 0.009 +kernel: 0.007 +hypervisor: 0.001 +-------------------- +user-level: 0.998 +virtual: 0.965 +network: 0.865 +register: 0.686 +hypervisor: 0.174 +semantic: 0.123 +permissions: 0.071 +KVM: 0.048 +files: 0.048 +TCG: 0.016 +x86: 0.011 +boot: 0.007 +risc-v: 0.007 +assembly: 0.007 +ppc: 0.006 +VMM: 0.006 +mistranslation: 0.006 +performance: 0.005 +device: 0.005 +arm: 0.005 +i386: 0.004 +debug: 0.004 +socket: 0.004 +vnc: 0.004 +architecture: 0.003 +kernel: 0.002 +peripherals: 0.002 +graphic: 0.002 +PID: 0.002 + +vhost user documentation for VHOST_USER_ADD_MEM_REG incorrect diff --git a/results/classifier/118/mistranslation/356 b/results/classifier/118/mistranslation/356 new file mode 100644 index 000000000..5090688f5 --- /dev/null +++ b/results/classifier/118/mistranslation/356 @@ -0,0 +1,61 @@ +mistranslation: 0.984 +user-level: 0.756 +network: 0.747 +device: 0.704 +performance: 0.559 +peripherals: 0.500 +socket: 0.412 +semantic: 0.377 +graphic: 0.365 +arm: 0.351 +architecture: 0.344 +PID: 0.318 +boot: 0.266 +permissions: 0.266 +register: 0.255 +virtual: 0.232 +debug: 0.186 +i386: 0.177 +vnc: 0.165 +ppc: 0.145 +files: 0.136 +VMM: 0.125 +kernel: 0.120 +TCG: 0.079 +hypervisor: 0.072 +x86: 0.034 +risc-v: 0.025 +assembly: 0.016 +KVM: 0.005 +-------------------- +virtual: 0.939 +user-level: 0.895 +hypervisor: 0.780 +kernel: 0.100 +semantic: 0.046 +TCG: 0.038 +x86: 0.020 +performance: 0.019 +network: 0.018 +KVM: 0.017 +debug: 0.015 +device: 0.014 +VMM: 0.013 +files: 0.012 +i386: 0.010 +socket: 0.008 +register: 0.008 +assembly: 0.006 +mistranslation: 0.005 +peripherals: 0.005 +architecture: 0.003 +PID: 0.003 +graphic: 0.002 +ppc: 0.002 +risc-v: 0.002 +boot: 0.002 +arm: 0.001 +vnc: 0.001 +permissions: 0.001 + +qemu linux-user doesn't translate host/target data for iovec I/O diff --git a/results/classifier/118/mistranslation/378 b/results/classifier/118/mistranslation/378 new file mode 100644 index 000000000..da917deed --- /dev/null +++ b/results/classifier/118/mistranslation/378 @@ -0,0 +1,61 @@ +mistranslation: 0.887 +graphic: 0.544 +semantic: 0.517 +device: 0.507 +architecture: 0.457 +network: 0.408 +peripherals: 0.398 +hypervisor: 0.390 +permissions: 0.353 +debug: 0.345 +register: 0.339 +x86: 0.328 +user-level: 0.308 +performance: 0.299 +PID: 0.295 +vnc: 0.279 +TCG: 0.274 +risc-v: 0.267 +virtual: 0.265 +ppc: 0.252 +files: 0.249 +KVM: 0.234 +kernel: 0.231 +i386: 0.229 +VMM: 0.221 +arm: 0.217 +boot: 0.185 +socket: 0.118 +assembly: 0.050 +-------------------- +architecture: 0.978 +user-level: 0.778 +semantic: 0.691 +virtual: 0.257 +assembly: 0.056 +peripherals: 0.048 +PID: 0.034 +mistranslation: 0.014 +debug: 0.010 +files: 0.009 +register: 0.008 +performance: 0.007 +device: 0.007 +VMM: 0.005 +kernel: 0.005 +KVM: 0.004 +ppc: 0.003 +TCG: 0.002 +network: 0.002 +i386: 0.002 +risc-v: 0.002 +socket: 0.002 +hypervisor: 0.001 +boot: 0.001 +graphic: 0.001 +x86: 0.001 +vnc: 0.001 +permissions: 0.000 +arm: 0.000 + +Indentation should be done with spaces, not with TABs diff --git a/results/classifier/118/mistranslation/426 b/results/classifier/118/mistranslation/426 new file mode 100644 index 000000000..5090688f5 --- /dev/null +++ b/results/classifier/118/mistranslation/426 @@ -0,0 +1,61 @@ +mistranslation: 0.984 +user-level: 0.756 +network: 0.747 +device: 0.704 +performance: 0.559 +peripherals: 0.500 +socket: 0.412 +semantic: 0.377 +graphic: 0.365 +arm: 0.351 +architecture: 0.344 +PID: 0.318 +boot: 0.266 +permissions: 0.266 +register: 0.255 +virtual: 0.232 +debug: 0.186 +i386: 0.177 +vnc: 0.165 +ppc: 0.145 +files: 0.136 +VMM: 0.125 +kernel: 0.120 +TCG: 0.079 +hypervisor: 0.072 +x86: 0.034 +risc-v: 0.025 +assembly: 0.016 +KVM: 0.005 +-------------------- +virtual: 0.939 +user-level: 0.895 +hypervisor: 0.780 +kernel: 0.100 +semantic: 0.046 +TCG: 0.038 +x86: 0.020 +performance: 0.019 +network: 0.018 +KVM: 0.017 +debug: 0.015 +device: 0.014 +VMM: 0.013 +files: 0.012 +i386: 0.010 +socket: 0.008 +register: 0.008 +assembly: 0.006 +mistranslation: 0.005 +peripherals: 0.005 +architecture: 0.003 +PID: 0.003 +graphic: 0.002 +ppc: 0.002 +risc-v: 0.002 +boot: 0.002 +arm: 0.001 +vnc: 0.001 +permissions: 0.001 + +qemu linux-user doesn't translate host/target data for iovec I/O diff --git a/results/classifier/118/mistranslation/508 b/results/classifier/118/mistranslation/508 new file mode 100644 index 000000000..842f93cb5 --- /dev/null +++ b/results/classifier/118/mistranslation/508 @@ -0,0 +1,61 @@ +mistranslation: 0.964 +architecture: 0.915 +device: 0.838 +TCG: 0.740 +performance: 0.638 +network: 0.591 +graphic: 0.501 +virtual: 0.350 +x86: 0.335 +arm: 0.266 +semantic: 0.261 +files: 0.257 +debug: 0.244 +register: 0.228 +kernel: 0.223 +boot: 0.211 +risc-v: 0.191 +permissions: 0.187 +hypervisor: 0.157 +ppc: 0.102 +VMM: 0.098 +assembly: 0.091 +peripherals: 0.087 +vnc: 0.078 +socket: 0.066 +user-level: 0.053 +PID: 0.050 +i386: 0.009 +KVM: 0.009 +-------------------- +virtual: 0.964 +TCG: 0.948 +x86: 0.796 +hypervisor: 0.776 +architecture: 0.325 +user-level: 0.217 +assembly: 0.140 +KVM: 0.059 +kernel: 0.050 +device: 0.036 +semantic: 0.035 +debug: 0.032 +files: 0.023 +register: 0.019 +performance: 0.017 +VMM: 0.016 +socket: 0.013 +PID: 0.008 +boot: 0.006 +graphic: 0.003 +peripherals: 0.003 +risc-v: 0.002 +mistranslation: 0.001 +ppc: 0.001 +vnc: 0.001 +permissions: 0.001 +network: 0.001 +i386: 0.000 +arm: 0.000 + +x86_64 cmpxchg behavior in qemu tcg does not match the real CPU diff --git a/results/classifier/118/mistranslation/629791 b/results/classifier/118/mistranslation/629791 new file mode 100644 index 000000000..abbd36d1d --- /dev/null +++ b/results/classifier/118/mistranslation/629791 @@ -0,0 +1,68 @@ +mistranslation: 0.911 +architecture: 0.901 +user-level: 0.892 +device: 0.848 +semantic: 0.806 +graphic: 0.765 +debug: 0.654 +performance: 0.632 +register: 0.617 +risc-v: 0.569 +i386: 0.555 +x86: 0.552 +peripherals: 0.515 +kernel: 0.503 +arm: 0.487 +socket: 0.447 +PID: 0.422 +boot: 0.420 +vnc: 0.417 +virtual: 0.404 +network: 0.381 +ppc: 0.357 +hypervisor: 0.342 +VMM: 0.304 +permissions: 0.300 +files: 0.264 +TCG: 0.255 +assembly: 0.244 +KVM: 0.142 +-------------------- +debug: 0.986 +register: 0.921 +x86: 0.916 +kernel: 0.840 +assembly: 0.827 +virtual: 0.183 +hypervisor: 0.108 +TCG: 0.041 +i386: 0.040 +arm: 0.015 +user-level: 0.008 +PID: 0.005 +risc-v: 0.005 +performance: 0.005 +semantic: 0.004 +architecture: 0.004 +device: 0.004 +files: 0.004 +ppc: 0.004 +KVM: 0.002 +boot: 0.002 +network: 0.002 +VMM: 0.001 +graphic: 0.001 +socket: 0.001 +permissions: 0.001 +peripherals: 0.000 +vnc: 0.000 +mistranslation: 0.000 + +sysret sets invalid ss + +I'm developing an OS. I use only sysret to enter user space. When an interrupt occurred, it would GPF on iretq'ing from it. On investigating, the cs on the stack is 0x2b (valid and correct). The ss on the stack is 0x20, which has a rpl of 0 which is incorrect. iretq checks that and gpf's. Making the irq handler manually modify it to 0x23 fixes it locally. + +This happens on the non-kvm'ed qemu. I haven't tried the kvm'ed one. Qemu version 0.12.5. I haven't tried with the current development version either. + +Minor update, I found that I made a mistake with the value in STAR. I loaded 0x18 into the top 16 bits, so the bug is not that SS is 0x20 (which I thought to be wrong but was my own mistake). Why does it set CS=0x2b from that value & run? + diff --git a/results/classifier/118/mistranslation/657 b/results/classifier/118/mistranslation/657 new file mode 100644 index 000000000..9b40c4ada --- /dev/null +++ b/results/classifier/118/mistranslation/657 @@ -0,0 +1,61 @@ +mistranslation: 0.856 +semantic: 0.830 +device: 0.713 +architecture: 0.538 +arm: 0.458 +performance: 0.448 +network: 0.385 +permissions: 0.379 +virtual: 0.341 +graphic: 0.340 +TCG: 0.297 +user-level: 0.275 +VMM: 0.253 +kernel: 0.236 +boot: 0.206 +ppc: 0.203 +files: 0.199 +debug: 0.193 +hypervisor: 0.170 +PID: 0.161 +peripherals: 0.159 +register: 0.129 +vnc: 0.120 +risc-v: 0.114 +KVM: 0.101 +socket: 0.100 +i386: 0.066 +assembly: 0.063 +x86: 0.010 +-------------------- +virtual: 0.974 +hypervisor: 0.913 +TCG: 0.875 +boot: 0.810 +kernel: 0.192 +x86: 0.182 +semantic: 0.071 +debug: 0.063 +user-level: 0.035 +performance: 0.018 +VMM: 0.014 +device: 0.013 +files: 0.006 +PID: 0.005 +i386: 0.004 +KVM: 0.003 +assembly: 0.002 +graphic: 0.002 +register: 0.002 +architecture: 0.002 +socket: 0.001 +risc-v: 0.001 +network: 0.001 +peripherals: 0.000 +vnc: 0.000 +mistranslation: 0.000 +permissions: 0.000 +arm: 0.000 +ppc: 0.000 + +qemu no valid state has been set by load or init-program Mac OS X Tiger diff --git a/results/classifier/118/mistranslation/658904 b/results/classifier/118/mistranslation/658904 new file mode 100644 index 000000000..6c73f966b --- /dev/null +++ b/results/classifier/118/mistranslation/658904 @@ -0,0 +1,69 @@ +mistranslation: 0.932 +semantic: 0.795 +network: 0.741 +virtual: 0.574 +device: 0.540 +socket: 0.483 +graphic: 0.420 +register: 0.311 +boot: 0.281 +kernel: 0.228 +ppc: 0.221 +arm: 0.219 +i386: 0.215 +files: 0.188 +debug: 0.179 +x86: 0.132 +risc-v: 0.118 +architecture: 0.114 +user-level: 0.107 +performance: 0.098 +hypervisor: 0.065 +peripherals: 0.063 +permissions: 0.057 +TCG: 0.056 +vnc: 0.049 +assembly: 0.035 +KVM: 0.034 +PID: 0.026 +VMM: 0.016 +-------------------- +network: 0.965 +semantic: 0.943 +user-level: 0.762 +hypervisor: 0.581 +x86: 0.206 +TCG: 0.082 +files: 0.047 +virtual: 0.024 +register: 0.023 +device: 0.021 +socket: 0.008 +architecture: 0.008 +kernel: 0.007 +debug: 0.006 +i386: 0.006 +ppc: 0.004 +mistranslation: 0.003 +assembly: 0.002 +arm: 0.002 +risc-v: 0.002 +PID: 0.002 +boot: 0.002 +performance: 0.002 +peripherals: 0.001 +VMM: 0.001 +graphic: 0.001 +KVM: 0.001 +permissions: 0.001 +vnc: 0.001 + +QEMU refers to VLAN, but doesn't mean 802.1Q + +Throughout the (sparse) documentation and the cmd-line help text, Qemu refers to VLAN ("virtual" LANs), which are unrelated to 802.1Q (tagged ethernet) VLAN, which, IMHO is _very_ confusing. Beyond that, it's also unnecessary, as the network in question isn't "virtual", only the devices used to implement it are. + +To avoid further frustration and confusion, can the term VLAN, _please_ be removed from source and documentation and replaced with something more suitable? Perhaps vNIC (seems like VMware is using that term for a similiar concept)? + +This issue has finally been addressed here: +https://git.qemu.org/?p=qemu.git;a=commitdiff;h=af1a5c3eb41521b4f090ad61 + diff --git a/results/classifier/118/mistranslation/704 b/results/classifier/118/mistranslation/704 new file mode 100644 index 000000000..300c83088 --- /dev/null +++ b/results/classifier/118/mistranslation/704 @@ -0,0 +1,61 @@ +mistranslation: 0.995 +user-level: 0.941 +debug: 0.838 +graphic: 0.521 +architecture: 0.490 +performance: 0.456 +device: 0.449 +boot: 0.319 +semantic: 0.290 +virtual: 0.142 +peripherals: 0.088 +TCG: 0.083 +assembly: 0.078 +register: 0.071 +files: 0.056 +arm: 0.053 +permissions: 0.042 +network: 0.038 +kernel: 0.035 +ppc: 0.032 +VMM: 0.026 +PID: 0.025 +KVM: 0.023 +x86: 0.021 +vnc: 0.015 +i386: 0.013 +socket: 0.005 +hypervisor: 0.002 +risc-v: 0.002 +-------------------- +user-level: 0.918 +debug: 0.409 +kernel: 0.270 +x86: 0.203 +virtual: 0.033 +assembly: 0.030 +TCG: 0.024 +semantic: 0.019 +files: 0.018 +device: 0.010 +architecture: 0.007 +i386: 0.006 +performance: 0.005 +ppc: 0.004 +VMM: 0.004 +KVM: 0.003 +arm: 0.002 +register: 0.002 +boot: 0.002 +PID: 0.002 +graphic: 0.002 +mistranslation: 0.001 +peripherals: 0.001 +hypervisor: 0.001 +network: 0.001 +risc-v: 0.001 +socket: 0.000 +vnc: 0.000 +permissions: 0.000 + +linux-user: misaligned address for type 'struct linux_dirent64' diff --git a/results/classifier/118/mistranslation/77 b/results/classifier/118/mistranslation/77 new file mode 100644 index 000000000..a638d0a6e --- /dev/null +++ b/results/classifier/118/mistranslation/77 @@ -0,0 +1,61 @@ +mistranslation: 0.980 +virtual: 0.648 +debug: 0.630 +files: 0.526 +graphic: 0.499 +semantic: 0.491 +register: 0.480 +PID: 0.420 +device: 0.380 +performance: 0.371 +peripherals: 0.361 +user-level: 0.314 +VMM: 0.313 +boot: 0.296 +network: 0.289 +permissions: 0.275 +TCG: 0.184 +risc-v: 0.181 +KVM: 0.062 +ppc: 0.059 +architecture: 0.057 +vnc: 0.053 +assembly: 0.052 +hypervisor: 0.050 +i386: 0.022 +socket: 0.013 +kernel: 0.012 +arm: 0.003 +x86: 0.002 +-------------------- +user-level: 0.910 +virtual: 0.872 +device: 0.833 +peripherals: 0.763 +semantic: 0.072 +network: 0.039 +performance: 0.023 +debug: 0.023 +vnc: 0.015 +PID: 0.011 +files: 0.010 +permissions: 0.007 +KVM: 0.006 +boot: 0.005 +hypervisor: 0.002 +TCG: 0.002 +x86: 0.002 +assembly: 0.002 +VMM: 0.001 +i386: 0.001 +mistranslation: 0.001 +ppc: 0.001 +socket: 0.001 +arm: 0.001 +kernel: 0.001 +register: 0.000 +risc-v: 0.000 +architecture: 0.000 +graphic: 0.000 + +msmouse not recognized in guest diff --git a/results/classifier/118/mistranslation/886147 b/results/classifier/118/mistranslation/886147 new file mode 100644 index 000000000..1eff487c2 --- /dev/null +++ b/results/classifier/118/mistranslation/886147 @@ -0,0 +1,74 @@ +mistranslation: 0.938 +user-level: 0.926 +semantic: 0.797 +graphic: 0.790 +device: 0.771 +virtual: 0.518 +performance: 0.403 +peripherals: 0.378 +arm: 0.320 +network: 0.310 +debug: 0.309 +architecture: 0.303 +socket: 0.270 +permissions: 0.258 +register: 0.216 +hypervisor: 0.215 +ppc: 0.201 +risc-v: 0.200 +x86: 0.194 +vnc: 0.193 +assembly: 0.191 +files: 0.142 +i386: 0.129 +PID: 0.127 +boot: 0.113 +kernel: 0.085 +TCG: 0.064 +VMM: 0.055 +KVM: 0.019 +-------------------- +user-level: 0.998 +semantic: 0.131 +virtual: 0.123 +x86: 0.037 +files: 0.020 +network: 0.015 +hypervisor: 0.007 +device: 0.003 +peripherals: 0.003 +register: 0.002 +ppc: 0.002 +arm: 0.002 +TCG: 0.001 +debug: 0.001 +PID: 0.001 +boot: 0.001 +i386: 0.001 +performance: 0.001 +graphic: 0.001 +socket: 0.001 +mistranslation: 0.001 +kernel: 0.001 +permissions: 0.000 +assembly: 0.000 +architecture: 0.000 +risc-v: 0.000 +VMM: 0.000 +KVM: 0.000 +vnc: 0.000 + +Cannot make program Icon on my desktop with rightmouse key + +Howdy Xubuntu users + +How can I make a "starter program Icon on my desktop" with the mouse command right key. + +I do not seen the commands when I hit the right key of my mouse. + +Hope to see some info in my pigeon-hole. + +Spidey-Westland + +This apparently has nothing to do with QEMU. Closing. + |