From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:50294)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andrey@xdel.ru>) id 1YYHwy-0004xZ-Cs
	for qemu-devel@nongnu.org; Wed, 18 Mar 2015 13:40:13 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <andrey@xdel.ru>) id 1YYHwx-0002ci-Dd
	for qemu-devel@nongnu.org; Wed, 18 Mar 2015 13:40:12 -0400
Received: from mail-lb0-x22e.google.com ([2a00:1450:4010:c04::22e]:36859)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andrey@xdel.ru>) id 1YYHwx-0002Xk-2Z
	for qemu-devel@nongnu.org; Wed, 18 Mar 2015 13:40:11 -0400
Received: by lbblx11 with SMTP id lx11so13064346lbb.3
	for <qemu-devel@nongnu.org>; Wed, 18 Mar 2015 10:40:09 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <CAHTgm8LEGMZg+Gt6eFf3D2ig4swRCe+V6W6-1LM8urCAaNwJQw@mail.gmail.com>
References: <CAHTgm8LEGMZg+Gt6eFf3D2ig4swRCe+V6W6-1LM8urCAaNwJQw@mail.gmail.com>
From: Andrey Korolyov <andrey@xdel.ru>
Date: Wed, 18 Mar 2015 20:39:49 +0300
Message-ID: <CABYiri_EERXhXdmMw=1M-2vF8QRuaG4qF6JmFEsvQbkB72MU0g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Qemu-devel] Emulation failure on booting/rebooting VMs
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Mohammed Gamal <mohammed.gamal@profitbricks.com>
Cc: ipxe-devel@lists.ipxe.org, seabios@seabios.org, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

On Wed, Mar 18, 2015 at 8:36 PM, Mohammed Gamal
<mohammed.gamal@profitbricks.com> wrote:
> Hi,
> I've been sporadically getting my KVM virtual machines crashing with this
> message while they're booting
>
> KVM internal error. Suberror: 1
> emulation failure
> EAX=00000000 EBX=00000000 ECX=00000000 EDX=00600f12
> ESI=00000000 EDI=00000000 EBP=00000000 ESP=0000fffa
> EIP=0000ff53 EFL=00000006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
> ES =0000 00000000 0000ffff 00009300
> CS =f000 000f0000 0000ffff 00009b00
> SS =0000 00000000 0000ffff 00009200
> DS =0000 00000000 0000ffff 00009300
> FS =0000 00000000 0000ffff 00009300
> GS =0000 00000000 0000ffff 00009300
> LDT=0000 00000000 0000ffff 00008200
> TR =0000 00000000 0000ffff 00008300
> GDT=     00000000 0000ffff
> IDT=     00000000 0000ffff
> CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000
> DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
> DR3=0000000000000000
> DR6=00000000ffff0ff0 DR7=0000000000000400
> EFER=0000000000000000
> Code=74 65 61 6d 2e 00 66 68 5f 55 00 00 e9 c3 f8 fb f4 cb 66 c3 <cf> 66 68
> ff e6 00 00 e9 8b b1 66 55 66 57 66 56 66 53 66 89 c1 66 89 d6 a8 07 75 23
> 66 0f
>
> I am running qemu 1.2, seabios 1.7.3 and ipxe (1.0.0-f6840ba) and the host
> CPU is AMD Opteron 6386 SE running kernel 3.4.71.
>
> I digged a little into the kvm kernel module code and I can trace these
> emulation failures only to either a call to pf_interception() - which is
> highly unlikely since the machine doesn't appear to have setup paging yet -
> and task_switch_interception(). I am suspecting that ipxe or seabios might
> be executing some invalid code or something, since this failure only appears
> sporadically and is not 100% reproducible. Any ideas why this might be
> happening?
>
> Regards,
> Mohammed

Hello, would you mind to try seabios 1.8.1?