From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DfyiS-00076k-4N for qemu-devel@nongnu.org; Wed, 08 Jun 2005 07:27:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DfyiP-00075h-G4 for qemu-devel@nongnu.org; Wed, 08 Jun 2005 07:27:21 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DfyiO-000725-Es for qemu-devel@nongnu.org; Wed, 08 Jun 2005 07:27:20 -0400 Received: from [64.233.184.196] (helo=wproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DfyhX-0000os-97 for qemu-devel@nongnu.org; Wed, 08 Jun 2005 07:26:27 -0400 Received: by wproxy.gmail.com with SMTP id 71so332577wra for ; Wed, 08 Jun 2005 04:22:45 -0700 (PDT) Message-ID: <46d6db6605060804226f5f6c5d@mail.gmail.com> Date: Wed, 8 Jun 2005 13:22:45 +0200 From: Christian MICHON Subject: Re: [Qemu-devel] Looking for an easy way to exchange data bidirectional between host and guest (including some suggestion) In-Reply-To: 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> <1118102065.9735.50.camel@aragorn> <46d6db66050607014022a530d8@mail.gmail.com> <46d6db66050607234354d0c93@mail.gmail.com> Reply-To: Christian MICHON , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Henrik Nordstrom Cc: qemu-devel@nongnu.org I made some progress based on your suggestions :) > I don't have any to test on, but the code is extremely simple and not OS > dependeng in any manner except the small detail that UNIX style paths mus= t > be used. >=20 > Where is the file on the host? c:\q\w >=20 > What tftp argument did you gave to qemu when you started it? -tftp "/q" inside a msdos prompt =3D> it's correct according to docs >=20 > What path did you try to retreive from the guest? this is the location of my mistake: I did "get w" instead of "get /q/w" now it works in "get" mode only. Is there anywhere a patch to get rw access to tftp, as well as upping the limit of 32M ? I indeed got a "transfer timeout" after 33553920 bytes :( Christian