From: flrichar <1455912@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1455912] Re: vnc websocket option not properly parsed when running on commandline
Date: Sun, 17 May 2015 13:16:24 -0000 [thread overview]
Message-ID: <20150517131624.22040.2844.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20150517130746.26692.51704.malonedeb@gac.canonical.com
Someone has had a similar issue with the port portion of the display as
a string and not an integer (so it's looking in /etc/services etc):
http://stackoverflow.com/questions/23079017/servname-not-supported-for-
ai-socktype
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1455912
Title:
vnc websocket option not properly parsed when running on commandline
Status in QEMU:
New
Bug description:
All of my vms are started with a simple script on the command line.
Starting with Qemu 2.3.0, the option "-vnc host:port,websocket" is no longer working.
Previously if I said listen on Tor:17,websocket it would function
correctly. Now it's kicking an error:
qemu-system-x86_64: -vnc tor:17,websocket: Failed to start VNC server on `(null)': address resolution failed for tor:on: Servname not supported for ai_socktype
The error leads me to believe it's not parsing the command line
options for the "vnc" option correctly. If I leave off ",websocket"
it works correctly. I've even tried, replacing the hostname with an
IP address, and using the alternate form " -display
vnc=tor:17,webscoket". It reports the same error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1455912/+subscriptions
next prev parent reply other threads:[~2015-05-17 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 13:07 [Qemu-devel] [Bug 1455912] [NEW] vnc websocket option not properly parsed when running on commandline flrichar
2015-05-17 13:16 ` flrichar [this message]
2015-05-17 14:08 ` [Qemu-devel] [Bug 1455912] " flrichar
2017-01-04 14:08 ` Daniel Berrange
2017-01-05 16:56 ` Daniel Berrange
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=20150517131624.22040.2844.malone@chaenomeles.canonical.com \
--to=1455912@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.