From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1DhDn3-0001Rd-RP
	for qemu-devel@nongnu.org; Sat, 11 Jun 2005 17:45:18 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1DhDmy-0001Oq-1p
	for qemu-devel@nongnu.org; Sat, 11 Jun 2005 17:45:13 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1DhDmw-0001L1-8I
	for qemu-devel@nongnu.org; Sat, 11 Jun 2005 17:45:10 -0400
Received: from [64.233.184.195] (helo=wproxy.gmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1DhDYR-0003rN-QJ
	for qemu-devel@nongnu.org; Sat, 11 Jun 2005 17:30:11 -0400
Received: by wproxy.gmail.com with SMTP id 71so1312943wra
	for <qemu-devel@nongnu.org>; Sat, 11 Jun 2005 14:29:28 -0700 (PDT)
Message-ID: <46d6db6605061114293bc84546@mail.gmail.com>
Date: Sat, 11 Jun 2005 23:29:28 +0200
From: Christian MICHON <christian.michon@gmail.com>
Subject: Re: [Qemu-devel] Looking for an easy way to exchange data
	bidirectional between host and guest (including some suggestion)
In-Reply-To: <20050611205850.GA7047@jbrown.mylinuxbox.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <42A061E3.8010804@xtal.rwth-aachen.de>
	<Pine.LNX.4.61.0506051236080.11204@filer.marasystems.com>
	<20050606142848.GA21394@jbrown.mylinuxbox.org>
	<Pine.LNX.4.61.0506072258550.13848@filer.marasystems.com>
	<20050608182439.GA25845@jbrown.mylinuxbox.org>
	<Pine.LNX.4.61.0506091349130.18410@filer.marasystems.com>
	<20050611205850.GA7047@jbrown.mylinuxbox.org>
Reply-To: Christian MICHON <christian.michon@gmail.com>, qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On 6/11/05, Jim C. Brown <jma5@umd.edu> wrote:
> I agree. While I believe this can be worked around (given a cooperative f=
tpd),
> having a child process for every data connection is really not worth the
> trouble. It's just too ugly. Besides, not every system will have an ftpd
> installed.

since we already have a 32Mb limited tftp, could we make it first
read-write? at least, this would validate what's theoretically
possible, and we could use this rw tftp to develop/debug the
later ftp.

I had a look at the code, and can't figure out where the original
tftp command like 'get' and 'put' are parsed inside the tftp.
Apparently, it's just a question of recognising the 'put' cmd,
then open/create a file on the host matching the tftp
arguments, and that'll be it.

Magnus would be the best person to do this, since it's his
code.

Why do I still think rw tftp could be of any use ?

I personally am using on XP host linux guest doing
kernel compilation. Once the kernel is done, I have 2
scenario:

1) move the compiled kernel to a vfat partition, shutdown
the qemu guest, use winimage to extract the kernel, launch
another qemu guest to test my latest kernel

2) lauch qemu within qemu. Slow square time :( no kqemu for
windows hosts yet

The 3rd possibility would be to use a tftp put back to the host,
and launch a second qemu guest in parallel.

Christian