Public bug reported:
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
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/772358
Title:
VNC working depends on command line options order
Status in QEMU:
New
Bug description:
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
