From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:44417) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T23Ss-0005Ls-DX for qemu-devel@nongnu.org; Thu, 16 Aug 2012 13:02:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T23Sr-0004FX-G7 for qemu-devel@nongnu.org; Thu, 16 Aug 2012 13:02:34 -0400 Received: from alpha.arachsys.com ([91.203.57.7]:33601) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T23Sr-0004FO-9x for qemu-devel@nongnu.org; Thu, 16 Aug 2012 13:02:33 -0400 Date: Thu, 16 Aug 2012 18:02:31 +0100 From: Richard Davies Message-ID: <20120816170231.GA19294@alpha.arachsys.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] Bug: E1000 kernel panic when transferring files over private network List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, e1000-devel@lists.sourceforge.net Cc: chris@arachsys.com, qemu.owentuz@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.