From: Scott Tsai <scottt.tw@gmail.com>
To: Christoffer Dall <cdall@vmware.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] Networking hangs
Date: Wed, 16 Dec 2009 11:09:13 +0800 [thread overview]
Message-ID: <ef2f888d0912151909i53354f30pec27f4b9c3642db5@mail.gmail.com> (raw)
In-Reply-To: <4B185DF6.8040602@vmware.com>
On Fri, Dec 4, 2009 at 8:55 AM, Christoffer Dall <cdall@vmware.com> wrote:
> 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?
I did a quick linux kernel hack to support the versatile_pci
compatible PCI controller for realview-eb boards.
Using the new stable-0.12 branch of qemu and the new 'realview-eb'
machine type, scp'ing large files into qemu no longer hangs the
network on ARMv6 CPUs.
kernel patch (trivial but ugly):
http://gitorious.org/scottt/linux-arm/commits/realview-eb-qemu
realview-eb-qemu branch
kernel config:
http://scottt.tw/bug/qemu-network-hang/realview-eb-qemu_defconfig
prebuilt kernel zImage:
http://scottt.tw/bug/qemu-network-hang/zImage-2.6.32-realview-eb-qemu-v6
script to launch qemu:
http://scottt.tw/bug/qemu-network-hang/launch-qemu
I used the same rootfs.ext2 image that you uploaded.
Sorry for the late reply, other priorities intruded.
prev parent reply other threads:[~2009-12-16 3:09 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
2009-12-16 3:09 ` Scott Tsai [this message]
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=ef2f888d0912151909i53354f30pec27f4b9c3642db5@mail.gmail.com \
--to=scottt.tw@gmail.com \
--cc=aurelien@aurel32.net \
--cc=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).