From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NGMSQ-0002nQ-CK for qemu-devel@nongnu.org; Thu, 03 Dec 2009 19:55:38 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NGMSL-0002mb-NV for qemu-devel@nongnu.org; Thu, 03 Dec 2009 19:55:37 -0500 Received: from [199.232.76.173] (port=60556 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NGMSL-0002mL-IY for qemu-devel@nongnu.org; Thu, 03 Dec 2009 19:55:33 -0500 Received: from smtp-outbound-2.vmware.com ([65.115.85.73]:38273) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NGMSL-0007as-6e for qemu-devel@nongnu.org; Thu, 03 Dec 2009 19:55:33 -0500 Message-ID: <4B185DF6.8040602@vmware.com> Date: Thu, 03 Dec 2009 19:55:18 -0500 From: Christoffer Dall MIME-Version: 1.0 Subject: Re: [Qemu-devel] Networking hangs References: <4B05CB22.7000200@vmware.com> <20091120232955.GH27493@hall.aurel32.net> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Scott Tsai Cc: "qemu-devel@nongnu.org" , Aurelien Jarno 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 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.