the remote address / port to something sensible. Otherwise
simultaneous connections to the same guest port don't work properly.
svn path=/nixpkgs/trunk/; revision=16805
the host to a TCP port on the guest. This will be useful for
automated testing using QEMU virtual machines. Using TCP ports on
the host is insecure and hard to manage (since you need to pick an
available host port).
For example:
$ qemu-system-x86_64 ... -redir tcp:65535::514
creates a Unix domain socket `./65535.socket' on the host. (There
is no proper syntax yet, so as a hack all host "ports" above 0xff00
are treated in this way.) Connections to that socket are then
forwarded to TCP port 514 on the guest. So the guest can do
$ nc -l -p 514 -e /bin/sh
to execute a shell for incoming connections on port 514, and then
the host can do
$ socat stdio ./65535.socket
to run a shell on the guest.
svn path=/nixpkgs/trunk/; revision=16593
