1 files changed, 111 insertions, 0 deletions
diff --git a/results/classifier/111/review/1922102 b/results/classifier/111/review/1922102
new file mode 100644
index 00000000..c3928999
--- /dev/null
+++ b/results/classifier/111/review/1922102
@@ -0,0 +1,111 @@
+device: 0.161
+other: 0.126
+network: 0.125
+files: 0.088
+PID: 0.085
+boot: 0.063
+permissions: 0.060
+semantic: 0.051
+graphic: 0.047
+performance: 0.047
+socket: 0.043
+debug: 0.043
+vnc: 0.031
+KVM: 0.030
+network: 0.196
+debug: 0.162
+files: 0.098
+device: 0.088
+other: 0.085
+PID: 0.075
+socket: 0.058
+semantic: 0.048
+boot: 0.047
+vnc: 0.046
+permissions: 0.026
+graphic: 0.026
+performance: 0.025
+KVM: 0.019
+
+Broken tap networking on macOS host
+
+Building QEMU with GLib newer than 2.58.3 corrupts tap networking. 
+Tap device was provided by Tun/Tap kernel extension installed from brew:
+  brew install tuntap
+
+Checked revisions:
+  553032d (v5.2.0)
+  6d40ce0 (v6.0.0-rc1)
+
+Host:
+ MacBook Pro (Retina, 15-inch, Mid 2015)
+ macOS Catalina 10.15.6 (19G2021)
+
+Guest:
+  Linux Ubuntu 4.4.0-206-generic x86_64
+  Also tested macOS Catalina 10.15.7 as a guest, the behaviour is the same.
+
+QEMU command line:
+
+qemu-system-x86_64 \
+  -drive file=hdd.qcow2,if=virtio,format=qcow2 \
+  -m 3G \
+  -nic tap,script=tap-up.sh
+
+tap-up.sh:
+ 
+ #!/bin/sh
+
+ TAPDEV="$1"
+ BRIDGEDEV="bridge0"
+
+ ifconfig "$BRIDGEDEV" addm "$TAPDEV"
+
+Enabling/disabling Hypervisor.Framework acceleration (`-accel hvf`) has no effect. 
+
+How to reproduce: 
+  1. Build & install GLib > 2.58.3 (tested 2.60.7, 2.60.7)
+  2. Build qemu-system-x86_64 with GLib > 2.58.3
+  3. Boot any guest any guest with tap networking enabled
+  4. See that the external network is inaccessible
+
+Hotfix:
+  1. Build & install GLib 2.58.3
+  2. Build qemu-system-x86_64 with GLib 2.58.3
+  3. Boot any guest with tap networking enabled
+  4. See that the external network is accessible, everything is working as expected
+
+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.
+
+
+Ticket has been moved here (thanks, Vladislav!):
+https://gitlab.com/qemu-project/qemu/-/issues/335
+... thus I'm closing this on Launchpad now.
+