All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alon Levy <alonlevy1@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1020484] Re: RFE: Support spice via unix domain socket
Date: Wed, 04 Jul 2012 16:39:36 -0000	[thread overview]
Message-ID: <20120704163936.12868.77814.malone@gac.canonical.com> (raw)
In-Reply-To: 20120703094755.29916.21218.malonedeb@chaenomeles.canonical.com

There is already support for that in spice-server afaik, though I don't
remember the api or what commit, or if it's in a released version (well,
it's surely in 0.11.0, but that's unstable). Sorry about the lack of
details, I suggest you search spice-devel mailing list archive though. I
think libvirt can already use it, but perhaps you want a commandline
option, that may be missing.

Alon

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1020484

Title:
  RFE: Support spice via unix domain socket

Status in QEMU:
  New

Bug description:
  According to the man page, spice can be only used via TCP/IP in
  opposite to VNC, which can also be configured to listen on a unix
  domain socket. To make it easy to use spice without exposing the
  interface, please support unix domain sockets as well. I can try  to
  provide a patch, if you can point me to the source code where TCP/IP
  socket is opened.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1020484/+subscriptions

  reply	other threads:[~2012-07-04 16:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03  9:47 [Qemu-devel] [Bug 1020484] [NEW] RFE: Support spice via unix domain socket Till Maas
2012-07-04 16:39 ` Alon Levy [this message]
2017-04-07 13:35 ` [Qemu-devel] [Bug 1020484] " Thomas Huth
2017-04-07 14:13 ` elmarco

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=20120704163936.12868.77814.malone@gac.canonical.com \
    --to=alonlevy1@gmail.com \
    --cc=1020484@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.