From: Richard Davies <richard@arachsys.com>
To: qemu-devel@nongnu.org, e1000-devel@lists.sourceforge.net
Cc: chris@arachsys.com, qemu.owentuz@gmail.com
Subject: Re: [Qemu-devel] Bug: E1000 kernel panic when transferring files over private network
Date: Thu, 16 Aug 2012 18:02:31 +0100 [thread overview]
Message-ID: <20120816170231.GA19294@alpha.arachsys.com> (raw)
In-Reply-To: <CAAhzb2Z4SGJKPcJuYoD6QJX6MzbcOY1rFWKfyPnDQVAerBMduw@mail.gmail.com>
Just to be clear - we are sure that it is the virtualization host networking
problems which are triggering this VM OS nic driver crash, and we haven't
described these here anything like well enough to reproduce the situation -
they are complex.
However, in the same situation, a VM with rtl8139 or virtio network cards
doesn't crash, so I believe that the e1000 crash is evidence of some kind of
bug in the e1000 driver which is triggered in our specific situation.
Hopefully the backtrace gives enough information to identify what that e1000
driver bug might be?
Richard.
prev parent reply other threads:[~2012-08-16 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 16:52 [Qemu-devel] Bug: E1000 kernel panic when transferring files over private network Owen Tuz
2012-08-16 17:02 ` Richard Davies [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=20120816170231.GA19294@alpha.arachsys.com \
--to=richard@arachsys.com \
--cc=chris@arachsys.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
--cc=qemu.owentuz@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).