From: Christoffer Dall <cdall@vmware.com>
To: Scott Tsai <scottt.tw@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] Networking hangs
Date: Thu, 03 Dec 2009 19:55:18 -0500 [thread overview]
Message-ID: <4B185DF6.8040602@vmware.com> (raw)
In-Reply-To: <ef2f888d0911201544m6448df4cmc91de00fef7af522@mail.gmail.com>
Hi there.
I tried to verify if the bug existed with Realview, but I just can't get
the guest to mount an sd-card, which I created with qemu-img and copied
a roots onto there and the guest kernel cannot be configured with
PCI/SCSI support for the ext2 image.
Do you have any ideas on how to proceed with either the realview stuff
to see if that's the problem or with the networking issue?
Thanks!
Best,
Christoffer
Scott Tsai wrote:
> On Sat, Nov 21, 2009 at 7:29 AM, Aurelien Jarno <aurelien@aurel32.net> wrote:
>> On Thu, Nov 19, 2009 at 05:48:02PM -0500, Christoffer Dall wrote:
>>> Hi.
>>>
>>> I am experiencing problems with bridged networking to ARM guests. I have
>>> experimented with various kernel versions, distributions and host
>>> machines and I experience the problem in all cases.
>>>
>>> When I copy files into the guest using SCP, after an undeterministic
>>> number of megabytes have been copied, the network crashes. At this point
>>> not even pings to localhost works inside the guest.
>>>
>>> I am using v0.11.0, emulating a versatilepb board with an arm1136-r2 cpu
>> Have you tried to use the stable-0.11 branch (that will become 0.11.1 at
>> some point) instead? It has some ARM and network related fixes.
>
> Using the files that Christoffer uploaded, I can reproduce this bug
> even on stable-0.11.
> (i.e. using scp to copy a large file seems to "hang" the network stack
> in the guest to the point that even "ping 127.0.0.1" fails)
>
> The interesting part about this bug is that Christoffer patched the
> Linux kernel to allow using an ARMv6 CPU on the versatilepb board.
> I've verified that by changing the emulated cpu from arm1136-r2 to
> arm926 and building a kernel for the arm926 this bug no longer
> happens.
>
> I'm not familiar enough with the ARM architecture to explain why the
> versatilepb board would have such "reliability problems" with
> arm1136-r2 CPU right away.
> I was about to try emulating a arm1136-r2 CPU on a realview board.
next prev parent reply other threads:[~2009-12-04 0:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 22:48 [Qemu-devel] Networking hangs Christoffer Dall
2009-11-20 18:41 ` Scott Tsai
2009-11-20 20:19 ` Christoffer Dall
2009-11-20 23:29 ` Aurelien Jarno
2009-11-20 23:44 ` Scott Tsai
2009-12-04 0:55 ` Christoffer Dall [this message]
2009-12-16 3:09 ` Scott Tsai
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=4B185DF6.8040602@vmware.com \
--to=cdall@vmware.com \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=scottt.tw@gmail.com \
/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).