qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christoffer Dall <cdall@vmware.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] ARM guest network issue
Date: Sun, 20 Sep 2009 12:21:16 -0400	[thread overview]
Message-ID: <4AB6567C.7020702@vmware.com> (raw)

When using tap networking with a Linux 2.6.29 kernel I experience that 
the guest network crashes after submitting a certain amount of data.

When transferring say 50MB using scp into the guest, it will halt 
somewhere before transferring everything.

Afterwards, I cannot even ping localhost inside the guest. The recvfrom 
system call returns ERESTARTSYS when waiting for data to read from a 
socket buffer, but there is never any data. From the strace output it 
seems that the sendto system call succeeds as it should.

I am using the latest upstream QEMU version.

Any help would be greatly appreciated.

Best regards,
Christoffer Dall

VMware, Inc.

                 reply	other threads:[~2009-09-20 16:21 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=4AB6567C.7020702@vmware.com \
    --to=cdall@vmware.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).