summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/108/other/1921280
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/zero-shot/108/other/1921280')
-rw-r--r--results/classifier/zero-shot/108/other/192128055
1 files changed, 55 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1921280 b/results/classifier/zero-shot/108/other/1921280
new file mode 100644
index 00000000..5b771b31
--- /dev/null
+++ b/results/classifier/zero-shot/108/other/1921280
@@ -0,0 +1,55 @@
+boot: 0.902
+graphic: 0.823
+other: 0.796
+performance: 0.787
+device: 0.785
+PID: 0.706
+files: 0.622
+semantic: 0.617
+network: 0.581
+permissions: 0.577
+debug: 0.557
+vnc: 0.552
+socket: 0.445
+KVM: 0.277
+
+OpenIndiana stuck in boot loop when using hvf
+
+I'm using QEMU version 5.2.0 on macOS, and running the "OpenIndiana Hipster 2020.10 Text Install DVD (64-bit x86)" ISO:
+
+qemu-system-x86_64 -cdrom ~/Downloads/OI-hipster-text-20201031.iso -m 2048 -accel hvf -cpu host
+
+It gets to "Booting...", stays there for a bit, and then restarts.
+
+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.]
+