From: Christian MICHON <christian.michon@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Looking for an easy way to exchange data bidirectional between host and guest (including some suggestion)
Date: Sat, 11 Jun 2005 23:29:28 +0200 [thread overview]
Message-ID: <46d6db6605061114293bc84546@mail.gmail.com> (raw)
In-Reply-To: <20050611205850.GA7047@jbrown.mylinuxbox.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 ftpd),
> 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
next prev parent reply other threads:[~2005-06-11 21:45 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 13:57 [Qemu-devel] Looking for an easy way to exchange data bidirectional between host and guest (including some suggestion) Jan Marten Simons
2005-06-05 19:17 ` Henrik Nordstrom
2005-06-06 14:28 ` Jim C. Brown
2005-06-07 21:45 ` Henrik Nordstrom
2005-06-08 18:24 ` Jim C. Brown
2005-06-09 11:56 ` Henrik Nordstrom
2005-06-11 20:58 ` Jim C. Brown
2005-06-11 21:29 ` Christian MICHON [this message]
2005-06-13 0:14 ` Henrik Nordstrom
2005-06-13 8:59 ` Christian MICHON
2005-06-13 11:55 ` Jernej Simonèiè
2005-06-13 12:52 ` Christian MICHON
2005-06-14 19:49 ` John R. Hogerhuis
2005-06-14 20:00 ` Christian MICHON
2005-06-15 13:40 ` Henrik Nordstrom
2005-06-14 20:33 ` Jim C. Brown
2005-06-15 13:43 ` Henrik Nordstrom
2005-06-13 0:02 ` Henrik Nordstrom
2005-06-13 0:22 ` Paul Brook
2005-06-06 18:11 ` marten
2005-06-06 19:55 ` Jim C. Brown
2005-06-06 23:38 ` Jan Marten Simons
2005-06-07 16:16 ` Johannes Schindelin
2005-06-07 21:52 ` Henrik Nordstrom
2005-06-08 18:27 ` Jim C. Brown
2005-06-07 21:50 ` Henrik Nordstrom
2005-06-06 23:54 ` John R. Hogerhuis
2005-06-07 8:40 ` Christian MICHON
2005-06-07 22:59 ` Henrik Nordstrom
2005-06-08 6:43 ` Christian MICHON
2005-06-08 7:55 ` Henrik Nordstrom
2005-06-08 11:22 ` Christian MICHON
2005-06-08 12:25 ` Henrik Nordstrom
2005-06-08 22:31 ` Jan Marten Simons
2005-06-08 23:50 ` Jim C. Brown
2005-06-21 14:17 ` Jan Marten Simons
2005-06-21 20:02 ` Jim C. Brown
2005-06-21 21:39 ` Paul Brook
2005-06-21 21:47 ` Jim C. Brown
2005-06-09 16:33 ` Johannes Schindelin
2005-06-10 13:45 ` Jan Marten Simons
2005-06-07 22:15 ` Henrik Nordstrom
2005-06-08 6:12 ` John R. Hogerhuis
2005-06-08 7:52 ` Henrik Nordstrom
2005-06-08 11:22 ` Johannes Schindelin
2005-06-09 11:48 ` Henrik Nordstrom
2005-06-09 16:26 ` Johannes Schindelin
2005-06-08 18:33 ` Jim C. Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46d6db6605061114293bc84546@mail.gmail.com \
--to=christian.michon@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.