summary refs log tree commit diff stats
path: root/results/classifier/118/user-level-i386/788701
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/118/user-level-i386/788701')
-rw-r--r--results/classifier/118/user-level-i386/78870176
1 files changed, 76 insertions, 0 deletions
diff --git a/results/classifier/118/user-level-i386/788701 b/results/classifier/118/user-level-i386/788701
new file mode 100644
index 000000000..346214c3d
--- /dev/null
+++ b/results/classifier/118/user-level-i386/788701
@@ -0,0 +1,76 @@
+i386: 0.949
+x86: 0.926
+graphic: 0.903
+user-level: 0.857
+architecture: 0.797
+device: 0.795
+network: 0.688
+performance: 0.686
+register: 0.618
+semantic: 0.600
+PID: 0.584
+socket: 0.569
+boot: 0.534
+vnc: 0.504
+files: 0.489
+permissions: 0.487
+ppc: 0.461
+peripherals: 0.452
+debug: 0.431
+mistranslation: 0.410
+arm: 0.381
+risc-v: 0.356
+TCG: 0.319
+kernel: 0.309
+VMM: 0.304
+KVM: 0.136
+virtual: 0.123
+hypervisor: 0.094
+assembly: 0.080
+--------------------
+user-level: 0.941
+x86: 0.852
+hypervisor: 0.652
+virtual: 0.456
+i386: 0.053
+debug: 0.053
+TCG: 0.039
+register: 0.028
+files: 0.025
+network: 0.007
+performance: 0.006
+kernel: 0.005
+PID: 0.003
+device: 0.002
+semantic: 0.002
+assembly: 0.002
+VMM: 0.001
+socket: 0.001
+architecture: 0.001
+risc-v: 0.001
+peripherals: 0.001
+ppc: 0.001
+boot: 0.001
+KVM: 0.000
+permissions: 0.000
+graphic: 0.000
+vnc: 0.000
+mistranslation: 0.000
+arm: 0.000
+
+qemu-user fails to run rpcgen (i386, x86_64)
+
+Confirmed on qemu current development tree (git commit aa29141). While trying to run eglibc's rpcgen from native system by qemu-user, I get an error:
+
+qemu-x86_64 /usr/bin/rpcgen -c /dev/null 
+fork: Invalid argument
+
+I am running a Debian Wheezy system and rpcgen comes from libc-dev-bin. Just in case I am attaching my rpcgen binaries from i386 and x86_64 systems.
+
+Very similar problem was mentioned on the QEMU forum on February 2007, so I guess it might be a known issue. Nevertheless, I was unable to find any information about bug reports, fixes nor workarounds for it so I'm reporting it here.
+
+
+
+This should be fixed in QEMU 1.6.
+
+