All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 7 Jun 2005 10:40:31 +0200	[thread overview]
Message-ID: <46d6db66050607014022a530d8@mail.gmail.com> (raw)
In-Reply-To: <1118102065.9735.50.camel@aragorn>

all these discussions around tftp looked nice and sweet. So I told
myself, instead of using winimage (shareware), why not transferring
files "live".

Yet, when you try on a windows host to exchange files with a linux
guest (inside qemu and with -tftp option), all you get is:

Error code 2: Access violation

is -tftp today working only on linux hosts ? I also read somewhere
the transfer is limited to files lesser than 64k. Can anyone confirm?

Christian

  reply	other threads:[~2005-06-07  8:51 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
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 [this message]
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=46d6db66050607014022a530d8@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.