summaryrefslogtreecommitdiffstats
path: root/results/classifier/118/none/772358
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--results/classifier/118/none/77235857
1 files changed, 57 insertions, 0 deletions
diff --git a/results/classifier/118/none/772358 b/results/classifier/118/none/772358
new file mode 100644
index 00000000..511a7518
--- /dev/null
+++ b/results/classifier/118/none/772358
@@ -0,0 +1,57 @@
+device: 0.229
+network: 0.204
+graphic: 0.179
+vnc: 0.106
+semantic: 0.106
+mistranslation: 0.093
+virtual: 0.091
+performance: 0.091
+register: 0.086
+kernel: 0.074
+socket: 0.067
+ppc: 0.060
+KVM: 0.045
+x86: 0.045
+architecture: 0.044
+risc-v: 0.036
+permissions: 0.030
+user-level: 0.028
+boot: 0.028
+hypervisor: 0.027
+debug: 0.022
+arm: 0.021
+PID: 0.020
+peripherals: 0.019
+assembly: 0.019
+files: 0.016
+VMM: 0.011
+i386: 0.010
+TCG: 0.009
+
+VNC working depends on command line options order
+
+OS: Ubuntu 10.04.2, amd64
+Pkg version: 0.12.3+noroms-0ubuntu9.5
+
+if -nographic option is specified before -vnc, vnc works, if vice-versa, it does not. I have been told (thanks, mjt), that -nographic is supposed to disable any graphic output, including vnc, so possibly it's a documentation bug:
+
+- kvm man page talks about -nographic disabling SDL , not VNC. While it might be the same to you, it was not to me and my colleagues
+
+- if -vnc and -nographic are conflicting, perhaps kvm should error out or at least warn
+
+- monitor console's message on "change vnc 127.0.0.1:1" command: "Could not start server on 127.0.0.1:1" is not helpful either
+
+- order of the options should not matter
+
+Example: (VNC works)
+
+/usr/bin/kvm -name ubuntu.example.com -m 3076 -smp 2 -drive if=virtio,file=/dev/vg0/kvm-ubuntu,boot=on,media=disk,cache=none,index=0 -net nic,vlan=0,model=virtio,macaddr=00:03:03:03:03:01 -net tap,ifname=kvm_ubuntu,vlan=0,script=no,downscript=no -balloon virtio -nographic -daemonize -vnc 127.0.0.1:1 -pidfile /var/run/kvm/1
+
+Example: (VNC does not work, also confuses terminal):
+
+/usr/bin/kvm -name ubuntu.example.com -m 3076 -smp 2 -drive if=virtio,file=/dev/vg0/kvm-ubuntu,boot=on,media=disk,cache=none,index=0 -net nic,vlan=0,model=virtio,macaddr=00:03:03:03:03:01 -net tap,ifname=kvm_ubuntu,vlan=0,script=no,downscript=no -balloon virtio -vnc 127.0.0.1:1 -nographic -daemonize -pidfile /var/run/kvm/1
+
+QEMU 0.12 is pretty much outdated nowadays ... can you still reproduce this problem with the latest version of QEMU, or can we close this bug?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+