4 files changed, 335 insertions, 0 deletions
diff --git a/results/classifier/108/other/1839 b/results/classifier/108/other/1839
new file mode 100644
index 000000000..b6d2f5a2f
--- /dev/null
+++ b/results/classifier/108/other/1839
@@ -0,0 +1,56 @@
+device: 0.874
+boot: 0.751
+KVM: 0.669
+graphic: 0.606
+network: 0.588
+semantic: 0.540
+other: 0.484
+vnc: 0.483
+debug: 0.476
+PID: 0.459
+performance: 0.450
+socket: 0.411
+permissions: 0.164
+files: 0.016
+
+command line option (fw_cfg) not being treated as opaque and generates error "short-form boolean option 'x' deprecated"
+Description of problem:
+I'm trying to run qemu with `fw_cfg` arguments. With a full example I am trying to provide an ignition configuration a flatcar VM using a 'string' parameter which is JSON (rather than a file parameter).
+
+Running qemu with command line options where the fields have arbitrary data that should be opaque to qemu are being interpreted and cause the command line argument parsing the fail. I have tried putting quotes and double quotes around various parts of the command without success.
+
+
+Sorry, but I haven't tested this with latest (v8.1.0.rc4 / v8.0.4)
+
+Examples:
+
+```# qemu-system-x86_64 -fw_cfg name=z,string=a,b
+qemu-system-x86_64: -fw_cfg name=z,string=a,b: warning: short-form boolean option 'b' deprecated
+Please use b=on instead
+qemu-system-x86_64: -fw_cfg name=z,string=a,b: Invalid parameter 'b'
+```
+
+Single quotes around the `string` value:
+```
+# qemu-system-x86_64 -fw_cfg name=z,string='a,b'
+qemu-system-x86_64: -fw_cfg name=z,string=a,b: warning: short-form boolean option 'b' deprecated
+Please use b=on instead
+qemu-system-x86_64: -fw_cfg name=z,string=a,b: Invalid parameter 'b'
+```
+
+Double quotes around the `string` value
+```
+# qemu-system-x86_64 -fw_cfg name=z,string="a,b"
+qemu-system-x86_64: -fw_cfg name=z,string=a,b: warning: short-form boolean option 'b' deprecated
+Please use b=on instead
+qemu-system-x86_64: -fw_cfg name=z,string=a,b: Invalid parameter 'b'
+
+```
+
+Double quotes around the whole `fw_cfg` option value:
+```
+# qemu-system-x86_64 -fw_cfg "name=z,string=a,b"
+qemu-system-x86_64: -fw_cfg name=z,string=a,b: warning: short-form boolean option 'b' deprecated
+Please use b=on instead
+qemu-system-x86_64: -fw_cfg name=z,string=a,b: Invalid parameter 'b'
+```
diff --git a/results/classifier/108/other/1839294 b/results/classifier/108/other/1839294
new file mode 100644
index 000000000..eb2a073b0
--- /dev/null
+++ b/results/classifier/108/other/1839294
@@ -0,0 +1,42 @@
+graphic: 0.865
+files: 0.821
+device: 0.720
+semantic: 0.671
+performance: 0.595
+other: 0.575
+socket: 0.448
+network: 0.401
+permissions: 0.384
+vnc: 0.376
+PID: 0.356
+boot: 0.268
+debug: 0.200
+KVM: 0.182
+
+Latest Installer (qemu-w64-setup-20190807.exe) for windows immediately deletes installed files at the very end of the installation
+
+This happens on Windows 10 with the latest installer for 64 bit Windows: qemu-w64-setup-20190807.exe
+
+On install it will create the files and go through all the typical functions of installing the software, at the very end step it will then delete all files the installer created.
+
+I looked for logs to see when was going on so I ran the installation in Sandboxie and was able to retain all the installed files but I couldn't find a log for the installer.
+
+Here is a screenshot of it deleting all the files at the end of the process.
+
+https://imgur.com/BWiTA38
+
+If goes too fast for me to see what is written in the text console otherwise I would post more information but this is all I have. It does not give any error or any other information at completion.
+
+This error does not occur in the earlier release: qemu-w64-setup-20190731.exe
+
+
+
+I hit the same error in my azure pipelines script that uses `choco install qemu`. While it worked with qemu-w64-setup-20190731.exe, the `C:\Program Files\qemu` directory is empty with qemu-w64-setup-20190807.exe.
+
+We can forget this one if nothing happens from now on; however, this problem might have a rare but systemic problem. We can always wait and see if this problem is ever duplicated. In which case there is at least a commonality to the bug.
+
+Looking through 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/108/other/1839325 b/results/classifier/108/other/1839325
new file mode 100644
index 000000000..1a70cfe3e
--- /dev/null
+++ b/results/classifier/108/other/1839325
@@ -0,0 +1,115 @@
+other: 0.959
+vnc: 0.937
+permissions: 0.936
+performance: 0.928
+debug: 0.923
+KVM: 0.921
+network: 0.917
+graphic: 0.914
+semantic: 0.914
+socket: 0.909
+device: 0.908
+boot: 0.890
+PID: 0.888
+files: 0.860
+
+Go programs crash on qemu-sh4 due to issues with atomics
+
+After #1738545 [1] was fixed, Go applications work fine on qemu-arm but still crash on qemu-sh4. From the backtrace, it looks like an issue with the atomics in qemu-sh4:
+
+(sid-sh4-sbuild)root@epyc:/# cat hello.go
+package main
+
+import "fmt"
+
+func main() {
+      fmt.Println("hello world")
+}
+
+(sid-sh4-sbuild)root@epyc:/# gccgo-9 hello.go -o hello
+(sid-sh4-sbuild)root@epyc:/# ./hello 
+panic: (        runtime runtime.errorString) (0x7f74527c,0x80a038)
+fatal error: panic on system stack
+panic: (        runtime runtime.errorString) (0x7f74527c,0x80a038)
+fatal error: panic on system stack
+
+runtime stack:
+runtime..z2finternal..z2fatomic.Load64
+        ../../../src/libgo/go/runtime/internal/atomic/atomic.c:37
+runtime_mstart
+        ../../../src/libgo/runtime/proc.c:596
+
+goroutine 1 [running]:
+        goroutine running on other thread; stack unavailable
+
+runtime stack:
+runtime..z2finternal..z2fatomic.Load64
+        ../../../src/libgo/go/runtime/internal/atomic/atomic.c:37
+runtime_mstart
+        ../../../src/libgo/runtime/proc.c:596
+(sid-sh4-sbuild)root@epyc:/#
+
+The same sample Go program runs fine on my SH7785LCR SH4 evaluation board:
+
+root@tirpitz:~> uname -a
+Linux tirpitz 3.16.7-ckt7 #8 PREEMPT Fri Oct 21 18:47:41 CEST 2016 sh4a GNU/Linux
+root@tirpitz:~> cat hello.go
+package main
+
+import "fmt"
+
+func main() {
+      fmt.Println("hello world")
+}
+
+root@tirpitz:~> gccgo-9 hello.go -o hello
+root@tirpitz:~> ./hello 
+hello world
+root@tirpitz:~>
+
+Please note: In order to be able to reproduce this, one also needs to revert commit 61dedf2af7 [2], otherwise the Go application crashes differently:
+
+(sid-sh4-sbuild)root@epyc:/# ./hello        
+Unhandled trap: 0x180
+pc=0x7e5f7f9e sr=0x00000000 pr=0x7ee3d582 fpscr=0x00080004
+spc=0x00000000 ssr=0x00000000 gbr=0x7e590480 vbr=0x00000000
+sgr=0x00000000 dbr=0x00000000 delayed_pc=0x7e5f7f60 fpul=0x00034f3b
+r0=0x008007d4 r1=0x00000000 r2=0xfffe0b2a r3=0x00000002
+r4=0x008006e4 r5=0x00872000 r6=0x00200000 r7=0x00000000
+r8=0x7f7bca7c r9=0x7fffebd4 r10=0x00800480 r11=0x7f7bc0f0
+r12=0x7f7a3fa4 r13=0x008004c0 r14=0x7f7b2238 r15=0x7fffebd0
+r16=0x00000000 r17=0x00000000 r18=0x00000000 r19=0x00000000
+r20=0x00000000 r21=0x00000000 r22=0x00000000 r23=0x00000000
+(sid-sh4-sbuild)root@epyc:/#
+
+> [1] https://bugs.launchpad.net/bugs/1738545
+> [2] https://bugs.launchpad.net/bugs/1796520
+
+The immediate cause of the crash here is that the runtime invokes the Load64() function on a pointer that isn't 8-aligned, which triggers a hand-coded check-and-panic in the libgo code. I haven't yet tracked down where that pointer came from.
+
+
+The non-8-aligned pointer is the runtime.work.empty field. The compilation that I have of this binary has put the 'runtime.work' struct at 0x6bfadc, which is only 4-aligned, and this won't work as the lfstack fields it starts with are supposed to be 8-aligned. So it looks to me like the compiler has miscompiled the binary somehow, and QEMU's actual execution of it is OK.
+
+I don't know if this is a general bug in the sh4 gccgo support (in which case we must be succeeding on the real hardware by accident, probably by finishing fast enough that the gc never kicks in), or if QEMU is mis-executing the compiler somehow and a build done on the real hardware puts the work struct at an 8-aligned address.
+
+
+I just did an objdump -x of the /usr/lib/sh4-linux-gnu/libgo.so.14, which will be the shipped version from the Debian package, and in the section header it has:
+
+ 24 .bss          000191f8  00fe74ec  00fe74ec  00fd74ec  2**2
+                  ALLOC
+
+and in the symbol table it has:
+
+00ff98f4 l     O .bss   00000104              runtime.work
+
+So the compiler has put the 'runtime.work' struct at a non-multiple-of-8 offset into the bss, and it's given the BSS alignment requirements that are only 4-aligned, not 8-aligned. That means it's random luck whether the struct gets 8-aligned or not.
+
+This looks to me like it's a bug in the sh4 gccgo -- https://go101.org/article/memory-layout.html says that the first word in a struct or variable is supposed to be guaranteed to be 8-aligned, so the compiler needs to align things more strictly than it is currently doing.
+
+
+Thanks. I will report this to Go/gcc upstream.
+
+I'm going to close this bug, since it's a problem with the gccgo codegen, not a QEMU bug. (I'm interested in any response you get from the go/gcc upstream folks, though.)
+
+
+
diff --git a/results/classifier/108/other/1839807 b/results/classifier/108/other/1839807
new file mode 100644
index 000000000..58ed2d27e
--- /dev/null
+++ b/results/classifier/108/other/1839807
@@ -0,0 +1,122 @@
+debug: 0.776
+graphic: 0.714
+files: 0.652
+PID: 0.627
+vnc: 0.605
+boot: 0.598
+device: 0.590
+network: 0.589
+semantic: 0.587
+permissions: 0.576
+performance: 0.566
+KVM: 0.566
+other: 0.564
+socket: 0.294
+
+Snapshots freeze guest Sabrelite IMX.6 board
+
+Hello,
+
+I'm trying to take and restore  a snapshot with the whole system state of the Sabrelite IMX.6 board running on QEMU with commands savevm/loadvm.
+It seems that I am able to take a snapshot but loading the snapshot fails.
+
+For comparison I checked out snapshots on 32bit ARM Virt with Debian as well as on the Versatilepb board with a bare metal application and it works fine.
+The problem occurs only with that one particular board.
+
+My environment is:
+Ubuntu 18.04
+QEMU 3.0.1 (I see the same issue in QEMU 4.0.0 as well)
+The kernel and device tree used for the board was 5.1.14 version from kernel.org
+
+The file system was build from imx_v6_v7_defconfig config in buildroot as and sd card image.
+
+Problem:
+
+Loading snapshot stops the whole machine and it's impossible to resume it.
+
+Steps to reproduce problem:
+
+1.      I converted the sdcard.img built from the buildroot to qcow2 using command qemu-img convert -f raw -O qcow2 sdcard.img sdcard.qcow2, since the raw doesn't support snapshots.
+
+2.      I start QEMU with a command
+./arm-softmmu/qemu-system-arm -m 512 -M sabrelite -kernel zImage -append "rootfstype=ext4 root=/dev/mmcblk2p2 rw rootwait" -rtc base=localtime,clock=vm -dtb imx6dl-sabresd.dtb -drive file=sdcard.qcow2,index=2,format=qcow2,id=mycard -device sd-card,drive=mycard -nographic -net nic -net user
+
+3.      I run a simple program which print characters to the console in the background and add some files in user directory, to differ from original image.
+
+4.      I switch to QEMU monitor, and type “savevm <name>”.
+When I type “info snapshots”, the snapshot is listed.
+So I assume it was saved correctly.
+
+5.      Then I switch back to Linux console from monitor, remove the added files and stop the background printing process.
+
+6.      I switch back to monitor and I'm trying now to load the snapshot by “loadvm <name>” command. 
+
+That’s where the problem occurs. QEMU stops and I can't switch back from monitor to Linux.
+Typing “cont” doesn’t help.
+It seems like the simulation has freezed. CPU usage on my Laptop machine equals 100% until I exit QEMU.
+
+
+What’s interesting when I exit the QEMU and then start it again the Linux boots and after it reaches the command prompt I can see the files which were removed after saving the snapshot.
+
+It looks like loading the snapshots works for restoring disk space but it fails for restoring the running processes.
+
+Due to the answer on QEMU mailing list (https://lists.nongnu.org/archive/html/qemu-discuss/2019-08/msg00016.html) it is QEMUs bug.
+
+The underlying cause of this is that we're not migrating the Secure banked cp15 register contents. So boards which don't enable TrustZone or where the guest runs in the NonSecure state (like the virt board, etc) can save/restore fine, but since the imx6 happens to run the guest in the Secure state it gets hit by the bug and its MMU setup etc is completely broken on restore.
+
+This is a bug I knew about (I mentioned it in LP:1739378 comment #5), but I've forgotten the detail of why it happens and don't seem to have written it down, so I'm going to have to think it through again...
+
+
+Hello again, 
+
+I have tried to disable TrustZone using argument mentioned in comment #5 by changing -M sabrelite to -M sabrelite,secure=off, but I get error "qemu-system-arm: Property '.secure' not found". It works with virt though. Is there any other way to disable it? 
+
+Thank you,
+...
+
+That property doesn't exist for the sabrelite board, it's only on some of the others like vexpress or virt.
+
+
+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.]
+
+Save/restore with TrustZone enabled is stil broken.
+
+
+
+This is an automated cleanup. This bug report has been moved to QEMU's
+new bug tracker on gitlab.com and thus gets marked as 'expired' now.
+Please continue with the discussion here:
+
+ https://gitlab.com/qemu-project/qemu/-/issues/467
+
+