From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Dg5Od-0000A4-Jt for qemu-devel@nongnu.org; Wed, 08 Jun 2005 14:35:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Dg5OR-0008U1-3K for qemu-devel@nongnu.org; Wed, 08 Jun 2005 14:35:14 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dg5OO-0008SR-4k for qemu-devel@nongnu.org; Wed, 08 Jun 2005 14:35:08 -0400 Received: from [128.8.10.163] (helo=po1.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Dg5Kh-0007E4-Dq for qemu-devel@nongnu.org; Wed, 08 Jun 2005 14:31:19 -0400 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.237.180]) by po1.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j58IRXRu006566 for ; Wed, 8 Jun 2005 14:27:33 -0400 (EDT) Date: Wed, 8 Jun 2005 14:27:33 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] Looking for an easy way to exchange data bidirectional between host and guest (including some suggestion) Message-ID: <20050608182733.GB25845@jbrown.mylinuxbox.org> References: <42A061E3.8010804@xtal.rwth-aachen.de> <64655.80.137.250.37.1118081468.squirrel@pc42.xtal.rwth-aachen.de> <20050606195519.GA4628@jbrown.mylinuxbox.org> <63058.80.137.250.37.1118101094.squirrel@pc42.xtal.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <63058.80.137.250.37.1118101094.squirrel@pc42.xtal.rwth-aachen.de> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Tue, Jun 07, 2005 at 01:38:14AM +0200, Jan Marten Simons wrote: > > Like I said, modifying TFTP for R/W would be a good option. It's already > there, > > the "miminalists" can't complain about having it removed (e.g. it may > one day > > be used to support "virtual" netboots), and one can use ftp clients for > > the tftp server (I think). > > Well the TFTP-server should get r/w, too, but if I get it right you'd have > to access the data on the guest from the host, which might lead to > situation where users shutdown the guest and then try to get their > (then lost) data from it via TFTP, which has to be installed on the host. I'm not sure I understand what you mean here. TFTP server support is builtin to qemu, once guest goes down so does TFTP. To access host data from guest is then no problem, but to access data on guest from host, you need to explicitly upload that data on the TFTP server - which will copy the data on the host. -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.