From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:39677) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SCsMd-0004Ry-Vf for qemu-devel@nongnu.org; Wed, 28 Mar 2012 08:52:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SCsMc-0007fh-6A for qemu-devel@nongnu.org; Wed, 28 Mar 2012 08:52:35 -0400 Received: from thoth.sbs.de ([192.35.17.2]:27096) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SCsMb-0007fJ-Sd for qemu-devel@nongnu.org; Wed, 28 Mar 2012 08:52:34 -0400 Message-ID: <4F73098B.2050109@siemens.com> Date: Wed, 28 Mar 2012 14:52:27 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4F6C504B.3070506@siemens.com> <4F6C68D5.8010901@siemens.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Bug report for kvm-kmod-3.3! List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Katrina Austin Cc: "qemu-devel@nongnu.org" On 2012-03-28 14:44, Katrina Austin wrote: > Hi Jan, > Now I wanna to locate the instruction in the guest OS that causes this problem. However, I dont know how to make it as the guest OS has not yet started up. I would be much appreicated if you can provide some suggestions. Not sure if we discussed this already, but getting kvm-kmod from the list of suspects would be good, ie. testing original kvm over a recent kernel (3.3 or kvm.git). There is always the risk that some wrapping is broken and causes such an error. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux