3 files changed, 157 insertions, 0 deletions
diff --git a/results/classifier/108/other/1712 b/results/classifier/108/other/1712
new file mode 100644
index 000000000..d60fcf86c
--- /dev/null
+++ b/results/classifier/108/other/1712
@@ -0,0 +1,24 @@
+device: 0.875
+graphic: 0.690
+PID: 0.538
+semantic: 0.458
+boot: 0.453
+files: 0.367
+permissions: 0.357
+debug: 0.333
+KVM: 0.281
+socket: 0.256
+network: 0.230
+vnc: 0.200
+other: 0.189
+performance: 0.178
+
+Arabic keyboard layout wrong.
+Description of problem:
+After a while the compilation process starts, xkb gives an error about symbols/ar not found. According to my research, linux distros using "ara" for arabic layout. But qemu pc-bios/keymaps/ folder contains "ar" for arabic layout.
+Steps to reproduce:
+1.Configure
+2.Build
+3.Wait until error appears.
+Additional information:
+
diff --git a/results/classifier/108/other/1712564 b/results/classifier/108/other/1712564
new file mode 100644
index 000000000..d1c1c04ec
--- /dev/null
+++ b/results/classifier/108/other/1712564
@@ -0,0 +1,47 @@
+graphic: 0.831
+PID: 0.802
+device: 0.723
+socket: 0.684
+vnc: 0.682
+performance: 0.667
+permissions: 0.655
+other: 0.642
+network: 0.640
+debug: 0.579
+semantic: 0.553
+files: 0.514
+boot: 0.466
+KVM: 0.410
+
+loadvm fails twice in sequence
+
+13:38:23) shorne_: Hello, I was doing some testing with migrations for my OpenRISC SMP patch set, I noticed something that looks like a bug, wondering if someone else wants to confirm
+(13:38:47) shorne_: Basically, calling loadvm 2 times causes crash
+(13:38:54) shorne_:    migration/savevm.c:    qemu_event_set(&mis->main_thread_load_event)
+(13:38:54) stefanha: fam: Here is my take at this change: https://paste.debian.net/982690/
+(13:38:56) shorne_:                             assert(ev->initialized)  - fails inside
+(13:39:32) stefanha: quintela davidgiluk: ^
+(13:41:23) ***davidgiluk looks
+(13:41:40) shorne_: c096358e747 util/qemu-thread-posix.c (Fam Zheng              2017-07-04 20:23:25 +0800 397)     assert(ev->initialized);
+(13:41:51) davidgiluk: shorne_: So you're doing a loadvm to load a snapshot and then again?
+(13:42:02) shorne_: Looks like adding that assert() was done really recently
+(13:42:41) shorne_: yes, just loadvm 'a' ... then wait a bit longer, loadvm 'a' again (confirm clocks go back etc)
+(13:42:50) stefanha: fam: While you're having dinner I'll work on turning my script into a qemu-iotests test case that we can merge.
+(13:44:03) gpiccoli [~gpiccoli@0002093a.user.oftc.net] entered the room.
+(13:44:21) davidgiluk: shorne_: Well, it looks like the c09635 assert is a sanity check to make sure we didn't do anything stupid, and well.....
+(13:44:57) pm215: migration_incoming_get_current() and migration_incoming_state_destroy() seem a bit mismatched
+(13:45:13) davidgiluk: pm215: Yep
+(13:45:46) davidgiluk: pm215: Generally we've thought that an incoming migration normally only happens once - shorne_'s case is the exception
+(13:46:03) shorne_: pm215: yeah, it looked something like that I just had a few seconds to look at today
+(13:46:03) HariharanTS left the room (quit: Ping timeout: 480 seconds).
+(13:46:03) shorne_ is now known as shorne
+(13:48:05) shorne: davidgiluk: pm215: thanks for having a look.  Unfortunately I need to head off to bed and put kids to sleep
+(13:49:11) davidgiluk: shorne: Sleep well, no nightmares about event destroyers....
+(13:49:30) davidgiluk: pm215: Yeh this is fall out from b4b076daf32
+
+Posted:
+migration: Reset rather than destroy main_thread_load_event
+snapshot/tests: Try loadvm twice
+
+Commit 5089e1862fe80b6f23ba4c494e2902cbe3d9d48e
+
diff --git a/results/classifier/108/other/1712818 b/results/classifier/108/other/1712818
new file mode 100644
index 000000000..a932f4bbd
--- /dev/null
+++ b/results/classifier/108/other/1712818
@@ -0,0 +1,86 @@
+device: 0.859
+PID: 0.803
+socket: 0.792
+graphic: 0.782
+KVM: 0.756
+other: 0.746
+boot: 0.738
+semantic: 0.662
+permissions: 0.623
+network: 0.616
+files: 0.595
+vnc: 0.588
+performance: 0.576
+debug: 0.567
+
+live migration with storage encounter assert(!(bs->open_flags & BDRV_O_INACTIVE)) crashes
+
+The vm guest runs a iotest program, and i migrate it with virsh --copy-storage-all,then the qemu process on the source host happens to crash with the following message:
+
+kvm: block/io.c:1543: bdrv_co_pwritev: Assertion `!(bs->open_flags & 0x0800)' failed.
+2017-08-24 11:43:45.919+0000: shutting down, reason=crashed
+
+
+here is the release:
+qemu 2.7 & 2.10.rc3 were tested.
+libvirt 3.0.0 & 3.2.0 were tested.
+
+command line:
+src_host:virsh migrate --verbose --live --persistent --copy-storage-all vm-core qemu+ssh://dst_host/system
+
+Resaon: After bdrv_inactivate_all() was called, mirror_run coroutine stills write the left dirty disk data to remote nbd server, which triggers the assertion. But I don't known how to avoid the problem, help is needed!  Thanks.
+
+On 08/24/2017 07:59 AM, meeho yuen wrote:
+> Public bug reported:
+> 
+> The vm guest runs a iotest program, and i migrate it with virsh --copy-
+> storage-all,then the qemu process on the source host happens to crash
+> with the following message:
+> 
+> kvm: block/io.c:1543: bdrv_co_pwritev: Assertion `!(bs->open_flags & 0x0800)' failed.
+> 2017-08-24 11:43:45.919+0000: shutting down, reason=crashed
+
+>   here is the release:
+>   qemu 2.7 & 2.10.rc3 were tested.
+
+The just-tagged 2.10-rc4 includes a fix that should be addressing that
+issue during live migration; can you please re-test with that?  (see
+also https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg04513.html)
+
+-- 
+Eric Blake, Principal Software Engineer
+Red Hat, Inc.           +1-919-301-3266
+Virtualization:  qemu.org | libvirt.org
+
+
+
+Thank you,I will try it.
+
+hi,eblake,the problem still exists on qemu 2.10_rc4,although the possibility is less than before.
+
+
+kvm: block/io.c:1543: bdrv_co_pwritev: Assertion `!(bs->open_flags & 0x0800)' failed.
+2017-08-25 11:08:18.963+0000: shutting down, reason=crashed
+
+
+I see the same thing:
+
+2017-12-28 21:36:26.837+0000: initiating migration
+qemu-system-x86_64: block/io.c:1537: bdrv_co_pwritev: Assertion `!(bs->open_flags & BDRV_O_INACTIVE)' failed.
+2017-12-28 21:36:40.516+0000: shutting down, reason=crashed
+~
+
+Running:
+QEMU emulator version 2.10.1
+libvirtd (libvirt) 3.10.0
+
+
+
+It seems that the following commit for libvirt fixed the problem.
+https://github.com/libvirt/libvirt/blob/960326237764f8970250a3608e7b2b880e030715/src/qemu/qemu_migration.c
+
+
+Looking through old bug tickets... is this still an 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.]
+