1 files changed, 46 insertions, 0 deletions
diff --git a/results/classifier/118/graphic/1280961 b/results/classifier/118/graphic/1280961
new file mode 100644
index 00000000..5931ad7e
--- /dev/null
+++ b/results/classifier/118/graphic/1280961
@@ -0,0 +1,46 @@
+graphic: 0.965
+KVM: 0.963
+kernel: 0.885
+x86: 0.868
+files: 0.855
+device: 0.820
+architecture: 0.771
+vnc: 0.745
+PID: 0.736
+ppc: 0.735
+debug: 0.718
+semantic: 0.717
+performance: 0.695
+virtual: 0.676
+hypervisor: 0.666
+arm: 0.659
+VMM: 0.655
+risc-v: 0.625
+TCG: 0.595
+network: 0.586
+user-level: 0.571
+register: 0.563
+boot: 0.558
+i386: 0.535
+mistranslation: 0.522
+socket: 0.517
+peripherals: 0.511
+permissions: 0.470
+assembly: 0.394
+
+editing the file when mount the file system using 9pfs. it will report fsync failed. 
+
+ I have get a fsync error when I use the 9pfs on the kvm guest. it appears when I use vi editor and sysbench. I have not  found the reason yet. can you tell something about it?  the attache is the picture. and there is no any log which I can provide.
+
+ My qemu version is qemu-kvm-0.13.0, and my  host  linux distributions is 2.6.32-431.el6.x86_64 and the guest vm is the same version which enable 9pfs and 9pnet support. I use the string of "mount -t 9p -o trans=virtio test_mount /tmp/shared/ -oversion=9p2000.L,posixacl" to get the file system.
+
+resovled it, this is because in the kernel 2.6.32; the 9pfs doesn't implement the fsync function. just back port the code from higher version, can resolve it. 
+
+like this patch
+
+https://gitorious.org/linux-gemini/mainline/commit/7a4439c406c21b1e900ed497cec1a79d05b38c07
+
+
+
+Closing, as this problem has been resolved according to the last comment.
+