From: Atoosah <atoosaah@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Why do rsync and scp stall when transferring files from host to guest?
Date: Mon, 17 Aug 2009 13:11:33 -0700 [thread overview]
Message-ID: <c3578ab90908171311s7907e86eud9509d5a342e8388@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
When I scp or rsync a file several MBs from host Linux machine to guest
Linux machine (both CentOS), the transfer starts at several hundred KB/s but
slows down pretty quickly until it eventually "stalls". I've found a strange
solution which is that if the guest machine pings the host at intervals then
it keeps the connection from stalling (with a rate of about 10 to 20 KB/s).
pinging works fine, but why does secure transfer have problems with
maintaining a stable connection when transfering a single decent sized file?
I've tried rebooting the machine to no avail :-(
scp command used: $scp somefile.gz user@10.0.2.15:/directory_path/
rsync command used: $rsync -av somefile.gz --rsh=ssh user@10.0.2.15:
/directory_path/
thank you,
Atoosah
[-- Attachment #2: Type: text/html, Size: 911 bytes --]
reply other threads:[~2009-08-17 20:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c3578ab90908171311s7907e86eud9509d5a342e8388@mail.gmail.com \
--to=atoosaah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).