On 19.03.2015 19:31, Mohammed Gamal wrote: > > On Wed, Mar 18, 2015 at 7:09 PM, Kevin O'Connor <ke...@koconnor.net > <mailto:ke...@koconnor.net>> wrote: > > On Wed, Mar 18, 2015 at 06:36:48PM +0100, Mohammed Gamal 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. > > To debug seabios issues, we need the full log - see: > http://www.seabios.org/Debugging > > But, your software versions are a bit old which makes diagnosing any > issues hard. I suggest updating to the latest software and seeing if > the problem is still present. > > -Kevin > > > Unfortunately I can't change that setup. The problem is also rather > sporadic so I have no other means to reproduce it and debug it. > I tried looking into the seabios code but it looks like the instruction > pointer is pointing at the default interrupt vector table entry > 'entry_iret_official'. I presume this means that was triggered with an > interrupt of some sort? The other register values don't seem to provide > any clues nevertheless.
I thought maybe this commit was relevant, https://git.ipxe.org/wimboot.git/commitdiff/1f11d05addc7aab9097b59e07680a0d1c05e34b3, but noticed you're not using wimboot at all... -- Robin
