From: Oliver Gerlich <olig9@gmx.de>
To: veillard@redhat.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Remote console access though socket
Date: Sat, 11 Mar 2006 23:22:29 +0100 [thread overview]
Message-ID: <44134DA5.9030700@gmx.de> (raw)
In-Reply-To: <20060311205918.GK346@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Daniel Veillard schrieb:
> On Sat, Mar 11, 2006 at 05:24:40PM +0100, Oliver Gerlich wrote:
>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>Daniel Veillard schrieb:
>>
>>> Hi,
>>>
>>>enclosed is a first version of a patch to allow remote access and control
>>>for QEmu instances, I'm not suggesting to apply it as is (though it seems
>>>to work in my limited testing) but would rather like to get comments back
>>>for choices I'm facing.
>>
>>[...]
>>
>>> There is a number of open questions which would need to be resolved before
>>>applying any such patch:
>>> - First one is the unix socket, we could as easilly start normal port
>>> based access but:
>>> + I would really like to be able to list the current running instance
>>> without checking all process on the OS, and mapping in the file
>>> system seems the easiest way
>>
>>Just an idea: how about using "Multicast DNS" (see multicastdns.org)?
>>IIUC it provides a generic way to find services on a net; and it's
>>supported at least by MacOSX and with eg. Avahi (see avahi.org) also on
>>Linux. Not sure about Windows, though...
>
>
> It's rather LAN oriented,
Yes, that's a bit ugly.
> 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 :-)
>
> Daniel
>
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...
Regards,
Oliver
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFEE02jTFOM6DcNJ6cRAtgLAJ9e8YlWFi6Is9+w2yDcOTIJFr9h8QCgvz18
hXvZb+16P1W5QDhnkac1ywc=
=d+pp
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-03-11 22:22 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 [this message]
2006-03-12 11:03 ` Daniel Veillard
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=44134DA5.9030700@gmx.de \
--to=olig9@gmx.de \
--cc=qemu-devel@nongnu.org \
--cc=veillard@redhat.com \
/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.