1 files changed, 67 insertions, 0 deletions
diff --git a/results/classifier/118/network/1702798 b/results/classifier/118/network/1702798
new file mode 100644
index 000000000..654a04695
--- /dev/null
+++ b/results/classifier/118/network/1702798
@@ -0,0 +1,67 @@
+network: 0.834
+ppc: 0.819
+performance: 0.796
+files: 0.774
+graphic: 0.750
+device: 0.695
+arm: 0.674
+kernel: 0.643
+virtual: 0.614
+register: 0.612
+semantic: 0.603
+hypervisor: 0.597
+KVM: 0.573
+PID: 0.571
+assembly: 0.571
+debug: 0.564
+mistranslation: 0.563
+socket: 0.550
+vnc: 0.547
+permissions: 0.546
+user-level: 0.536
+architecture: 0.533
+risc-v: 0.531
+VMM: 0.499
+peripherals: 0.491
+boot: 0.453
+i386: 0.445
+x86: 0.378
+TCG: 0.363
+
+colo: secondary vm can't receive any packet
+
+Following document 'COLO-FT.txt', I test colo feature on my hosts. It seems goes well,but I found the secondary vm can't receive any packets. I attached the process and find out the reason as follow, the filter-redirector(red0) didn't flush it's queue because the secondary vm in migrate state(RUN_STATE_INMIGRATE) :
+int qemu_can_send_packet(NetClientState *sender)
+{
+    int vm_running = runstate_is_running():
+
+    if (!vm_running) {         // it will return false on the secondary vm
+        return 0;
+    }
+    ------
+}
+
+How does it produce outbound packets in the secondary vm as it in migrate state?
+static void *qemu_kvm_cpu_thread_fn(void *arg)
+{
+    ------
+    do {
+        if (cpu_can_run(cpu)) {      // it will return false on the secondary vm
+            r = kvm_cpu_exec(cpu);
+    ------
+}
+
+The qemu version is 2.9.0 release.
+The secondary vm state make me confused. I tried to add vm_stop and vm_start in colo_process_incoming_thread function, but it crashed.
+
+In qemu upstream COLO project can not fully running, you can test my internal branch.
+https://github.com/zhangckid/qemu/commits/colo-with-virtio-net-internal-jul10
+
+Thanks
+Zhang Chen
+
+The QEMU project is currently considering to move 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 older bugs to "Incomplete" now.
+If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Thank you and sorry for the inconvenience.
+
+[Expired for QEMU because there has been no activity for 60 days.]
+