All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarda Benkovsky <772358@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 772358] [NEW] VNC working depends on command line options order
Date: Thu, 28 Apr 2011 13:22:50 -0000	[thread overview]
Message-ID: <20110428132250.19043.64893.malonedeb@soybean.canonical.com> (raw)
In-Reply-To: 20110428132250.19043.64893.malonedeb@soybean.canonical.com

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

       reply	other threads:[~2011-04-28 13:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28 13:22 Jarda Benkovsky [this message]
2017-01-17 12:11 ` [Qemu-devel] [Bug 772358] Re: VNC working depends on command line options order Thomas Huth
2017-03-19  4:17 ` Launchpad Bug Tracker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110428132250.19043.64893.malonedeb@soybean.canonical.com \
    --to=772358@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.