From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Dmzqq-00019u-A3 for qemu-devel@nongnu.org; Mon, 27 Jun 2005 16:05:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Dmzqf-00014b-Ug for qemu-devel@nongnu.org; Mon, 27 Jun 2005 16:04:54 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dmzqe-0000rv-EY for qemu-devel@nongnu.org; Mon, 27 Jun 2005 16:04:52 -0400 Received: from [64.233.182.201] (helo=nproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DmzVu-0003FR-W0 for qemu-devel@nongnu.org; Mon, 27 Jun 2005 15:43:27 -0400 Received: by nproxy.gmail.com with SMTP id n15so198950nfc for ; Mon, 27 Jun 2005 12:39:00 -0700 (PDT) Message-ID: <46d6db66050627123916f44242@mail.gmail.com> Date: Mon, 27 Jun 2005 21:39:00 +0200 From: Christian MICHON Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: [Qemu-devel] native slirp/tftp: a temporary solution 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: qemu-devel@nongnu.org ok, after some thinking, I came out to the conclusion that slirp/tftp inside qemu/linux_guest with the xp host is usable enough, even with the restriction of only 1 exchange per session. Indeed, turning off eth0 with a "/etc/rc.d/rc.inet1 stop", and a "/etc/rc.d/rc.inet1 start" allows to redo a new transfer. Then again the eth0 jams internally... until someone finds a fix... At long last I can compile inside qemu with qcow ext2, without having to use winimage and a dos raw image to exchange the resulting kernel. If people are interested in knowing about the whole process, I'll post patches and howto. What I did with a xp host should definitely work with a linux host ;) --=20 Christian