qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Veillard <veillard@redhat.com>
To: Oliver Gerlich <olig9@gmx.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Remote console access though socket
Date: Sun, 12 Mar 2006 06:03:09 -0500	[thread overview]
Message-ID: <20060312110308.GD22089@redhat.com> (raw)
In-Reply-To: <44134DA5.9030700@gmx.de>

On Sat, Mar 11, 2006 at 11:22:29PM +0100, Oliver Gerlich wrote:
> Daniel Veillard schrieb:
> > I need first to find the ports of the 
> > QEmu instances (plural, if you limit to one per box, then you can block the
> > default port number and there would be no problem) on a local machine. I
> > don't think that "Multicast DNS"/RendezVous works with random port numbers,
> > all it does over normal TCP is scan for local hosts without using DNS
> > resolution. Again I don't think it's really the problem I'm trying to solve,
> > maybe I just didn't expressed myself clearly :-)
> 
> After experimenting with the avahi apps a bit, I think mDNS can indeed
> advertise several services on the same host with different ports! I ran
> "avahi-publish -s -H localhost myserver1 _http._tcp 80" in one terminal,
> then "avahi-publish -s -H localhost myserver2 _http._tcp 12345" in
> another terminal. This advertised two HTTP servers which were running on
> my local host, on ports 80 and 12345, under the names myserver1 and
> myserver2.
> avahi-discover then displayed these two services, with their names and
> the correct port numbers. And in konqueror, browsing to "zeroconf:/"
> also showed the two "WWW servers" correctly.
> 
> So, this could provide the functionality you were looking for... But it
> still has the drawback that zeroconf seems to be quite a big framework,
> and it requires multicast DNS in the kernel and such stuff...

  Ah, okay, well basically once you run you own DNS like service locally 
this kind of things becomes possible. But yes this is quite a big framework,
adding this as a dependency sounds a bit extreme, and I assume it won't
work if you don't have an avahi or zeroconf server running. One of the main
advantage of QEmu is that its requirement at the system level are very low,
I'm not sure we can put gracefully such requirement there :-)

  But thanks for updating me on this, that's good to know !

Daniel

-- 
Daniel Veillard      | Red Hat http://redhat.com/
veillard@redhat.com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

  reply	other threads:[~2006-03-12 11:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 14:52 [Qemu-devel] [PATCH] Remote console access though socket Daniel Veillard
     [not found] ` <16af12af0603081035h5f61d947y6c24b7a7675eeb14@mail.gmail.com>
2006-03-08 20:35   ` Ed Swierk
2006-03-11 20:53     ` Daniel Veillard
2006-03-11 16:24 ` Oliver Gerlich
2006-03-11 20:59   ` Daniel Veillard
2006-03-11 22:22     ` Oliver Gerlich
2006-03-12 11:03       ` Daniel Veillard [this message]
2006-03-11 21:07 ` Daniel Veillard
  -- strict thread matches above, loose matches on Subject: below --
2006-03-09 12:47 wanderer
2006-03-09 12:55 ` Daniel Veillard

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=20060312110308.GD22089@redhat.com \
    --to=veillard@redhat.com \
    --cc=olig9@gmx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).