openbsd system_powerdown: "KVM internal error. Suberror: 1"

openbsd system_powerdown: "KVM internal error. Suberror: 1"

[Michael Tokarev]

Hello.

I installed an openbsd 4.8 image today to play with,
and noticed that when issuing "system_powerdown" in
kvm monitor, in about 5 seconds, qemu-kvm spews this
message in a tight loop:

 KVM internal error. Suberror: 1
 emulation failure
 KVM internal error. Suberror: 1
 emulation failure
 ....

ad infinitum, until interrupted.

I verified the issue exists in 0.14 and 0.12 qemu-kvm,
both 32 and 64bits.

Freebsd does not trigger this behavour, it is running
normally.

kvm-0.12.5 behaves somewhat more sane in this case too,
it prints some more information:

 KVM internal error. Suberror: 1
 rax 0000000000000030 rbx 0000000000000000 rcx 0000000000000000 rdx 000000000000b100
 rsi 00000000d0201fc6 rdi 00000000d0ac1ad4 rsp 00000000d9651004 rbp 00000000d9759a38
 r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 0000000000000000
 r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000
 rip 00000000d0202041 rflags 00000292
 cs 0050 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
 ds 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
 es 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
 ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
 fs 0058 (d0ac1aa0/000003db p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
 gs 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
 tr 0078 (d9758000/00000333 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
 ldt 0018 (d0a31580/00000087 p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0)
 gdt d9575000/ffff
 idt d0a31620/7ff
 cr0 8001003b cr2 dcd0000 cr3 1f202000 cr4 780 cr8 3 efer 0
 emulation failure, check dmesg for details

As far as I can see, this is just a one-time message in 0.12.
Dmesg (on host) is completely silent.

-no-kvm-irqchip does not help either (I tried it for a different
reason but decided to check this case too, while at it).

Host kernel is 2.6.37-2 (with e5d135f80b98b0 + 2607b0533353c
applied after yesterdays freebsd issues), 64bit, running on
amd AthlonII CPU.  In all cases guests were with -smp 1, and
without any fancy options (just -hda & -m).  Openbsd 4.8 32bit.

I see two issues here: one is the emulation failure and another
is the erratic behavour of kvm-0.14 - issuing that error message
in a tight loop.

Thanks!

/mjt

Re: openbsd system_powerdown: "KVM internal error. Suberror: 1"

[Marcelo Tosatti]

On Fri, Mar 11, 2011 at 02:54:00PM +0300, Michael Tokarev wrote:
> Hello.
> 
> I installed an openbsd 4.8 image today to play with,
> and noticed that when issuing "system_powerdown" in
> kvm monitor, in about 5 seconds, qemu-kvm spews this
> message in a tight loop:
> 
>  KVM internal error. Suberror: 1
>  emulation failure
>  KVM internal error. Suberror: 1
>  emulation failure
>  ....
> 
> ad infinitum, until interrupted.
> 
> I verified the issue exists in 0.14 and 0.12 qemu-kvm,
> both 32 and 64bits.

> Freebsd does not trigger this behavour, it is running
> normally.
> 
> kvm-0.12.5 behaves somewhat more sane in this case too,
> it prints some more information:
> 
>  KVM internal error. Suberror: 1
>  rax 0000000000000030 rbx 0000000000000000 rcx 0000000000000000 rdx 000000000000b100
>  rsi 00000000d0201fc6 rdi 00000000d0ac1ad4 rsp 00000000d9651004 rbp 00000000d9759a38
>  r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 0000000000000000
>  r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000
>  rip 00000000d0202041 rflags 00000292
>  cs 0050 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
>  ds 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
>  es 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
>  ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
>  fs 0058 (d0ac1aa0/000003db p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
>  gs 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
>  tr 0078 (d9758000/00000333 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
>  ldt 0018 (d0a31580/00000087 p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0)
>  gdt d9575000/ffff
>  idt d0a31620/7ff
>  cr0 8001003b cr2 dcd0000 cr3 1f202000 cr4 780 cr8 3 efer 0
>  emulation failure, check dmesg for details

Michael,

Can you stop the guest and issue:

x/10i 0x00000000d0202041

> 
> As far as I can see, this is just a one-time message in 0.12.
> Dmesg (on host) is completely silent.
> 
> -no-kvm-irqchip does not help either (I tried it for a different
> reason but decided to check this case too, while at it).
> 
> Host kernel is 2.6.37-2 (with e5d135f80b98b0 + 2607b0533353c
> applied after yesterdays freebsd issues), 64bit, running on
> amd AthlonII CPU.  In all cases guests were with -smp 1, and
> without any fancy options (just -hda & -m).  Openbsd 4.8 32bit.
> 
> I see two issues here: one is the emulation failure and another
> is the erratic behavour of kvm-0.14 - issuing that error message
> in a tight loop.

Re: openbsd system_powerdown: "KVM internal error. Suberror: 1"

[Michael Tokarev]

16.03.2011 22:44, Marcelo Tosatti wrote:
> On Fri, Mar 11, 2011 at 02:54:00PM +0300, Michael Tokarev wrote:
>> Hello.
>>
>> I installed an openbsd 4.8 image today to play with,
>> and noticed that when issuing "system_powerdown" in
>> kvm monitor, in about 5 seconds, qemu-kvm spews this
>> message in a tight loop:
>>
>>  KVM internal error. Suberror: 1
>>  emulation failure
>>  KVM internal error. Suberror: 1
>>  emulation failure
>>  ....
>>
>> ad infinitum, until interrupted.
>>
>> I verified the issue exists in 0.14 and 0.12 qemu-kvm,
>> both 32 and 64bits.
> 
>> Freebsd does not trigger this behavour, it is running
>> normally.
>>
>> kvm-0.12.5 behaves somewhat more sane in this case too,
>> it prints some more information:
>>
>>  KVM internal error. Suberror: 1
>>  rax 0000000000000030 rbx 0000000000000000 rcx 0000000000000000 rdx 000000000000b100
>>  rsi 00000000d0201fc6 rdi 00000000d0ac1ad4 rsp 00000000d9651004 rbp 00000000d9759a38
>>  r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 0000000000000000
>>  r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000
>>  rip 00000000d0202041 rflags 00000292
[]
> Can you stop the guest and issue:
> 
> x/10i 0x00000000d0202041

(qemu) KVM internal error. Suberror: 1
rax 0000000000000030 rbx 0000000000000000 rcx 00000000d0a3200c rdx 0000000000000000
rsi 00000000d0201fc6 rdi 00000000d0ac1ad4 rsp 00000000d438d008 rbp 00000000d4495f08
r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000
rip 00000000d0202041 rflags 00000282
cs 0050 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
ds 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
es 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
fs 0058 (d0ac1aa0/000003db p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
gs 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
tr 0078 (d4494000/00000333 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
ldt 0018 (d0a31580/00000087 p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0)
gdt d42b1000/ffff
idt d0a31620/7ff
cr0 8001003b cr2 3c0029b0 cr3 71d8000 cr4 780 cr8 3 efer 0
emulation failure, check dmesg for details
(qemu) x/20i 0x00000000d0202036
0x00000000d0202036:  pop    %edi
0x00000000d0202037:  pop    %esi
0x00000000d0202038:  pop    %ebp
0x00000000d0202039:  pop    %ebx
0x00000000d020203a:  pop    %edx
0x00000000d020203b:  pop    %ecx
0x00000000d020203c:  pop    %eax
0x00000000d020203d:  sti
0x00000000d020203e:  add    $0x8,%esp
0x00000000d0202041:  iret
0x00000000d0202042:  mov    %esi,%esi
0x00000000d0202044:  mov    $0x70,%eax
0x00000000d0202049:  mov    %eax,0xd0990080
0x00000000d020204e:  sti
0x00000000d020204f:  push   $0x2
0x00000000d0202051:  call   0xd0570470
0x00000000d0202056:  add    $0x4,%esp
0x00000000d0202059:  jmp    *%esi
0x00000000d020205b:  nop
0x00000000d020205c:  mov    $0x40,%eax

The guest stops automatically after that message, so no need to
stop it.  The address (rip) is the same as before, so it's repeatable.

I was using 0.12.5 for this, with 0.14 it's impossible to do anything
after the "Emulation error" anymore, it spews these error messages too
fast.

What interesting is that there's some race condition somewhere
there: I tried 4 times, first the guest just suddenly rebooted
right after system_powerdown (not shut down, it was a sudden
reboot), next it went into the above situation, next (after
restart) it rebooted again, also suddenly, next it come into
emulation error.  It can do one or another, more or less randomly,
but the above emulation error is quite a bit more common.

Thanks!

/mjt

Re: openbsd system_powerdown: "KVM internal error. Suberror: 1"

[Marcelo Tosatti]

On Wed, Mar 16, 2011 at 11:09:11PM +0300, Michael Tokarev wrote:
> 16.03.2011 22:44, Marcelo Tosatti wrote:
> > On Fri, Mar 11, 2011 at 02:54:00PM +0300, Michael Tokarev wrote:
> >> Hello.
> >>
> >> I installed an openbsd 4.8 image today to play with,
> >> and noticed that when issuing "system_powerdown" in
> >> kvm monitor, in about 5 seconds, qemu-kvm spews this
> >> message in a tight loop:
> >>
> >>  KVM internal error. Suberror: 1
> >>  emulation failure
> >>  KVM internal error. Suberror: 1
> >>  emulation failure
> >>  ....
> >>
> >> ad infinitum, until interrupted.
> >>
> >> I verified the issue exists in 0.14 and 0.12 qemu-kvm,
> >> both 32 and 64bits.
> > 
> >> Freebsd does not trigger this behavour, it is running
> >> normally.
> >>
> >> kvm-0.12.5 behaves somewhat more sane in this case too,
> >> it prints some more information:
> >>
> >>  KVM internal error. Suberror: 1
> >>  rax 0000000000000030 rbx 0000000000000000 rcx 0000000000000000 rdx 000000000000b100
> >>  rsi 00000000d0201fc6 rdi 00000000d0ac1ad4 rsp 00000000d9651004 rbp 00000000d9759a38
> >>  r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 0000000000000000
> >>  r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000
> >>  rip 00000000d0202041 rflags 00000292
> []
> > Can you stop the guest and issue:
> > 
> > x/10i 0x00000000d0202041
> 
> (qemu) KVM internal error. Suberror: 1
> rax 0000000000000030 rbx 0000000000000000 rcx 00000000d0a3200c rdx 0000000000000000
> rsi 00000000d0201fc6 rdi 00000000d0ac1ad4 rsp 00000000d438d008 rbp 00000000d4495f08
> r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 0000000000000000
> r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000
> rip 00000000d0202041 rflags 00000282
> cs 0050 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
> ds 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
> es 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
> ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
> fs 0058 (d0ac1aa0/000003db p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
> gs 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
> tr 0078 (d4494000/00000333 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
> ldt 0018 (d0a31580/00000087 p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0)
> gdt d42b1000/ffff
> idt d0a31620/7ff
> cr0 8001003b cr2 3c0029b0 cr3 71d8000 cr4 780 cr8 3 efer 0
> emulation failure, check dmesg for details
> (qemu) x/20i 0x00000000d0202036
> 0x00000000d0202036:  pop    %edi
> 0x00000000d0202037:  pop    %esi
> 0x00000000d0202038:  pop    %ebp
> 0x00000000d0202039:  pop    %ebx
> 0x00000000d020203a:  pop    %edx
> 0x00000000d020203b:  pop    %ecx
> 0x00000000d020203c:  pop    %eax
> 0x00000000d020203d:  sti
> 0x00000000d020203e:  add    $0x8,%esp
> 0x00000000d0202041:  iret
> 0x00000000d0202042:  mov    %esi,%esi
> 0x00000000d0202044:  mov    $0x70,%eax
> 0x00000000d0202049:  mov    %eax,0xd0990080
> 0x00000000d020204e:  sti
> 0x00000000d020204f:  push   $0x2
> 0x00000000d0202051:  call   0xd0570470
> 0x00000000d0202056:  add    $0x4,%esp
> 0x00000000d0202059:  jmp    *%esi
> 0x00000000d020205b:  nop
> 0x00000000d020205c:  mov    $0x40,%eax
> 
> The guest stops automatically after that message, so no need to
> stop it.  The address (rip) is the same as before, so it's repeatable.
> 
> I was using 0.12.5 for this, with 0.14 it's impossible to do anything
> after the "Emulation error" anymore, it spews these error messages too
> fast.
> 
> What interesting is that there's some race condition somewhere
> there: I tried 4 times, first the guest just suddenly rebooted
> right after system_powerdown (not shut down, it was a sudden
> reboot), next it went into the above situation, next (after
> restart) it rebooted again, also suddenly, next it come into
> emulation error.  It can do one or another, more or less randomly,
> but the above emulation error is quite a bit more common.

iret emulation is only partially implemented. Why is iret faulting
in the first place i don't know. Can you enable tracing with

echo kvm > /$debugfs/tracing/set_event 

And save the tail of the log, including events at $RIP?

Re: openbsd system_powerdown: "KVM internal error. Suberror: 1"

[Michael Tokarev]

17.03.2011 20:52, Marcelo Tosatti wrote:
[]
> iret emulation is only partially implemented. Why is iret faulting
> in the first place i don't know. Can you enable tracing with
> 
> echo kvm > /$debugfs/tracing/set_event 
> 
> And save the tail of the log, including events at $RIP?

Something like the one below (with the error at the end)?

What do you mean "events at $RIP" ?  I see 2 patterns here
with references to $RIP.  Many like this:

      kvm-0.12.5-1301  [001] 47965.427622: kvm_page_fault: address fee00080 error_code 6
      kvm-0.12.5-1301  [001] 47965.427622: kvm_emulate_insn: 0:d0202002: 89 1d 80 00 99 d0 (prot32)
      kvm-0.12.5-1301  [001] 47965.427623: kvm_mmio: mmio write len 4 gpa 0xfee00080 val 0x30
      kvm-0.12.5-1301  [001] 47965.427623: kvm_apic: apic_write APIC_TASKPRI = 0x30
      kvm-0.12.5-1301  [001] 47965.427624: kvm_entry: vcpu 0
      kvm-0.12.5-1301  [001] 47965.427625: kvm_exit: reason vintr rip 0xd0202041
      kvm-0.12.5-1301  [001] 47965.427625: kvm_inj_virq: irq 81
      kvm-0.12.5-1301  [001] 47965.427625: kvm_inj_virq: irq 81
      kvm-0.12.5-1301  [001] 47965.427626: kvm_entry: vcpu 0
      kvm-0.12.5-1301  [001] 47965.427627: kvm_exit: reason npf rip 0xd02024f1
      kvm-0.12.5-1301  [001] 47965.427627: kvm_page_fault: address fee00080 error_code 4

which are repeated without changes over and over again.
And at the end, several like this:

      kvm-0.12.5-1301  [001] 47965.428634: kvm_entry: vcpu 0
      kvm-0.12.5-1301  [001] 47965.428635: kvm_exit: reason npf rip 0xd020203a
      kvm-0.12.5-1301  [001] 47965.428635: kvm_page_fault: address bfffc error_code 4
      kvm-0.12.5-1301  [001] 47965.428635: kvm_emulate_insn: 0:d020203a: 5a (prot32)
      kvm-0.12.5-1301  [001] 47965.428636: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfffc val 0x0
      kvm-0.12.5-1301  [001] 47965.428637: kvm_mmio: mmio read len 4 gpa 0xbfffc val 0xb100
      kvm-0.12.5-1301  [001] 47965.428637: kvm_entry: vcpu 0
      kvm-0.12.5-1301  [001] 47965.428638: kvm_exit: reason vintr rip 0xd0202041
      kvm-0.12.5-1301  [001] 47965.428638: kvm_inj_virq: irq 81
      kvm-0.12.5-1301  [001] 47965.428638: kvm_inj_virq: irq 81
      kvm-0.12.5-1301  [001] 47965.428639: kvm_entry: vcpu 0
      kvm-0.12.5-1301  [001] 47965.428640: kvm_exit: reason npf rip 0xd02024cc
      kvm-0.12.5-1301  [001] 47965.428640: kvm_page_fault: address bfffc error_code 6
      kvm-0.12.5-1301  [001] 47965.428640: kvm_emulate_insn: 0:d02024cc: 6a 03 (prot32)
      kvm-0.12.5-1301  [001] 47965.428641: kvm_mmio: mmio write len 4 gpa 0xbfffc val 0x3

(with different kvm_emulate_insn each time), which finally ends with
      kvm-0.12.5-1301  [001] 47965.428804: kvm_emulate_insn: 0:d0202041: cf (prot32)
      kvm-0.12.5-1301  [001] 47965.428805: kvm_emulate_insn: 0:d0202041: cf (prot32) failed

Note it's the same openbsd which triggers insane amount of
host_state_reloads, so the trace is quite, well, large :)

Thanks!

/mjt

$ kvm-0.12.5 -drive file=obsd.raw,snapshot=on -net none -monitor stdio
QEMU 0.12.5 monitor - type 'help' for more information
(qemu) system_powerdown
(qemu) KVM internal error. Suberror: 1
rax 0000000000000030 rbx 0000000000000000 rcx 0000000000000000 rdx 000000000000b100
rsi 00000000d0201fc6 rdi 00000000d0ac1ad4 rsp 00000000d438d004 rbp 00000000d4492e1c
r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000
rip 00000000d0202041 rflags 00000292
cs 0050 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
ds 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
es 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
fs 0058 (d0ac1aa0/000003db p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
gs 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
tr 0078 (d4491000/00000333 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
ldt 0018 (d0a31580/00000087 p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0)
gdt d42b1000/ffff
idt d0a31620/7ff
cr0 8001003b cr2 8adaa850 cr3 7370000 cr4 780 cr8 3 efer 0
emulation failure, check dmesg for details

(qemu) x/20i 0x00000000d0202036
0x00000000d0202036:  pop    %edi
0x00000000d0202037:  pop    %esi
0x00000000d0202038:  pop    %ebp
0x00000000d0202039:  pop    %ebx
0x00000000d020203a:  pop    %edx
0x00000000d020203b:  pop    %ecx
0x00000000d020203c:  pop    %eax
0x00000000d020203d:  sti
0x00000000d020203e:  add    $0x8,%esp
0x00000000d0202041:  iret
0x00000000d0202042:  mov    %esi,%esi
0x00000000d0202044:  mov    $0x70,%eax
0x00000000d0202049:  mov    %eax,0xd0990080
0x00000000d020204e:  sti
0x00000000d020204f:  push   $0x2
0x00000000d0202051:  call   0xd0570470
0x00000000d0202056:  add    $0x4,%esp
0x00000000d0202059:  jmp    *%esi
0x00000000d020205b:  nop
0x00000000d020205c:  mov    $0x40,%eax
(qemu) q

# tail -500 /sys/kernel/debug/tracing/trace | sed 's|^.*\] ||'

47965.428524: kvm_page_fault: address bffd4 error_code 6
47965.428524: kvm_emulate_insn: 0:d0202534: 50 (prot32)
47965.428525: kvm_mmio: mmio write len 4 gpa 0xbffd4 val 0xd0ec7b00
47965.428525: kvm_entry: vcpu 0
47965.428526: kvm_exit: reason npf rip 0xd0202535
47965.428526: kvm_page_fault: address bffd0 error_code 6
47965.428527: kvm_emulate_insn: 0:d0202535: ff 53 00 (prot32)
47965.428527: kvm_mmio: mmio write len 4 gpa 0xbffd0 val 0xd0202538
47965.428528: kvm_entry: vcpu 0
47965.428529: kvm_exit: reason npf rip 0xd06e53d0
47965.428529: kvm_page_fault: address bffcc error_code 6
47965.428529: kvm_emulate_insn: 0:d06e53d0: 55 (prot32)
47965.428529: kvm_mmio: mmio write len 4 gpa 0xbffcc val 0xd438cfd4
47965.428530: kvm_entry: vcpu 0
47965.428531: kvm_exit: reason npf rip 0xd06e53d6
47965.428531: kvm_page_fault: address bffc4 error_code 6
47965.428531: kvm_emulate_insn: 0:d06e53d6: 89 75 f8 (prot32)
47965.428532: kvm_mmio: mmio write len 4 gpa 0xbffc4 val 0xd0201fc6
47965.428532: kvm_entry: vcpu 0
47965.428533: kvm_exit: reason npf rip 0xd06e53d9
47965.428533: kvm_page_fault: address bffd4 error_code 4
47965.428534: kvm_emulate_insn: 0:d06e53d9: 8b 75 08 (prot32)
47965.428534: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffd4 val 0x0
47965.428536: kvm_mmio: mmio read len 4 gpa 0xbffd4 val 0xd0ec7b00
47965.428536: kvm_entry: vcpu 0
47965.428537: kvm_exit: reason npf rip 0xd06e53dc
47965.428537: kvm_page_fault: address bffc0 error_code 6
47965.428538: kvm_emulate_insn: 0:d06e53dc: 89 5d f4 (prot32)
47965.428538: kvm_mmio: mmio write len 4 gpa 0xbffc0 val 0xd0eea840
47965.428539: kvm_entry: vcpu 0
47965.428540: kvm_exit: reason npf rip 0xd06e53df
47965.428540: kvm_page_fault: address bffc8 error_code 6
47965.428541: kvm_emulate_insn: 0:d06e53df: 89 7d fc (prot32)
47965.428541: kvm_mmio: mmio write len 4 gpa 0xbffc8 val 0xd0ac1ad4
47965.428541: kvm_entry: vcpu 0
47965.428542: kvm_exit: reason npf rip 0xd06e53e2
47965.428542: kvm_page_fault: address bffac error_code 6
47965.428543: kvm_emulate_insn: 0:d06e53e2: c7 44 24 08 00 00 00 00 (prot32)
47965.428543: kvm_mmio: mmio write len 4 gpa 0xbffac val 0x0
47965.428543: kvm_entry: vcpu 0
47965.428544: kvm_exit: reason npf rip 0xd06e53ed
47965.428545: kvm_page_fault: address bffa8 error_code 6
47965.428545: kvm_emulate_insn: 0:d06e53ed: 89 44 24 04 (prot32)
47965.428545: kvm_mmio: mmio write len 4 gpa 0xbffa8 val 0xb100
47965.428546: kvm_entry: vcpu 0
47965.428547: kvm_exit: reason npf rip 0xd06e53f4
47965.428547: kvm_page_fault: address bffa4 error_code 6
47965.428547: kvm_emulate_insn: 0:d06e53f4: 89 04 24 (prot32)
47965.428548: kvm_mmio: mmio write len 4 gpa 0xbffa4 val 0x0
47965.428548: kvm_entry: vcpu 0
47965.428549: kvm_exit: reason npf rip 0xd06e53f7
47965.428549: kvm_page_fault: address bffa0 error_code 6
47965.428550: kvm_emulate_insn: 0:d06e53f7: e8 94 98 e7 ff (prot32)
47965.428550: kvm_mmio: mmio write len 4 gpa 0xbffa0 val 0xd06e53fc
47965.428550: kvm_entry: vcpu 0
47965.428551: kvm_exit: reason npf rip 0xd055ec90
47965.428551: kvm_page_fault: address bff9c error_code 6
47965.428552: kvm_emulate_insn: 0:d055ec90: 55 (prot32)
47965.428552: kvm_mmio: mmio write len 4 gpa 0xbff9c val 0xd438cfcc
47965.428553: kvm_entry: vcpu 0
47965.428554: kvm_exit: reason npf rip 0xd055ec93
47965.428554: kvm_page_fault: address bffa4 error_code 4
47965.428554: kvm_emulate_insn: 0:d055ec93: 8b 45 08 (prot32)
47965.428555: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffa4 val 0x0
47965.428557: kvm_mmio: mmio read len 4 gpa 0xbffa4 val 0x0
47965.428557: kvm_entry: vcpu 0
47965.428558: kvm_exit: reason npf rip 0xd055eca8
47965.428558: kvm_page_fault: address bffac error_code 4
47965.428559: kvm_emulate_insn: 0:d055eca8: 8b 55 10 (prot32)
47965.428559: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffac val 0x0
47965.428560: kvm_mmio: mmio read len 4 gpa 0xbffac val 0x0
47965.428561: kvm_entry: vcpu 0
47965.428562: kvm_exit: reason npf rip 0xd055ecab
47965.428562: kvm_page_fault: address bffa8 error_code 4
47965.428562: kvm_emulate_insn: 0:d055ecab: 03 55 0c (prot32)
47965.428563: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffa8 val 0x0
47965.428564: kvm_mmio: mmio read len 4 gpa 0xbffa8 val 0xb100
47965.428564: kvm_entry: vcpu 0
47965.428565: kvm_exit: reason io rip 0xd055ecae
47965.428565: kvm_emulate_insn: 0:d055ecae: ec (prot32)
47965.428565: kvm_pio: pio_read at 0xb100 size 1 count 1
47965.428567: kvm_entry: vcpu 0
47965.428568: kvm_exit: reason npf rip 0xd055ecaf
47965.428568: kvm_page_fault: address bff9c error_code 4
47965.428569: kvm_emulate_insn: 0:d055ecaf: 5d (prot32)
47965.428569: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbff9c val 0x0
47965.428570: kvm_mmio: mmio read len 4 gpa 0xbff9c val 0xd438cfcc
47965.428570: kvm_entry: vcpu 0
47965.428571: kvm_exit: reason npf rip 0xd055ecb3
47965.428572: kvm_page_fault: address bffa0 error_code 4
47965.428572: kvm_emulate_insn: 0:d055ecb3: c3 (prot32)
47965.428573: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffa0 val 0x0
47965.428574: kvm_mmio: mmio read len 4 gpa 0xbffa0 val 0xd06e53fc
47965.428574: kvm_entry: vcpu 0
47965.428575: kvm_exit: reason npf rip 0xd06e540b
47965.428575: kvm_page_fault: address bffc0 error_code 4
47965.428576: kvm_emulate_insn: 0:d06e540b: 8b 5d f4 (prot32)
47965.428576: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffc0 val 0x0
47965.428577: kvm_mmio: mmio read len 4 gpa 0xbffc0 val 0xd0eea840
47965.428578: kvm_entry: vcpu 0
47965.428579: kvm_exit: reason npf rip 0xd06e540e
47965.428579: kvm_page_fault: address bffc4 error_code 4
47965.428579: kvm_emulate_insn: 0:d06e540e: 8b 75 f8 (prot32)
47965.428580: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffc4 val 0x0
47965.428581: kvm_mmio: mmio read len 4 gpa 0xbffc4 val 0xd0201fc6
47965.428581: kvm_entry: vcpu 0
47965.428582: kvm_exit: reason npf rip 0xd06e5411
47965.428582: kvm_page_fault: address bffc8 error_code 4
47965.428583: kvm_emulate_insn: 0:d06e5411: 8b 7d fc (prot32)
47965.428584: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffc8 val 0x0
47965.428585: kvm_mmio: mmio read len 4 gpa 0xbffc8 val 0xd0ac1ad4
47965.428585: kvm_entry: vcpu 0
47965.428586: kvm_exit: reason npf rip 0xd06e5416
47965.428586: kvm_page_fault: address bffcc error_code 4
47965.428587: kvm_emulate_insn: 0:d06e5416: 5d (prot32)
47965.428587: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffcc val 0x0
47965.428588: kvm_mmio: mmio read len 4 gpa 0xbffcc val 0xd438cfd4
47965.428589: kvm_entry: vcpu 0
47965.428590: kvm_exit: reason npf rip 0xd06e5417
47965.428590: kvm_page_fault: address bffd0 error_code 4
47965.428590: kvm_emulate_insn: 0:d06e5417: c3 (prot32)
47965.428591: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffd0 val 0x0
47965.428592: kvm_mmio: mmio read len 4 gpa 0xbffd0 val 0xd0202538
47965.428592: kvm_entry: vcpu 0
47965.428593: kvm_exit: reason npf rip 0xd0202554
47965.428593: kvm_page_fault: address fee000b0 error_code 6
47965.428594: kvm_emulate_insn: 0:d0202554: c7 05 b0 00 99 d0 00 00 00 00 (prot32)
47965.428594: kvm_mmio: mmio write len 4 gpa 0xfee000b0 val 0x0
47965.428594: kvm_apic: apic_write APIC_EOI = 0x0
47965.428595: kvm_ack_irq: irqchip IOAPIC pin 9
47965.428595: kvm_apic_accept_irq: apicid 0 vec 81 (Fixed|level)
47965.428595: kvm_entry: vcpu 0
47965.428596: kvm_exit: reason npf rip 0xd0201fc0
47965.428596: kvm_page_fault: address bffd8 error_code 4
47965.428597: kvm_emulate_insn: 0:d0201fc0: 5b (prot32)
47965.428598: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffd8 val 0x0
47965.428599: kvm_mmio: mmio read len 4 gpa 0xbffd8 val 0x30
47965.428599: kvm_entry: vcpu 0
47965.428600: kvm_exit: reason npf rip 0xd0202002
47965.428600: kvm_page_fault: address fee00080 error_code 6
47965.428601: kvm_emulate_insn: 0:d0202002: 89 1d 80 00 99 d0 (prot32)
47965.428601: kvm_mmio: mmio write len 4 gpa 0xfee00080 val 0x30
47965.428601: kvm_apic: apic_write APIC_TASKPRI = 0x30
47965.428603: kvm_entry: vcpu 0
47965.428604: kvm_exit: reason npf rip 0xd0202030
47965.428604: kvm_page_fault: address bffdc error_code 4
47965.428605: kvm_emulate_insn: 0:d0202030: 0f a1 (prot32)
47965.428605: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffdc val 0x0
47965.428606: kvm_mmio: mmio read len 4 gpa 0xbffdc val 0x58
47965.428607: kvm_entry: vcpu 0
47965.428608: kvm_exit: reason npf rip 0xd0202032
47965.428608: kvm_page_fault: address bffe0 error_code 4
47965.428609: kvm_emulate_insn: 0:d0202032: 0f a9 (prot32)
47965.428609: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffe0 val 0x0
47965.428610: kvm_mmio: mmio read len 4 gpa 0xbffe0 val 0x10
47965.428611: kvm_entry: vcpu 0
47965.428612: kvm_exit: reason npf rip 0xd0202034
47965.428612: kvm_page_fault: address bffe4 error_code 4
47965.428613: kvm_emulate_insn: 0:d0202034: 07 (prot32)
47965.428613: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffe4 val 0x0
47965.428614: kvm_mmio: mmio read len 4 gpa 0xbffe4 val 0x10
47965.428615: kvm_entry: vcpu 0
47965.428616: kvm_exit: reason npf rip 0xd0202035
47965.428616: kvm_page_fault: address bffe8 error_code 4
47965.428617: kvm_emulate_insn: 0:d0202035: 1f (prot32)
47965.428617: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffe8 val 0x0
47965.428618: kvm_mmio: mmio read len 4 gpa 0xbffe8 val 0x10
47965.428619: kvm_entry: vcpu 0
47965.428620: kvm_exit: reason npf rip 0xd0202036
47965.428620: kvm_page_fault: address bffec error_code 4
47965.428621: kvm_emulate_insn: 0:d0202036: 5f (prot32)
47965.428621: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffec val 0x0
47965.428622: kvm_mmio: mmio read len 4 gpa 0xbffec val 0xd0ac1ad4
47965.428623: kvm_entry: vcpu 0
47965.428624: kvm_exit: reason npf rip 0xd0202037
47965.428624: kvm_page_fault: address bfff0 error_code 4
47965.428624: kvm_emulate_insn: 0:d0202037: 5e (prot32)
47965.428625: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff0 val 0x0
47965.428626: kvm_mmio: mmio read len 4 gpa 0xbfff0 val 0xd0201fc6
47965.428626: kvm_entry: vcpu 0
47965.428627: kvm_exit: reason npf rip 0xd0202038
47965.428627: kvm_page_fault: address bfff4 error_code 4
47965.428628: kvm_emulate_insn: 0:d0202038: 5d (prot32)
47965.428628: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff4 val 0x0
47965.428630: kvm_mmio: mmio read len 4 gpa 0xbfff4 val 0xd4492e1c
47965.428630: kvm_entry: vcpu 0
47965.428631: kvm_exit: reason npf rip 0xd0202039
47965.428631: kvm_page_fault: address bfff8 error_code 4
47965.428632: kvm_emulate_insn: 0:d0202039: 5b (prot32)
47965.428632: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff8 val 0x0
47965.428633: kvm_mmio: mmio read len 4 gpa 0xbfff8 val 0x0
47965.428634: kvm_entry: vcpu 0
47965.428635: kvm_exit: reason npf rip 0xd020203a
47965.428635: kvm_page_fault: address bfffc error_code 4
47965.428635: kvm_emulate_insn: 0:d020203a: 5a (prot32)
47965.428636: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfffc val 0x0
47965.428637: kvm_mmio: mmio read len 4 gpa 0xbfffc val 0xb100
47965.428637: kvm_entry: vcpu 0
47965.428638: kvm_exit: reason vintr rip 0xd0202041
47965.428638: kvm_inj_virq: irq 81
47965.428638: kvm_inj_virq: irq 81
47965.428639: kvm_entry: vcpu 0
47965.428640: kvm_exit: reason npf rip 0xd02024cc
47965.428640: kvm_page_fault: address bfffc error_code 6
47965.428640: kvm_emulate_insn: 0:d02024cc: 6a 03 (prot32)
47965.428641: kvm_mmio: mmio write len 4 gpa 0xbfffc val 0x3
47965.428641: kvm_entry: vcpu 0
47965.428642: kvm_exit: reason npf rip 0xd02024ce
47965.428642: kvm_page_fault: address bfff8 error_code 6
47965.428643: kvm_emulate_insn: 0:d02024ce: 50 (prot32)
47965.428643: kvm_mmio: mmio write len 4 gpa 0xbfff8 val 0x30
47965.428643: kvm_entry: vcpu 0
47965.428645: kvm_exit: reason npf rip 0xd02024cf
47965.428645: kvm_page_fault: address bfff4 error_code 6
47965.428645: kvm_emulate_insn: 0:d02024cf: 51 (prot32)
47965.428646: kvm_mmio: mmio write len 4 gpa 0xbfff4 val 0x0
47965.428646: kvm_entry: vcpu 0
47965.428647: kvm_exit: reason npf rip 0xd02024d0
47965.428647: kvm_page_fault: address bfff0 error_code 6
47965.428648: kvm_emulate_insn: 0:d02024d0: 52 (prot32)
47965.428648: kvm_mmio: mmio write len 4 gpa 0xbfff0 val 0xb100
47965.428648: kvm_entry: vcpu 0
47965.428649: kvm_exit: reason npf rip 0xd02024d1
47965.428649: kvm_page_fault: address bffec error_code 6
47965.428650: kvm_emulate_insn: 0:d02024d1: 53 (prot32)
47965.428650: kvm_mmio: mmio write len 4 gpa 0xbffec val 0x0
47965.428651: kvm_entry: vcpu 0
47965.428652: kvm_exit: reason npf rip 0xd02024d2
47965.428652: kvm_page_fault: address bffe8 error_code 6
47965.428652: kvm_emulate_insn: 0:d02024d2: 55 (prot32)
47965.428653: kvm_mmio: mmio write len 4 gpa 0xbffe8 val 0xd4492e1c
47965.428653: kvm_entry: vcpu 0
47965.428654: kvm_exit: reason npf rip 0xd02024d3
47965.428654: kvm_page_fault: address bffe4 error_code 6
47965.428655: kvm_emulate_insn: 0:d02024d3: 56 (prot32)
47965.428655: kvm_mmio: mmio write len 4 gpa 0xbffe4 val 0xd0201fc6
47965.428655: kvm_entry: vcpu 0
47965.428656: kvm_exit: reason npf rip 0xd02024d4
47965.428656: kvm_page_fault: address bffe0 error_code 6
47965.428657: kvm_emulate_insn: 0:d02024d4: 57 (prot32)
47965.428657: kvm_mmio: mmio write len 4 gpa 0xbffe0 val 0xd0ac1ad4
47965.428657: kvm_entry: vcpu 0
47965.428658: kvm_exit: reason npf rip 0xd02024d5
47965.428658: kvm_page_fault: address bffdc error_code 6
47965.428659: kvm_emulate_insn: 0:d02024d5: 1e (prot32)
47965.428659: kvm_mmio: mmio write len 4 gpa 0xbffdc val 0x10
47965.428660: kvm_entry: vcpu 0
47965.428661: kvm_exit: reason npf rip 0xd02024d6
47965.428661: kvm_page_fault: address bffd8 error_code 6
47965.428662: kvm_emulate_insn: 0:d02024d6: 06 (prot32)
47965.428662: kvm_mmio: mmio write len 4 gpa 0xbffd8 val 0x10
47965.428662: kvm_entry: vcpu 0
47965.428663: kvm_exit: reason npf rip 0xd02024d7
47965.428663: kvm_page_fault: address bffd4 error_code 6
47965.428664: kvm_emulate_insn: 0:d02024d7: 0f a8 (prot32)
47965.428664: kvm_mmio: mmio write len 4 gpa 0xbffd4 val 0x10
47965.428665: kvm_entry: vcpu 0
47965.428666: kvm_exit: reason npf rip 0xd02024e4
47965.428666: kvm_page_fault: address bffd0 error_code 6
47965.428666: kvm_emulate_insn: 0:d02024e4: 0f a0 (prot32)
47965.428666: kvm_mmio: mmio write len 4 gpa 0xbffd0 val 0x58
47965.428667: kvm_entry: vcpu 0
47965.428668: kvm_exit: reason npf rip 0xd02024f1
47965.428668: kvm_page_fault: address fee00080 error_code 4
47965.428668: kvm_emulate_insn: 0:d02024f1: ff 35 80 00 99 d0 (prot32)
47965.428669: kvm_apic: apic_read APIC_TASKPRI = 0x30
47965.428669: kvm_mmio: mmio read len 4 gpa 0xfee00080 val 0x30
47965.428669: kvm_mmio: mmio write len 4 gpa 0xbffcc val 0x30
47965.428672: kvm_entry: vcpu 0
47965.428673: kvm_exit: reason npf rip 0xd02024f7
47965.428673: kvm_page_fault: address fee000a0 error_code 4
47965.428674: kvm_emulate_insn: 0:d02024f7: a1 a0 00 99 d0 (prot32)
47965.428674: kvm_apic: apic_read APIC_PROCPRI = 0x50
47965.428674: kvm_mmio: mmio read len 4 gpa 0xfee000a0 val 0x50
47965.428675: kvm_entry: vcpu 0
47965.428676: kvm_exit: reason npf rip 0xd0202506
47965.428676: kvm_page_fault: address fee00080 error_code 6
47965.428677: kvm_emulate_insn: 0:d0202506: 89 1d 80 00 99 d0 (prot32)
47965.428677: kvm_mmio: mmio write len 4 gpa 0xfee00080 val 0x50
47965.428677: kvm_apic: apic_write APIC_TASKPRI = 0x50
47965.428678: kvm_entry: vcpu 0
47965.428679: kvm_exit: reason npf rip 0xd0202534
47965.428680: kvm_page_fault: address bffc8 error_code 6
47965.428680: kvm_emulate_insn: 0:d0202534: 50 (prot32)
47965.428680: kvm_mmio: mmio write len 4 gpa 0xbffc8 val 0xd0ec7b00
47965.428681: kvm_entry: vcpu 0
47965.428682: kvm_exit: reason npf rip 0xd0202535
47965.428682: kvm_page_fault: address bffc4 error_code 6
47965.428683: kvm_emulate_insn: 0:d0202535: ff 53 00 (prot32)
47965.428683: kvm_mmio: mmio write len 4 gpa 0xbffc4 val 0xd0202538
47965.428683: kvm_entry: vcpu 0
47965.428684: kvm_exit: reason npf rip 0xd06e53d0
47965.428685: kvm_page_fault: address bffc0 error_code 6
47965.428685: kvm_emulate_insn: 0:d06e53d0: 55 (prot32)
47965.428685: kvm_mmio: mmio write len 4 gpa 0xbffc0 val 0xd438cfc8
47965.428686: kvm_entry: vcpu 0
47965.428687: kvm_exit: reason npf rip 0xd06e53d6
47965.428687: kvm_page_fault: address bffb8 error_code 6
47965.428687: kvm_emulate_insn: 0:d06e53d6: 89 75 f8 (prot32)
47965.428688: kvm_mmio: mmio write len 4 gpa 0xbffb8 val 0xd0201fc6
47965.428688: kvm_entry: vcpu 0
47965.428689: kvm_exit: reason npf rip 0xd06e53d9
47965.428689: kvm_page_fault: address bffc8 error_code 4
47965.428690: kvm_emulate_insn: 0:d06e53d9: 8b 75 08 (prot32)
47965.428690: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffc8 val 0x0
47965.428692: kvm_mmio: mmio read len 4 gpa 0xbffc8 val 0xd0ec7b00
47965.428692: kvm_entry: vcpu 0
47965.428693: kvm_exit: reason npf rip 0xd06e53dc
47965.428693: kvm_page_fault: address bffb4 error_code 6
47965.428694: kvm_emulate_insn: 0:d06e53dc: 89 5d f4 (prot32)
47965.428694: kvm_mmio: mmio write len 4 gpa 0xbffb4 val 0xd0eea840
47965.428695: kvm_entry: vcpu 0
47965.428696: kvm_exit: reason npf rip 0xd06e53df
47965.428696: kvm_page_fault: address bffbc error_code 6
47965.428696: kvm_emulate_insn: 0:d06e53df: 89 7d fc (prot32)
47965.428697: kvm_mmio: mmio write len 4 gpa 0xbffbc val 0xd0ac1ad4
47965.428697: kvm_entry: vcpu 0
47965.428698: kvm_exit: reason npf rip 0xd06e53e2
47965.428698: kvm_page_fault: address bffa0 error_code 6
47965.428699: kvm_emulate_insn: 0:d06e53e2: c7 44 24 08 00 00 00 00 (prot32)
47965.428699: kvm_mmio: mmio write len 4 gpa 0xbffa0 val 0x0
47965.428699: kvm_entry: vcpu 0
47965.428700: kvm_exit: reason npf rip 0xd06e53ed
47965.428700: kvm_page_fault: address bff9c error_code 6
47965.428701: kvm_emulate_insn: 0:d06e53ed: 89 44 24 04 (prot32)
47965.428701: kvm_mmio: mmio write len 4 gpa 0xbff9c val 0xb100
47965.428701: kvm_entry: vcpu 0
47965.428703: kvm_exit: reason npf rip 0xd06e53f4
47965.428703: kvm_page_fault: address bff98 error_code 6
47965.428703: kvm_emulate_insn: 0:d06e53f4: 89 04 24 (prot32)
47965.428704: kvm_mmio: mmio write len 4 gpa 0xbff98 val 0x0
47965.428704: kvm_entry: vcpu 0
47965.428705: kvm_exit: reason npf rip 0xd06e53f7
47965.428705: kvm_page_fault: address bff94 error_code 6
47965.428706: kvm_emulate_insn: 0:d06e53f7: e8 94 98 e7 ff (prot32)
47965.428706: kvm_mmio: mmio write len 4 gpa 0xbff94 val 0xd06e53fc
47965.428706: kvm_entry: vcpu 0
47965.428707: kvm_exit: reason npf rip 0xd055ec90
47965.428707: kvm_page_fault: address bff90 error_code 6
47965.428708: kvm_emulate_insn: 0:d055ec90: 55 (prot32)
47965.428708: kvm_mmio: mmio write len 4 gpa 0xbff90 val 0xd438cfc0
47965.428709: kvm_entry: vcpu 0
47965.428710: kvm_exit: reason npf rip 0xd055ec93
47965.428710: kvm_page_fault: address bff98 error_code 4
47965.428710: kvm_emulate_insn: 0:d055ec93: 8b 45 08 (prot32)
47965.428711: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbff98 val 0x0
47965.428712: kvm_mmio: mmio read len 4 gpa 0xbff98 val 0x0
47965.428713: kvm_entry: vcpu 0
47965.428714: kvm_exit: reason npf rip 0xd055eca8
47965.428714: kvm_page_fault: address bffa0 error_code 4
47965.428715: kvm_emulate_insn: 0:d055eca8: 8b 55 10 (prot32)
47965.428715: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffa0 val 0x0
47965.428716: kvm_mmio: mmio read len 4 gpa 0xbffa0 val 0x0
47965.428717: kvm_entry: vcpu 0
47965.428718: kvm_exit: reason npf rip 0xd055ecab
47965.428718: kvm_page_fault: address bff9c error_code 4
47965.428718: kvm_emulate_insn: 0:d055ecab: 03 55 0c (prot32)
47965.428719: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbff9c val 0x0
47965.428720: kvm_mmio: mmio read len 4 gpa 0xbff9c val 0xb100
47965.428721: kvm_entry: vcpu 0
47965.428721: kvm_exit: reason io rip 0xd055ecae
47965.428722: kvm_emulate_insn: 0:d055ecae: ec (prot32)
47965.428722: kvm_pio: pio_read at 0xb100 size 1 count 1
47965.428723: kvm_entry: vcpu 0
47965.428724: kvm_exit: reason npf rip 0xd055ecaf
47965.428725: kvm_page_fault: address bff90 error_code 4
47965.428725: kvm_emulate_insn: 0:d055ecaf: 5d (prot32)
47965.428726: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbff90 val 0x0
47965.428727: kvm_mmio: mmio read len 4 gpa 0xbff90 val 0xd438cfc0
47965.428727: kvm_entry: vcpu 0
47965.428728: kvm_exit: reason npf rip 0xd055ecb3
47965.428728: kvm_page_fault: address bff94 error_code 4
47965.428729: kvm_emulate_insn: 0:d055ecb3: c3 (prot32)
47965.428729: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbff94 val 0x0
47965.428730: kvm_mmio: mmio read len 4 gpa 0xbff94 val 0xd06e53fc
47965.428731: kvm_entry: vcpu 0
47965.428732: kvm_exit: reason npf rip 0xd06e540b
47965.428732: kvm_page_fault: address bffb4 error_code 4
47965.428732: kvm_emulate_insn: 0:d06e540b: 8b 5d f4 (prot32)
47965.428733: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffb4 val 0x0
47965.428734: kvm_mmio: mmio read len 4 gpa 0xbffb4 val 0xd0eea840
47965.428734: kvm_entry: vcpu 0
47965.428735: kvm_exit: reason npf rip 0xd06e540e
47965.428735: kvm_page_fault: address bffb8 error_code 4
47965.428736: kvm_emulate_insn: 0:d06e540e: 8b 75 f8 (prot32)
47965.428736: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffb8 val 0x0
47965.428737: kvm_mmio: mmio read len 4 gpa 0xbffb8 val 0xd0201fc6
47965.428738: kvm_entry: vcpu 0
47965.428739: kvm_exit: reason npf rip 0xd06e5411
47965.428739: kvm_page_fault: address bffbc error_code 4
47965.428740: kvm_emulate_insn: 0:d06e5411: 8b 7d fc (prot32)
47965.428740: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffbc val 0x0
47965.428741: kvm_mmio: mmio read len 4 gpa 0xbffbc val 0xd0ac1ad4
47965.428741: kvm_entry: vcpu 0
47965.428742: kvm_exit: reason npf rip 0xd06e5416
47965.428743: kvm_page_fault: address bffc0 error_code 4
47965.428743: kvm_emulate_insn: 0:d06e5416: 5d (prot32)
47965.428743: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffc0 val 0x0
47965.428745: kvm_mmio: mmio read len 4 gpa 0xbffc0 val 0xd438cfc8
47965.428745: kvm_entry: vcpu 0
47965.428746: kvm_exit: reason npf rip 0xd06e5417
47965.428746: kvm_page_fault: address bffc4 error_code 4
47965.428747: kvm_emulate_insn: 0:d06e5417: c3 (prot32)
47965.428747: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffc4 val 0x0
47965.428748: kvm_mmio: mmio read len 4 gpa 0xbffc4 val 0xd0202538
47965.428748: kvm_entry: vcpu 0
47965.428749: kvm_exit: reason npf rip 0xd0202554
47965.428750: kvm_page_fault: address fee000b0 error_code 6
47965.428750: kvm_emulate_insn: 0:d0202554: c7 05 b0 00 99 d0 00 00 00 00 (prot32)
47965.428751: kvm_mmio: mmio write len 4 gpa 0xfee000b0 val 0x0
47965.428751: kvm_apic: apic_write APIC_EOI = 0x0
47965.428751: kvm_ack_irq: irqchip IOAPIC pin 9
47965.428751: kvm_apic_accept_irq: apicid 0 vec 81 (Fixed|level)
47965.428752: kvm_entry: vcpu 0
47965.428753: kvm_exit: reason npf rip 0xd0201fc0
47965.428753: kvm_page_fault: address bffcc error_code 4
47965.428753: kvm_emulate_insn: 0:d0201fc0: 5b (prot32)
47965.428754: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffcc val 0x0
47965.428755: kvm_mmio: mmio read len 4 gpa 0xbffcc val 0x30
47965.428755: kvm_entry: vcpu 0
47965.428756: kvm_exit: reason npf rip 0xd0202002
47965.428756: kvm_page_fault: address fee00080 error_code 6
47965.428757: kvm_emulate_insn: 0:d0202002: 89 1d 80 00 99 d0 (prot32)
47965.428757: kvm_mmio: mmio write len 4 gpa 0xfee00080 val 0x30
47965.428757: kvm_apic: apic_write APIC_TASKPRI = 0x30
47965.428759: kvm_entry: vcpu 0
47965.428760: kvm_exit: reason npf rip 0xd0202030
47965.428760: kvm_page_fault: address bffd0 error_code 4
47965.428760: kvm_emulate_insn: 0:d0202030: 0f a1 (prot32)
47965.428761: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffd0 val 0x0
47965.428762: kvm_mmio: mmio read len 4 gpa 0xbffd0 val 0x58
47965.428763: kvm_entry: vcpu 0
47965.428764: kvm_exit: reason npf rip 0xd0202032
47965.428764: kvm_page_fault: address bffd4 error_code 4
47965.428765: kvm_emulate_insn: 0:d0202032: 0f a9 (prot32)
47965.428765: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffd4 val 0x0
47965.428766: kvm_mmio: mmio read len 4 gpa 0xbffd4 val 0x10
47965.428767: kvm_entry: vcpu 0
47965.428768: kvm_exit: reason npf rip 0xd0202034
47965.428768: kvm_page_fault: address bffd8 error_code 4
47965.428769: kvm_emulate_insn: 0:d0202034: 07 (prot32)
47965.428769: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffd8 val 0x0
47965.428770: kvm_mmio: mmio read len 4 gpa 0xbffd8 val 0x10
47965.428771: kvm_entry: vcpu 0
47965.428772: kvm_exit: reason npf rip 0xd0202035
47965.428772: kvm_page_fault: address bffdc error_code 4
47965.428773: kvm_emulate_insn: 0:d0202035: 1f (prot32)
47965.428773: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffdc val 0x0
47965.428774: kvm_mmio: mmio read len 4 gpa 0xbffdc val 0x10
47965.428775: kvm_entry: vcpu 0
47965.428776: kvm_exit: reason npf rip 0xd0202036
47965.428776: kvm_page_fault: address bffe0 error_code 4
47965.428777: kvm_emulate_insn: 0:d0202036: 5f (prot32)
47965.428777: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffe0 val 0x0
47965.428778: kvm_mmio: mmio read len 4 gpa 0xbffe0 val 0xd0ac1ad4
47965.428779: kvm_entry: vcpu 0
47965.428780: kvm_exit: reason npf rip 0xd0202037
47965.428780: kvm_page_fault: address bffe4 error_code 4
47965.428780: kvm_emulate_insn: 0:d0202037: 5e (prot32)
47965.428781: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffe4 val 0x0
47965.428782: kvm_mmio: mmio read len 4 gpa 0xbffe4 val 0xd0201fc6
47965.428782: kvm_entry: vcpu 0
47965.428783: kvm_exit: reason npf rip 0xd0202038
47965.428783: kvm_page_fault: address bffe8 error_code 4
47965.428784: kvm_emulate_insn: 0:d0202038: 5d (prot32)
47965.428784: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffe8 val 0x0
47965.428786: kvm_mmio: mmio read len 4 gpa 0xbffe8 val 0xd4492e1c
47965.428786: kvm_entry: vcpu 0
47965.428787: kvm_exit: reason npf rip 0xd0202039
47965.428788: kvm_page_fault: address bffec error_code 4
47965.428788: kvm_emulate_insn: 0:d0202039: 5b (prot32)
47965.428789: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffec val 0x0
47965.428790: kvm_mmio: mmio read len 4 gpa 0xbffec val 0x0
47965.428790: kvm_entry: vcpu 0
47965.428791: kvm_exit: reason npf rip 0xd020203a
47965.428791: kvm_page_fault: address bfff0 error_code 4
47965.428792: kvm_emulate_insn: 0:d020203a: 5a (prot32)
47965.428792: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff0 val 0x0
47965.428793: kvm_mmio: mmio read len 4 gpa 0xbfff0 val 0xb100
47965.428794: kvm_entry: vcpu 0
47965.428795: kvm_exit: reason npf rip 0xd020203b
47965.428795: kvm_page_fault: address bfff4 error_code 4
47965.428795: kvm_emulate_insn: 0:d020203b: 59 (prot32)
47965.428796: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff4 val 0x0
47965.428797: kvm_mmio: mmio read len 4 gpa 0xbfff4 val 0x0
47965.428797: kvm_entry: vcpu 0
47965.428798: kvm_exit: reason npf rip 0xd020203c
47965.428798: kvm_page_fault: address bfff8 error_code 4
47965.428799: kvm_emulate_insn: 0:d020203c: 58 (prot32)
47965.428799: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff8 val 0x0
47965.428801: kvm_mmio: mmio read len 4 gpa 0xbfff8 val 0x30
47965.428801: kvm_entry: vcpu 0
47965.428802: kvm_exit: reason vintr rip 0xd0202041
47965.428802: kvm_inj_virq: irq 81
47965.428802: kvm_inj_virq: irq 81
47965.428803: kvm_entry: vcpu 0
47965.428803: kvm_exit: reason npf rip 0xd0202041
47965.428804: kvm_page_fault: address bfffc error_code 6
47965.428804: kvm_emulate_insn: 0:d0202041: cf (prot32)
47965.428805: kvm_emulate_insn: 0:d0202041: cf (prot32) failed

Re: openbsd system_powerdown: "KVM internal error. Suberror: 1"

[Avi Kivity]

On 03/17/2011 10:18 PM, Michael Tokarev wrote:
> 17.03.2011 20:52, Marcelo Tosatti wrote:
> []
> >  iret emulation is only partially implemented. Why is iret faulting
> >  in the first place i don't know. Can you enable tracing with
> >
> >  echo kvm>  /$debugfs/tracing/set_event
> >
> >  And save the tail of the log, including events at $RIP?
>
> Something like the one below (with the error at the end)?
>
> What do you mean "events at $RIP" ?  I see 2 patterns here
> with references to $RIP.  Many like this:
>
>        kvm-0.12.5-1301  [001] 47965.427622: kvm_page_fault: address fee00080 error_code 6
>        kvm-0.12.5-1301  [001] 47965.427622: kvm_emulate_insn: 0:d0202002: 89 1d 80 00 99 d0 (prot32)
>        kvm-0.12.5-1301  [001] 47965.427623: kvm_mmio: mmio write len 4 gpa 0xfee00080 val 0x30
>        kvm-0.12.5-1301  [001] 47965.427623: kvm_apic: apic_write APIC_TASKPRI = 0x30
>        kvm-0.12.5-1301  [001] 47965.427624: kvm_entry: vcpu 0
>        kvm-0.12.5-1301  [001] 47965.427625: kvm_exit: reason vintr rip 0xd0202041
>        kvm-0.12.5-1301  [001] 47965.427625: kvm_inj_virq: irq 81
>        kvm-0.12.5-1301  [001] 47965.427625: kvm_inj_virq: irq 81
>        kvm-0.12.5-1301  [001] 47965.427626: kvm_entry: vcpu 0
>        kvm-0.12.5-1301  [001] 47965.427627: kvm_exit: reason npf rip 0xd02024f1
>        kvm-0.12.5-1301  [001] 47965.427627: kvm_page_fault: address fee00080 error_code 4
>
> which are repeated without changes over and over again.
> And at the end, several like this:
>
>        kvm-0.12.5-1301  [001] 47965.428634: kvm_entry: vcpu 0
>        kvm-0.12.5-1301  [001] 47965.428635: kvm_exit: reason npf rip 0xd020203a
>        kvm-0.12.5-1301  [001] 47965.428635: kvm_page_fault: address bfffc error_code 4
>        kvm-0.12.5-1301  [001] 47965.428635: kvm_emulate_insn: 0:d020203a: 5a (prot32)
>        kvm-0.12.5-1301  [001] 47965.428636: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfffc val 0x0
>        kvm-0.12.5-1301  [001] 47965.428637: kvm_mmio: mmio read len 4 gpa 0xbfffc val 0xb100
>        kvm-0.12.5-1301  [001] 47965.428637: kvm_entry: vcpu 0
>        kvm-0.12.5-1301  [001] 47965.428638: kvm_exit: reason vintr rip 0xd0202041
>        kvm-0.12.5-1301  [001] 47965.428638: kvm_inj_virq: irq 81
>        kvm-0.12.5-1301  [001] 47965.428638: kvm_inj_virq: irq 81
>        kvm-0.12.5-1301  [001] 47965.428639: kvm_entry: vcpu 0
>        kvm-0.12.5-1301  [001] 47965.428640: kvm_exit: reason npf rip 0xd02024cc
>        kvm-0.12.5-1301  [001] 47965.428640: kvm_page_fault: address bfffc error_code 6
>        kvm-0.12.5-1301  [001] 47965.428640: kvm_emulate_insn: 0:d02024cc: 6a 03 (prot32)
>        kvm-0.12.5-1301  [001] 47965.428641: kvm_mmio: mmio write len 4 gpa 0xbfffc val 0x3
>
> (with different kvm_emulate_insn each time), which finally ends with
>        kvm-0.12.5-1301  [001] 47965.428804: kvm_emulate_insn: 0:d0202041: cf (prot32)
>        kvm-0.12.5-1301  [001] 47965.428805: kvm_emulate_insn: 0:d0202041: cf (prot32) failed
>
> Note it's the same openbsd which triggers insane amount of
> host_state_reloads, so the trace is quite, well, large :)
>
> Thanks!
>
> /mjt
>
> $ kvm-0.12.5 -drive file=obsd.raw,snapshot=on -net none -monitor stdio
> QEMU 0.12.5 monitor - type 'help' for more information
> (qemu) system_powerdown
> (qemu) KVM internal error. Suberror: 1
> rax 0000000000000030 rbx 0000000000000000 rcx 0000000000000000 rdx 000000000000b100
> rsi 00000000d0201fc6 rdi 00000000d0ac1ad4 rsp 00000000d438d004 rbp 00000000d4492e1c
> r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 0000000000000000
> r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000
> rip 00000000d0202041 rflags 00000292
> cs 0050 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
> ds 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
> es 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
> ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
> fs 0058 (d0ac1aa0/000003db p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
> gs 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
> tr 0078 (d4491000/00000333 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
> ldt 0018 (d0a31580/00000087 p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0)
> gdt d42b1000/ffff
> idt d0a31620/7ff
> cr0 8001003b cr2 8adaa850 cr3 7370000 cr4 780 cr8 3 efer 0
> emulation failure, check dmesg for details
>
> (qemu) x/20i 0x00000000d0202036
> 0x00000000d0202036:  pop    %edi
> 0x00000000d0202037:  pop    %esi
> 0x00000000d0202038:  pop    %ebp
> 0x00000000d0202039:  pop    %ebx
> 0x00000000d020203a:  pop    %edx
> 0x00000000d020203b:  pop    %ecx
> 0x00000000d020203c:  pop    %eax
> 0x00000000d020203d:  sti
> 0x00000000d020203e:  add    $0x8,%esp
> 0x00000000d0202041:  iret
> 0x00000000d0202042:  mov    %esi,%esi
> 0x00000000d0202044:  mov    $0x70,%eax
> 0x00000000d0202049:  mov    %eax,0xd0990080
> 0x00000000d020204e:  sti
> 0x00000000d020204f:  push   $0x2
> 0x00000000d0202051:  call   0xd0570470
> 0x00000000d0202056:  add    $0x4,%esp
> 0x00000000d0202059:  jmp    *%esi
> 0x00000000d020205b:  nop
> 0x00000000d020205c:  mov    $0x40,%eax
> (qemu) q
>
> # tail -500 /sys/kernel/debug/tracing/trace | sed 's|^.*\] ||'
>
> 47965.428524: kvm_page_fault: address bffd4 error_code 6
> 47965.428524: kvm_emulate_insn: 0:d0202534: 50 (prot32)
> 47965.428525: kvm_mmio: mmio write len 4 gpa 0xbffd4 val 0xd0ec7b00
> 47965.428525: kvm_entry: vcpu 0
> 47965.428526: kvm_exit: reason npf rip 0xd0202535
> 47965.428526: kvm_page_fault: address bffd0 error_code 6
> 47965.428527: kvm_emulate_insn: 0:d0202535: ff 53 00 (prot32)
> 47965.428527: kvm_mmio: mmio write len 4 gpa 0xbffd0 val 0xd0202538
> 47965.428528: kvm_entry: vcpu 0
> 47965.428529: kvm_exit: reason npf rip 0xd06e53d0
> 47965.428529: kvm_page_fault: address bffcc error_code 6
> 47965.428529: kvm_emulate_insn: 0:d06e53d0: 55 (prot32)
> 47965.428529: kvm_mmio: mmio write len 4 gpa 0xbffcc val 0xd438cfd4
> 47965.428530: kvm_entry: vcpu 0
> 47965.428531: kvm_exit: reason npf rip 0xd06e53d6
> 47965.428531: kvm_page_fault: address bffc4 error_code 6
> 47965.428531: kvm_emulate_insn: 0:d06e53d6: 89 75 f8 (prot32)
> 47965.428532: kvm_mmio: mmio write len 4 gpa 0xbffc4 val 0xd0201fc6
> 47965.428532: kvm_entry: vcpu 0
> 47965.428533: kvm_exit: reason npf rip 0xd06e53d9
> 47965.428533: kvm_page_fault: address bffd4 error_code 4
> 47965.428534: kvm_emulate_insn: 0:d06e53d9: 8b 75 08 (prot32)
> 47965.428534: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffd4 val 0x0
> 47965.428536: kvm_mmio: mmio read len 4 gpa 0xbffd4 val 0xd0ec7b00
> 47965.428536: kvm_entry: vcpu 0
> 47965.428537: kvm_exit: reason npf rip 0xd06e53dc
> 47965.428537: kvm_page_fault: address bffc0 error_code 6
> 47965.428538: kvm_emulate_insn: 0:d06e53dc: 89 5d f4 (prot32)
> 47965.428538: kvm_mmio: mmio write len 4 gpa 0xbffc0 val 0xd0eea840
> 47965.428539: kvm_entry: vcpu 0
> 47965.428540: kvm_exit: reason npf rip 0xd06e53df
> 47965.428540: kvm_page_fault: address bffc8 error_code 6
> 47965.428541: kvm_emulate_insn: 0:d06e53df: 89 7d fc (prot32)
> 47965.428541: kvm_mmio: mmio write len 4 gpa 0xbffc8 val 0xd0ac1ad4
> 47965.428541: kvm_entry: vcpu 0
> 47965.428542: kvm_exit: reason npf rip 0xd06e53e2
> 47965.428542: kvm_page_fault: address bffac error_code 6
> 47965.428543: kvm_emulate_insn: 0:d06e53e2: c7 44 24 08 00 00 00 00 (prot32)
> 47965.428543: kvm_mmio: mmio write len 4 gpa 0xbffac val 0x0
> 47965.428543: kvm_entry: vcpu 0
> 47965.428544: kvm_exit: reason npf rip 0xd06e53ed
> 47965.428545: kvm_page_fault: address bffa8 error_code 6
> 47965.428545: kvm_emulate_insn: 0:d06e53ed: 89 44 24 04 (prot32)
> 47965.428545: kvm_mmio: mmio write len 4 gpa 0xbffa8 val 0xb100
> 47965.428546: kvm_entry: vcpu 0
> 47965.428547: kvm_exit: reason npf rip 0xd06e53f4
> 47965.428547: kvm_page_fault: address bffa4 error_code 6
> 47965.428547: kvm_emulate_insn: 0:d06e53f4: 89 04 24 (prot32)
> 47965.428548: kvm_mmio: mmio write len 4 gpa 0xbffa4 val 0x0
> 47965.428548: kvm_entry: vcpu 0
> 47965.428549: kvm_exit: reason npf rip 0xd06e53f7
> 47965.428549: kvm_page_fault: address bffa0 error_code 6
> 47965.428550: kvm_emulate_insn: 0:d06e53f7: e8 94 98 e7 ff (prot32)
> 47965.428550: kvm_mmio: mmio write len 4 gpa 0xbffa0 val 0xd06e53fc
> 47965.428550: kvm_entry: vcpu 0
> 47965.428551: kvm_exit: reason npf rip 0xd055ec90
> 47965.428551: kvm_page_fault: address bff9c error_code 6
> 47965.428552: kvm_emulate_insn: 0:d055ec90: 55 (prot32)
> 47965.428552: kvm_mmio: mmio write len 4 gpa 0xbff9c val 0xd438cfcc
> 47965.428553: kvm_entry: vcpu 0
> 47965.428554: kvm_exit: reason npf rip 0xd055ec93
> 47965.428554: kvm_page_fault: address bffa4 error_code 4
> 47965.428554: kvm_emulate_insn: 0:d055ec93: 8b 45 08 (prot32)
> 47965.428555: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffa4 val 0x0
> 47965.428557: kvm_mmio: mmio read len 4 gpa 0xbffa4 val 0x0
> 47965.428557: kvm_entry: vcpu 0
> 47965.428558: kvm_exit: reason npf rip 0xd055eca8
> 47965.428558: kvm_page_fault: address bffac error_code 4
> 47965.428559: kvm_emulate_insn: 0:d055eca8: 8b 55 10 (prot32)
> 47965.428559: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffac val 0x0
> 47965.428560: kvm_mmio: mmio read len 4 gpa 0xbffac val 0x0
> 47965.428561: kvm_entry: vcpu 0
> 47965.428562: kvm_exit: reason npf rip 0xd055ecab
> 47965.428562: kvm_page_fault: address bffa8 error_code 4
> 47965.428562: kvm_emulate_insn: 0:d055ecab: 03 55 0c (prot32)
> 47965.428563: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffa8 val 0x0
> 47965.428564: kvm_mmio: mmio read len 4 gpa 0xbffa8 val 0xb100
> 47965.428564: kvm_entry: vcpu 0
> 47965.428565: kvm_exit: reason io rip 0xd055ecae
> 47965.428565: kvm_emulate_insn: 0:d055ecae: ec (prot32)
> 47965.428565: kvm_pio: pio_read at 0xb100 size 1 count 1
> 47965.428567: kvm_entry: vcpu 0
> 47965.428568: kvm_exit: reason npf rip 0xd055ecaf
> 47965.428568: kvm_page_fault: address bff9c error_code 4
> 47965.428569: kvm_emulate_insn: 0:d055ecaf: 5d (prot32)
> 47965.428569: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbff9c val 0x0
> 47965.428570: kvm_mmio: mmio read len 4 gpa 0xbff9c val 0xd438cfcc
> 47965.428570: kvm_entry: vcpu 0
> 47965.428571: kvm_exit: reason npf rip 0xd055ecb3
> 47965.428572: kvm_page_fault: address bffa0 error_code 4
> 47965.428572: kvm_emulate_insn: 0:d055ecb3: c3 (prot32)
> 47965.428573: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffa0 val 0x0
> 47965.428574: kvm_mmio: mmio read len 4 gpa 0xbffa0 val 0xd06e53fc
> 47965.428574: kvm_entry: vcpu 0
> 47965.428575: kvm_exit: reason npf rip 0xd06e540b
> 47965.428575: kvm_page_fault: address bffc0 error_code 4
> 47965.428576: kvm_emulate_insn: 0:d06e540b: 8b 5d f4 (prot32)
> 47965.428576: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffc0 val 0x0
> 47965.428577: kvm_mmio: mmio read len 4 gpa 0xbffc0 val 0xd0eea840
> 47965.428578: kvm_entry: vcpu 0
> 47965.428579: kvm_exit: reason npf rip 0xd06e540e
> 47965.428579: kvm_page_fault: address bffc4 error_code 4
> 47965.428579: kvm_emulate_insn: 0:d06e540e: 8b 75 f8 (prot32)
> 47965.428580: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffc4 val 0x0
> 47965.428581: kvm_mmio: mmio read len 4 gpa 0xbffc4 val 0xd0201fc6
> 47965.428581: kvm_entry: vcpu 0
> 47965.428582: kvm_exit: reason npf rip 0xd06e5411
> 47965.428582: kvm_page_fault: address bffc8 error_code 4
> 47965.428583: kvm_emulate_insn: 0:d06e5411: 8b 7d fc (prot32)
> 47965.428584: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffc8 val 0x0
> 47965.428585: kvm_mmio: mmio read len 4 gpa 0xbffc8 val 0xd0ac1ad4
> 47965.428585: kvm_entry: vcpu 0
> 47965.428586: kvm_exit: reason npf rip 0xd06e5416
> 47965.428586: kvm_page_fault: address bffcc error_code 4
> 47965.428587: kvm_emulate_insn: 0:d06e5416: 5d (prot32)
> 47965.428587: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffcc val 0x0
> 47965.428588: kvm_mmio: mmio read len 4 gpa 0xbffcc val 0xd438cfd4
> 47965.428589: kvm_entry: vcpu 0
> 47965.428590: kvm_exit: reason npf rip 0xd06e5417
> 47965.428590: kvm_page_fault: address bffd0 error_code 4
> 47965.428590: kvm_emulate_insn: 0:d06e5417: c3 (prot32)
> 47965.428591: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffd0 val 0x0
> 47965.428592: kvm_mmio: mmio read len 4 gpa 0xbffd0 val 0xd0202538
> 47965.428592: kvm_entry: vcpu 0
> 47965.428593: kvm_exit: reason npf rip 0xd0202554
> 47965.428593: kvm_page_fault: address fee000b0 error_code 6
> 47965.428594: kvm_emulate_insn: 0:d0202554: c7 05 b0 00 99 d0 00 00 00 00 (prot32)
> 47965.428594: kvm_mmio: mmio write len 4 gpa 0xfee000b0 val 0x0
> 47965.428594: kvm_apic: apic_write APIC_EOI = 0x0
> 47965.428595: kvm_ack_irq: irqchip IOAPIC pin 9
> 47965.428595: kvm_apic_accept_irq: apicid 0 vec 81 (Fixed|level)
> 47965.428595: kvm_entry: vcpu 0
> 47965.428596: kvm_exit: reason npf rip 0xd0201fc0
> 47965.428596: kvm_page_fault: address bffd8 error_code 4
> 47965.428597: kvm_emulate_insn: 0:d0201fc0: 5b (prot32)
> 47965.428598: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffd8 val 0x0
> 47965.428599: kvm_mmio: mmio read len 4 gpa 0xbffd8 val 0x30
> 47965.428599: kvm_entry: vcpu 0
> 47965.428600: kvm_exit: reason npf rip 0xd0202002
> 47965.428600: kvm_page_fault: address fee00080 error_code 6
> 47965.428601: kvm_emulate_insn: 0:d0202002: 89 1d 80 00 99 d0 (prot32)
> 47965.428601: kvm_mmio: mmio write len 4 gpa 0xfee00080 val 0x30
> 47965.428601: kvm_apic: apic_write APIC_TASKPRI = 0x30
> 47965.428603: kvm_entry: vcpu 0
> 47965.428604: kvm_exit: reason npf rip 0xd0202030
> 47965.428604: kvm_page_fault: address bffdc error_code 4
> 47965.428605: kvm_emulate_insn: 0:d0202030: 0f a1 (prot32)
> 47965.428605: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffdc val 0x0
> 47965.428606: kvm_mmio: mmio read len 4 gpa 0xbffdc val 0x58
> 47965.428607: kvm_entry: vcpu 0
> 47965.428608: kvm_exit: reason npf rip 0xd0202032
> 47965.428608: kvm_page_fault: address bffe0 error_code 4
> 47965.428609: kvm_emulate_insn: 0:d0202032: 0f a9 (prot32)
> 47965.428609: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffe0 val 0x0
> 47965.428610: kvm_mmio: mmio read len 4 gpa 0xbffe0 val 0x10
> 47965.428611: kvm_entry: vcpu 0
> 47965.428612: kvm_exit: reason npf rip 0xd0202034
> 47965.428612: kvm_page_fault: address bffe4 error_code 4
> 47965.428613: kvm_emulate_insn: 0:d0202034: 07 (prot32)
> 47965.428613: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffe4 val 0x0
> 47965.428614: kvm_mmio: mmio read len 4 gpa 0xbffe4 val 0x10
> 47965.428615: kvm_entry: vcpu 0
> 47965.428616: kvm_exit: reason npf rip 0xd0202035
> 47965.428616: kvm_page_fault: address bffe8 error_code 4
> 47965.428617: kvm_emulate_insn: 0:d0202035: 1f (prot32)
> 47965.428617: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffe8 val 0x0
> 47965.428618: kvm_mmio: mmio read len 4 gpa 0xbffe8 val 0x10
> 47965.428619: kvm_entry: vcpu 0
> 47965.428620: kvm_exit: reason npf rip 0xd0202036
> 47965.428620: kvm_page_fault: address bffec error_code 4
> 47965.428621: kvm_emulate_insn: 0:d0202036: 5f (prot32)
> 47965.428621: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffec val 0x0
> 47965.428622: kvm_mmio: mmio read len 4 gpa 0xbffec val 0xd0ac1ad4
> 47965.428623: kvm_entry: vcpu 0
> 47965.428624: kvm_exit: reason npf rip 0xd0202037
> 47965.428624: kvm_page_fault: address bfff0 error_code 4
> 47965.428624: kvm_emulate_insn: 0:d0202037: 5e (prot32)
> 47965.428625: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff0 val 0x0
> 47965.428626: kvm_mmio: mmio read len 4 gpa 0xbfff0 val 0xd0201fc6
> 47965.428626: kvm_entry: vcpu 0
> 47965.428627: kvm_exit: reason npf rip 0xd0202038
> 47965.428627: kvm_page_fault: address bfff4 error_code 4
> 47965.428628: kvm_emulate_insn: 0:d0202038: 5d (prot32)
> 47965.428628: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff4 val 0x0
> 47965.428630: kvm_mmio: mmio read len 4 gpa 0xbfff4 val 0xd4492e1c
> 47965.428630: kvm_entry: vcpu 0
> 47965.428631: kvm_exit: reason npf rip 0xd0202039
> 47965.428631: kvm_page_fault: address bfff8 error_code 4
> 47965.428632: kvm_emulate_insn: 0:d0202039: 5b (prot32)
> 47965.428632: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff8 val 0x0
> 47965.428633: kvm_mmio: mmio read len 4 gpa 0xbfff8 val 0x0
> 47965.428634: kvm_entry: vcpu 0
> 47965.428635: kvm_exit: reason npf rip 0xd020203a
> 47965.428635: kvm_page_fault: address bfffc error_code 4
> 47965.428635: kvm_emulate_insn: 0:d020203a: 5a (prot32)
> 47965.428636: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfffc val 0x0
> 47965.428637: kvm_mmio: mmio read len 4 gpa 0xbfffc val 0xb100
> 47965.428637: kvm_entry: vcpu 0
> 47965.428638: kvm_exit: reason vintr rip 0xd0202041
> 47965.428638: kvm_inj_virq: irq 81
> 47965.428638: kvm_inj_virq: irq 81
> 47965.428639: kvm_entry: vcpu 0
> 47965.428640: kvm_exit: reason npf rip 0xd02024cc
> 47965.428640: kvm_page_fault: address bfffc error_code 6
> 47965.428640: kvm_emulate_insn: 0:d02024cc: 6a 03 (prot32)
> 47965.428641: kvm_mmio: mmio write len 4 gpa 0xbfffc val 0x3
> 47965.428641: kvm_entry: vcpu 0
> 47965.428642: kvm_exit: reason npf rip 0xd02024ce
> 47965.428642: kvm_page_fault: address bfff8 error_code 6
> 47965.428643: kvm_emulate_insn: 0:d02024ce: 50 (prot32)
> 47965.428643: kvm_mmio: mmio write len 4 gpa 0xbfff8 val 0x30
> 47965.428643: kvm_entry: vcpu 0
> 47965.428645: kvm_exit: reason npf rip 0xd02024cf
> 47965.428645: kvm_page_fault: address bfff4 error_code 6
> 47965.428645: kvm_emulate_insn: 0:d02024cf: 51 (prot32)
> 47965.428646: kvm_mmio: mmio write len 4 gpa 0xbfff4 val 0x0
> 47965.428646: kvm_entry: vcpu 0
> 47965.428647: kvm_exit: reason npf rip 0xd02024d0
> 47965.428647: kvm_page_fault: address bfff0 error_code 6
> 47965.428648: kvm_emulate_insn: 0:d02024d0: 52 (prot32)
> 47965.428648: kvm_mmio: mmio write len 4 gpa 0xbfff0 val 0xb100
> 47965.428648: kvm_entry: vcpu 0
> 47965.428649: kvm_exit: reason npf rip 0xd02024d1
> 47965.428649: kvm_page_fault: address bffec error_code 6
> 47965.428650: kvm_emulate_insn: 0:d02024d1: 53 (prot32)
> 47965.428650: kvm_mmio: mmio write len 4 gpa 0xbffec val 0x0
> 47965.428651: kvm_entry: vcpu 0
> 47965.428652: kvm_exit: reason npf rip 0xd02024d2
> 47965.428652: kvm_page_fault: address bffe8 error_code 6
> 47965.428652: kvm_emulate_insn: 0:d02024d2: 55 (prot32)
> 47965.428653: kvm_mmio: mmio write len 4 gpa 0xbffe8 val 0xd4492e1c
> 47965.428653: kvm_entry: vcpu 0
> 47965.428654: kvm_exit: reason npf rip 0xd02024d3
> 47965.428654: kvm_page_fault: address bffe4 error_code 6
> 47965.428655: kvm_emulate_insn: 0:d02024d3: 56 (prot32)
> 47965.428655: kvm_mmio: mmio write len 4 gpa 0xbffe4 val 0xd0201fc6
> 47965.428655: kvm_entry: vcpu 0
> 47965.428656: kvm_exit: reason npf rip 0xd02024d4
> 47965.428656: kvm_page_fault: address bffe0 error_code 6
> 47965.428657: kvm_emulate_insn: 0:d02024d4: 57 (prot32)
> 47965.428657: kvm_mmio: mmio write len 4 gpa 0xbffe0 val 0xd0ac1ad4
> 47965.428657: kvm_entry: vcpu 0
> 47965.428658: kvm_exit: reason npf rip 0xd02024d5
> 47965.428658: kvm_page_fault: address bffdc error_code 6
> 47965.428659: kvm_emulate_insn: 0:d02024d5: 1e (prot32)
> 47965.428659: kvm_mmio: mmio write len 4 gpa 0xbffdc val 0x10
> 47965.428660: kvm_entry: vcpu 0
> 47965.428661: kvm_exit: reason npf rip 0xd02024d6
> 47965.428661: kvm_page_fault: address bffd8 error_code 6
> 47965.428662: kvm_emulate_insn: 0:d02024d6: 06 (prot32)
> 47965.428662: kvm_mmio: mmio write len 4 gpa 0xbffd8 val 0x10
> 47965.428662: kvm_entry: vcpu 0
> 47965.428663: kvm_exit: reason npf rip 0xd02024d7
> 47965.428663: kvm_page_fault: address bffd4 error_code 6
> 47965.428664: kvm_emulate_insn: 0:d02024d7: 0f a8 (prot32)
> 47965.428664: kvm_mmio: mmio write len 4 gpa 0xbffd4 val 0x10
> 47965.428665: kvm_entry: vcpu 0
> 47965.428666: kvm_exit: reason npf rip 0xd02024e4
> 47965.428666: kvm_page_fault: address bffd0 error_code 6
> 47965.428666: kvm_emulate_insn: 0:d02024e4: 0f a0 (prot32)
> 47965.428666: kvm_mmio: mmio write len 4 gpa 0xbffd0 val 0x58
> 47965.428667: kvm_entry: vcpu 0
> 47965.428668: kvm_exit: reason npf rip 0xd02024f1
> 47965.428668: kvm_page_fault: address fee00080 error_code 4
> 47965.428668: kvm_emulate_insn: 0:d02024f1: ff 35 80 00 99 d0 (prot32)
> 47965.428669: kvm_apic: apic_read APIC_TASKPRI = 0x30
> 47965.428669: kvm_mmio: mmio read len 4 gpa 0xfee00080 val 0x30
> 47965.428669: kvm_mmio: mmio write len 4 gpa 0xbffcc val 0x30
> 47965.428672: kvm_entry: vcpu 0
> 47965.428673: kvm_exit: reason npf rip 0xd02024f7
> 47965.428673: kvm_page_fault: address fee000a0 error_code 4
> 47965.428674: kvm_emulate_insn: 0:d02024f7: a1 a0 00 99 d0 (prot32)
> 47965.428674: kvm_apic: apic_read APIC_PROCPRI = 0x50
> 47965.428674: kvm_mmio: mmio read len 4 gpa 0xfee000a0 val 0x50
> 47965.428675: kvm_entry: vcpu 0
> 47965.428676: kvm_exit: reason npf rip 0xd0202506
> 47965.428676: kvm_page_fault: address fee00080 error_code 6
> 47965.428677: kvm_emulate_insn: 0:d0202506: 89 1d 80 00 99 d0 (prot32)
> 47965.428677: kvm_mmio: mmio write len 4 gpa 0xfee00080 val 0x50
> 47965.428677: kvm_apic: apic_write APIC_TASKPRI = 0x50
> 47965.428678: kvm_entry: vcpu 0
> 47965.428679: kvm_exit: reason npf rip 0xd0202534
> 47965.428680: kvm_page_fault: address bffc8 error_code 6
> 47965.428680: kvm_emulate_insn: 0:d0202534: 50 (prot32)
> 47965.428680: kvm_mmio: mmio write len 4 gpa 0xbffc8 val 0xd0ec7b00
> 47965.428681: kvm_entry: vcpu 0
> 47965.428682: kvm_exit: reason npf rip 0xd0202535
> 47965.428682: kvm_page_fault: address bffc4 error_code 6
> 47965.428683: kvm_emulate_insn: 0:d0202535: ff 53 00 (prot32)
> 47965.428683: kvm_mmio: mmio write len 4 gpa 0xbffc4 val 0xd0202538
> 47965.428683: kvm_entry: vcpu 0
> 47965.428684: kvm_exit: reason npf rip 0xd06e53d0
> 47965.428685: kvm_page_fault: address bffc0 error_code 6
> 47965.428685: kvm_emulate_insn: 0:d06e53d0: 55 (prot32)
> 47965.428685: kvm_mmio: mmio write len 4 gpa 0xbffc0 val 0xd438cfc8
> 47965.428686: kvm_entry: vcpu 0
> 47965.428687: kvm_exit: reason npf rip 0xd06e53d6
> 47965.428687: kvm_page_fault: address bffb8 error_code 6
> 47965.428687: kvm_emulate_insn: 0:d06e53d6: 89 75 f8 (prot32)
> 47965.428688: kvm_mmio: mmio write len 4 gpa 0xbffb8 val 0xd0201fc6
> 47965.428688: kvm_entry: vcpu 0
> 47965.428689: kvm_exit: reason npf rip 0xd06e53d9
> 47965.428689: kvm_page_fault: address bffc8 error_code 4
> 47965.428690: kvm_emulate_insn: 0:d06e53d9: 8b 75 08 (prot32)
> 47965.428690: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffc8 val 0x0
> 47965.428692: kvm_mmio: mmio read len 4 gpa 0xbffc8 val 0xd0ec7b00
> 47965.428692: kvm_entry: vcpu 0
> 47965.428693: kvm_exit: reason npf rip 0xd06e53dc
> 47965.428693: kvm_page_fault: address bffb4 error_code 6
> 47965.428694: kvm_emulate_insn: 0:d06e53dc: 89 5d f4 (prot32)
> 47965.428694: kvm_mmio: mmio write len 4 gpa 0xbffb4 val 0xd0eea840
> 47965.428695: kvm_entry: vcpu 0
> 47965.428696: kvm_exit: reason npf rip 0xd06e53df
> 47965.428696: kvm_page_fault: address bffbc error_code 6
> 47965.428696: kvm_emulate_insn: 0:d06e53df: 89 7d fc (prot32)
> 47965.428697: kvm_mmio: mmio write len 4 gpa 0xbffbc val 0xd0ac1ad4
> 47965.428697: kvm_entry: vcpu 0
> 47965.428698: kvm_exit: reason npf rip 0xd06e53e2
> 47965.428698: kvm_page_fault: address bffa0 error_code 6
> 47965.428699: kvm_emulate_insn: 0:d06e53e2: c7 44 24 08 00 00 00 00 (prot32)
> 47965.428699: kvm_mmio: mmio write len 4 gpa 0xbffa0 val 0x0
> 47965.428699: kvm_entry: vcpu 0
> 47965.428700: kvm_exit: reason npf rip 0xd06e53ed
> 47965.428700: kvm_page_fault: address bff9c error_code 6
> 47965.428701: kvm_emulate_insn: 0:d06e53ed: 89 44 24 04 (prot32)
> 47965.428701: kvm_mmio: mmio write len 4 gpa 0xbff9c val 0xb100
> 47965.428701: kvm_entry: vcpu 0
> 47965.428703: kvm_exit: reason npf rip 0xd06e53f4
> 47965.428703: kvm_page_fault: address bff98 error_code 6
> 47965.428703: kvm_emulate_insn: 0:d06e53f4: 89 04 24 (prot32)
> 47965.428704: kvm_mmio: mmio write len 4 gpa 0xbff98 val 0x0
> 47965.428704: kvm_entry: vcpu 0
> 47965.428705: kvm_exit: reason npf rip 0xd06e53f7
> 47965.428705: kvm_page_fault: address bff94 error_code 6
> 47965.428706: kvm_emulate_insn: 0:d06e53f7: e8 94 98 e7 ff (prot32)
> 47965.428706: kvm_mmio: mmio write len 4 gpa 0xbff94 val 0xd06e53fc
> 47965.428706: kvm_entry: vcpu 0
> 47965.428707: kvm_exit: reason npf rip 0xd055ec90
> 47965.428707: kvm_page_fault: address bff90 error_code 6
> 47965.428708: kvm_emulate_insn: 0:d055ec90: 55 (prot32)
> 47965.428708: kvm_mmio: mmio write len 4 gpa 0xbff90 val 0xd438cfc0
> 47965.428709: kvm_entry: vcpu 0
> 47965.428710: kvm_exit: reason npf rip 0xd055ec93
> 47965.428710: kvm_page_fault: address bff98 error_code 4
> 47965.428710: kvm_emulate_insn: 0:d055ec93: 8b 45 08 (prot32)
> 47965.428711: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbff98 val 0x0
> 47965.428712: kvm_mmio: mmio read len 4 gpa 0xbff98 val 0x0
> 47965.428713: kvm_entry: vcpu 0
> 47965.428714: kvm_exit: reason npf rip 0xd055eca8
> 47965.428714: kvm_page_fault: address bffa0 error_code 4
> 47965.428715: kvm_emulate_insn: 0:d055eca8: 8b 55 10 (prot32)
> 47965.428715: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffa0 val 0x0
> 47965.428716: kvm_mmio: mmio read len 4 gpa 0xbffa0 val 0x0
> 47965.428717: kvm_entry: vcpu 0
> 47965.428718: kvm_exit: reason npf rip 0xd055ecab
> 47965.428718: kvm_page_fault: address bff9c error_code 4
> 47965.428718: kvm_emulate_insn: 0:d055ecab: 03 55 0c (prot32)
> 47965.428719: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbff9c val 0x0
> 47965.428720: kvm_mmio: mmio read len 4 gpa 0xbff9c val 0xb100
> 47965.428721: kvm_entry: vcpu 0
> 47965.428721: kvm_exit: reason io rip 0xd055ecae
> 47965.428722: kvm_emulate_insn: 0:d055ecae: ec (prot32)
> 47965.428722: kvm_pio: pio_read at 0xb100 size 1 count 1
> 47965.428723: kvm_entry: vcpu 0
> 47965.428724: kvm_exit: reason npf rip 0xd055ecaf
> 47965.428725: kvm_page_fault: address bff90 error_code 4
> 47965.428725: kvm_emulate_insn: 0:d055ecaf: 5d (prot32)
> 47965.428726: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbff90 val 0x0
> 47965.428727: kvm_mmio: mmio read len 4 gpa 0xbff90 val 0xd438cfc0
> 47965.428727: kvm_entry: vcpu 0
> 47965.428728: kvm_exit: reason npf rip 0xd055ecb3
> 47965.428728: kvm_page_fault: address bff94 error_code 4
> 47965.428729: kvm_emulate_insn: 0:d055ecb3: c3 (prot32)
> 47965.428729: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbff94 val 0x0
> 47965.428730: kvm_mmio: mmio read len 4 gpa 0xbff94 val 0xd06e53fc
> 47965.428731: kvm_entry: vcpu 0
> 47965.428732: kvm_exit: reason npf rip 0xd06e540b
> 47965.428732: kvm_page_fault: address bffb4 error_code 4
> 47965.428732: kvm_emulate_insn: 0:d06e540b: 8b 5d f4 (prot32)
> 47965.428733: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffb4 val 0x0
> 47965.428734: kvm_mmio: mmio read len 4 gpa 0xbffb4 val 0xd0eea840
> 47965.428734: kvm_entry: vcpu 0
> 47965.428735: kvm_exit: reason npf rip 0xd06e540e
> 47965.428735: kvm_page_fault: address bffb8 error_code 4
> 47965.428736: kvm_emulate_insn: 0:d06e540e: 8b 75 f8 (prot32)
> 47965.428736: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffb8 val 0x0
> 47965.428737: kvm_mmio: mmio read len 4 gpa 0xbffb8 val 0xd0201fc6
> 47965.428738: kvm_entry: vcpu 0
> 47965.428739: kvm_exit: reason npf rip 0xd06e5411
> 47965.428739: kvm_page_fault: address bffbc error_code 4
> 47965.428740: kvm_emulate_insn: 0:d06e5411: 8b 7d fc (prot32)
> 47965.428740: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffbc val 0x0
> 47965.428741: kvm_mmio: mmio read len 4 gpa 0xbffbc val 0xd0ac1ad4
> 47965.428741: kvm_entry: vcpu 0
> 47965.428742: kvm_exit: reason npf rip 0xd06e5416
> 47965.428743: kvm_page_fault: address bffc0 error_code 4
> 47965.428743: kvm_emulate_insn: 0:d06e5416: 5d (prot32)
> 47965.428743: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffc0 val 0x0
> 47965.428745: kvm_mmio: mmio read len 4 gpa 0xbffc0 val 0xd438cfc8
> 47965.428745: kvm_entry: vcpu 0
> 47965.428746: kvm_exit: reason npf rip 0xd06e5417
> 47965.428746: kvm_page_fault: address bffc4 error_code 4
> 47965.428747: kvm_emulate_insn: 0:d06e5417: c3 (prot32)
> 47965.428747: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffc4 val 0x0
> 47965.428748: kvm_mmio: mmio read len 4 gpa 0xbffc4 val 0xd0202538
> 47965.428748: kvm_entry: vcpu 0
> 47965.428749: kvm_exit: reason npf rip 0xd0202554
> 47965.428750: kvm_page_fault: address fee000b0 error_code 6
> 47965.428750: kvm_emulate_insn: 0:d0202554: c7 05 b0 00 99 d0 00 00 00 00 (prot32)
> 47965.428751: kvm_mmio: mmio write len 4 gpa 0xfee000b0 val 0x0
> 47965.428751: kvm_apic: apic_write APIC_EOI = 0x0
> 47965.428751: kvm_ack_irq: irqchip IOAPIC pin 9
> 47965.428751: kvm_apic_accept_irq: apicid 0 vec 81 (Fixed|level)
> 47965.428752: kvm_entry: vcpu 0
> 47965.428753: kvm_exit: reason npf rip 0xd0201fc0
> 47965.428753: kvm_page_fault: address bffcc error_code 4
> 47965.428753: kvm_emulate_insn: 0:d0201fc0: 5b (prot32)
> 47965.428754: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffcc val 0x0
> 47965.428755: kvm_mmio: mmio read len 4 gpa 0xbffcc val 0x30
> 47965.428755: kvm_entry: vcpu 0
> 47965.428756: kvm_exit: reason npf rip 0xd0202002
> 47965.428756: kvm_page_fault: address fee00080 error_code 6
> 47965.428757: kvm_emulate_insn: 0:d0202002: 89 1d 80 00 99 d0 (prot32)
> 47965.428757: kvm_mmio: mmio write len 4 gpa 0xfee00080 val 0x30
> 47965.428757: kvm_apic: apic_write APIC_TASKPRI = 0x30
> 47965.428759: kvm_entry: vcpu 0
> 47965.428760: kvm_exit: reason npf rip 0xd0202030
> 47965.428760: kvm_page_fault: address bffd0 error_code 4
> 47965.428760: kvm_emulate_insn: 0:d0202030: 0f a1 (prot32)
> 47965.428761: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffd0 val 0x0
> 47965.428762: kvm_mmio: mmio read len 4 gpa 0xbffd0 val 0x58
> 47965.428763: kvm_entry: vcpu 0
> 47965.428764: kvm_exit: reason npf rip 0xd0202032
> 47965.428764: kvm_page_fault: address bffd4 error_code 4
> 47965.428765: kvm_emulate_insn: 0:d0202032: 0f a9 (prot32)
> 47965.428765: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffd4 val 0x0
> 47965.428766: kvm_mmio: mmio read len 4 gpa 0xbffd4 val 0x10
> 47965.428767: kvm_entry: vcpu 0
> 47965.428768: kvm_exit: reason npf rip 0xd0202034
> 47965.428768: kvm_page_fault: address bffd8 error_code 4
> 47965.428769: kvm_emulate_insn: 0:d0202034: 07 (prot32)
> 47965.428769: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffd8 val 0x0
> 47965.428770: kvm_mmio: mmio read len 4 gpa 0xbffd8 val 0x10
> 47965.428771: kvm_entry: vcpu 0
> 47965.428772: kvm_exit: reason npf rip 0xd0202035
> 47965.428772: kvm_page_fault: address bffdc error_code 4
> 47965.428773: kvm_emulate_insn: 0:d0202035: 1f (prot32)
> 47965.428773: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffdc val 0x0
> 47965.428774: kvm_mmio: mmio read len 4 gpa 0xbffdc val 0x10
> 47965.428775: kvm_entry: vcpu 0
> 47965.428776: kvm_exit: reason npf rip 0xd0202036
> 47965.428776: kvm_page_fault: address bffe0 error_code 4
> 47965.428777: kvm_emulate_insn: 0:d0202036: 5f (prot32)
> 47965.428777: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffe0 val 0x0
> 47965.428778: kvm_mmio: mmio read len 4 gpa 0xbffe0 val 0xd0ac1ad4
> 47965.428779: kvm_entry: vcpu 0
> 47965.428780: kvm_exit: reason npf rip 0xd0202037
> 47965.428780: kvm_page_fault: address bffe4 error_code 4
> 47965.428780: kvm_emulate_insn: 0:d0202037: 5e (prot32)
> 47965.428781: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffe4 val 0x0
> 47965.428782: kvm_mmio: mmio read len 4 gpa 0xbffe4 val 0xd0201fc6
> 47965.428782: kvm_entry: vcpu 0
> 47965.428783: kvm_exit: reason npf rip 0xd0202038
> 47965.428783: kvm_page_fault: address bffe8 error_code 4
> 47965.428784: kvm_emulate_insn: 0:d0202038: 5d (prot32)
> 47965.428784: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffe8 val 0x0
> 47965.428786: kvm_mmio: mmio read len 4 gpa 0xbffe8 val 0xd4492e1c
> 47965.428786: kvm_entry: vcpu 0
> 47965.428787: kvm_exit: reason npf rip 0xd0202039
> 47965.428788: kvm_page_fault: address bffec error_code 4
> 47965.428788: kvm_emulate_insn: 0:d0202039: 5b (prot32)
> 47965.428789: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbffec val 0x0
> 47965.428790: kvm_mmio: mmio read len 4 gpa 0xbffec val 0x0
> 47965.428790: kvm_entry: vcpu 0
> 47965.428791: kvm_exit: reason npf rip 0xd020203a
> 47965.428791: kvm_page_fault: address bfff0 error_code 4
> 47965.428792: kvm_emulate_insn: 0:d020203a: 5a (prot32)
> 47965.428792: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff0 val 0x0
> 47965.428793: kvm_mmio: mmio read len 4 gpa 0xbfff0 val 0xb100
> 47965.428794: kvm_entry: vcpu 0
> 47965.428795: kvm_exit: reason npf rip 0xd020203b
> 47965.428795: kvm_page_fault: address bfff4 error_code 4
> 47965.428795: kvm_emulate_insn: 0:d020203b: 59 (prot32)
> 47965.428796: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff4 val 0x0
> 47965.428797: kvm_mmio: mmio read len 4 gpa 0xbfff4 val 0x0
> 47965.428797: kvm_entry: vcpu 0
> 47965.428798: kvm_exit: reason npf rip 0xd020203c
> 47965.428798: kvm_page_fault: address bfff8 error_code 4
> 47965.428799: kvm_emulate_insn: 0:d020203c: 58 (prot32)

That's a POP instruction.  So openbsd mapped the stack into the 
framebuffer, and kvm has to emulate everything.

Please post a complete binary trace from bootup until the 
host_state_reload issue appears.

> 47965.428799: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff8 val 0x0
> 47965.428801: kvm_mmio: mmio read len 4 gpa 0xbfff8 val 0x30
> 47965.428801: kvm_entry: vcpu 0
> 47965.428802: kvm_exit: reason vintr rip 0xd0202041
> 47965.428802: kvm_inj_virq: irq 81
> 47965.428802: kvm_inj_virq: irq 81
> 47965.428803: kvm_entry: vcpu 0
> 47965.428803: kvm_exit: reason npf rip 0xd0202041
> 47965.428804: kvm_page_fault: address bfffc error_code 6
> 47965.428804: kvm_emulate_insn: 0:d0202041: cf (prot32)
> 47965.428805: kvm_emulate_insn: 0:d0202041: cf (prot32) failed

We don't emulate IRET-with-mmio-stack.


-- 
error compiling committee.c: too many arguments to function

Re: openbsd system_powerdown: "KVM internal error. Suberror: 1"

[Gleb Natapov]

On Mon, Mar 21, 2011 at 11:43:32AM +0200, Avi Kivity wrote:
> >47965.428797: kvm_mmio: mmio read len 4 gpa 0xbfff4 val 0x0
> >47965.428797: kvm_entry: vcpu 0
> >47965.428798: kvm_exit: reason npf rip 0xd020203c
> >47965.428798: kvm_page_fault: address bfff8 error_code 4
> >47965.428799: kvm_emulate_insn: 0:d020203c: 58 (prot32)
> 
> That's a POP instruction.  So openbsd mapped the stack into the
> framebuffer, and kvm has to emulate everything.
> 
IIRC openbsd had always have this problem with powerdown. Last time
I looked at it I found that when openbsd receives ACPI interrupt it
enters some kind of interrupt injection loop where with each received
interrupt stack grows a little bit. When stack starts to overlap with
frame buffer emulation error happens. May be something wrong with our MP
tables, but I couldn't figure what.

> Please post a complete binary trace from bootup until the
> host_state_reload issue appears.
> 
> >47965.428799: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff8 val 0x0
> >47965.428801: kvm_mmio: mmio read len 4 gpa 0xbfff8 val 0x30
> >47965.428801: kvm_entry: vcpu 0
> >47965.428802: kvm_exit: reason vintr rip 0xd0202041
> >47965.428802: kvm_inj_virq: irq 81
> >47965.428802: kvm_inj_virq: irq 81
> >47965.428803: kvm_entry: vcpu 0
> >47965.428803: kvm_exit: reason npf rip 0xd0202041
> >47965.428804: kvm_page_fault: address bfffc error_code 6
> >47965.428804: kvm_emulate_insn: 0:d0202041: cf (prot32)
> >47965.428805: kvm_emulate_insn: 0:d0202041: cf (prot32) failed
> 
> We don't emulate IRET-with-mmio-stack.
> 

--
			Gleb.

Re: openbsd system_powerdown: "KVM internal error. Suberror: 1"

[Michael Tokarev]

21.03.2011 12:43, Avi Kivity wrote:
> On 03/17/2011 10:18 PM, Michael Tokarev wrote:

[]
>> 47965.428791: kvm_exit: reason npf rip 0xd020203a
>> 47965.428791: kvm_page_fault: address bfff0 error_code 4
>> 47965.428792: kvm_emulate_insn: 0:d020203a: 5a (prot32)
>> 47965.428792: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff0 val 0x0
>> 47965.428793: kvm_mmio: mmio read len 4 gpa 0xbfff0 val 0xb100
>> 47965.428794: kvm_entry: vcpu 0
>> 47965.428795: kvm_exit: reason npf rip 0xd020203b
>> 47965.428795: kvm_page_fault: address bfff4 error_code 4
>> 47965.428795: kvm_emulate_insn: 0:d020203b: 59 (prot32)
>> 47965.428796: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff4 val 0x0
>> 47965.428797: kvm_mmio: mmio read len 4 gpa 0xbfff4 val 0x0
>> 47965.428797: kvm_entry: vcpu 0
>> 47965.428798: kvm_exit: reason npf rip 0xd020203c
>> 47965.428798: kvm_page_fault: address bfff8 error_code 4
>> 47965.428799: kvm_emulate_insn: 0:d020203c: 58 (prot32)
> 
> That's a POP instruction.  So openbsd mapped the stack into the
> framebuffer, and kvm has to emulate everything.
> 
> Please post a complete binary trace from bootup until the
> host_state_reload issue appears.

http://95.84.243.119:8000/tmp/kvm-obsd/ -- that's the whole
thing.

There, trace.dat.gz and trace.txt.gz are the complete traces
from trace-cmd from the beginning to the login prompt.

I don't think it's easy to catch the place when host_state_reloads
starts increasing - it happens during boot before userspace takes
control, while in kernel (during this time the text on the screen -
bootup progress - in on a strange background color). The difficulty
is because during that time there are lots of other activity on
kvm side - number of exits and emulations for example.

Also, obsd4.8-32bit.qcow2.xz is the disk image of openbsd install
which I used for all these tests - it's 112 Mb compressed, about
600Mb uncompressed, 2Gb virtual size.  This is here in order for
me to stop acting as a broken phone (but I can continue doing so
just fine - I just think it's a bit less productive this way :)

I've shown this file to Gleb Natapov (Cc'd) before too (who tried
to debug the "insane amount of host_state_reload" issue. This is
a default openbsd install from their current installation cdrom,
so anyone can create their own disk image too, obviously.

I run it just like "kvm -hda obsd4.8-32bit.qcow2 -snapshot -net none"
(and it can use rtl8139 NIC).  Root password is "12", but there's no
need to login since all the problems happens before login.

In order to trigger the error in $subject, wait till it's idle
(which happens right after "login:" prompt) and send
"system_powerdown" command (I use -monitor stdio) - in about
5 seconds from there it'll error out.  In order to catch this
error it's better to use kvm 0.12 (it works with current seabios
under freebsd since graphics mode isn't used) -- current 0.14
behaves badly after "KVM internal error" (which needs to be
improved a bit too, I think)

>> 47965.428799: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff8 val 0x0
>> 47965.428801: kvm_mmio: mmio read len 4 gpa 0xbfff8 val 0x30
>> 47965.428801: kvm_entry: vcpu 0
>> 47965.428802: kvm_exit: reason vintr rip 0xd0202041
>> 47965.428802: kvm_inj_virq: irq 81
>> 47965.428802: kvm_inj_virq: irq 81
>> 47965.428803: kvm_entry: vcpu 0
>> 47965.428803: kvm_exit: reason npf rip 0xd0202041
>> 47965.428804: kvm_page_fault: address bfffc error_code 6
>> 47965.428804: kvm_emulate_insn: 0:d0202041: cf (prot32)
>> 47965.428805: kvm_emulate_insn: 0:d0202041: cf (prot32) failed
> 
> We don't emulate IRET-with-mmio-stack.

Note that the whole this story - two issues with OpenBSD - is
pure my "luck" - I don't use openbsd, never used it before, and
don't actually plan to use in a near future.  We debugged an
unrelated problem (a bug in linux nfs server) and tried to
perform various interoperability tests (installing various
operating systems in kvm), and found out that OpenBSD behaves
somewhat.. unexpectedly in kvm.  So I went on and performed
a few tests locally (installing OpenBSD for the first time
ever), which resulted in 2 my "bugreports".

I'm not sure how important OpenBSD support for kvm is, and if
it's something which better be done in OpenBSD itself instead
of kvm.

(This all is not to say I wont help resolving these issues -
quite the opposite, I'm willing to help, but I think my help
in a form of broken phone isn't of much value :)

Thanks!

/mjt

Re: openbsd system_powerdown: "KVM internal error. Suberror: 1"

[Avi Kivity]

On 03/21/2011 12:12 PM, Michael Tokarev wrote:
> 21.03.2011 12:43, Avi Kivity wrote:
> >  On 03/17/2011 10:18 PM, Michael Tokarev wrote:
>
> []
> >>  47965.428791: kvm_exit: reason npf rip 0xd020203a
> >>  47965.428791: kvm_page_fault: address bfff0 error_code 4
> >>  47965.428792: kvm_emulate_insn: 0:d020203a: 5a (prot32)
> >>  47965.428792: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff0 val 0x0
> >>  47965.428793: kvm_mmio: mmio read len 4 gpa 0xbfff0 val 0xb100
> >>  47965.428794: kvm_entry: vcpu 0
> >>  47965.428795: kvm_exit: reason npf rip 0xd020203b
> >>  47965.428795: kvm_page_fault: address bfff4 error_code 4
> >>  47965.428795: kvm_emulate_insn: 0:d020203b: 59 (prot32)
> >>  47965.428796: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff4 val 0x0
> >>  47965.428797: kvm_mmio: mmio read len 4 gpa 0xbfff4 val 0x0
> >>  47965.428797: kvm_entry: vcpu 0
> >>  47965.428798: kvm_exit: reason npf rip 0xd020203c
> >>  47965.428798: kvm_page_fault: address bfff8 error_code 4
> >>  47965.428799: kvm_emulate_insn: 0:d020203c: 58 (prot32)
> >
> >  That's a POP instruction.  So openbsd mapped the stack into the
> >  framebuffer, and kvm has to emulate everything.
> >
> >  Please post a complete binary trace from bootup until the
> >  host_state_reload issue appears.
>
> http://95.84.243.119:8000/tmp/kvm-obsd/ -- that's the whole
> thing.
>
> There, trace.dat.gz and trace.txt.gz are the complete traces
> from trace-cmd from the beginning to the login prompt.
>
> I don't think it's easy to catch the place when host_state_reloads
> starts increasing - it happens during boot before userspace takes
> control, while in kernel (during this time the text on the screen -
> bootup progress - in on a strange background color). The difficulty
> is because during that time there are lots of other activity on
> kvm side - number of exits and emulations for example.
>
> Also, obsd4.8-32bit.qcow2.xz is the disk image of openbsd install
> which I used for all these tests - it's 112 Mb compressed, about
> 600Mb uncompressed, 2Gb virtual size.  This is here in order for
> me to stop acting as a broken phone (but I can continue doing so
> just fine - I just think it's a bit less productive this way :)
>
> I've shown this file to Gleb Natapov (Cc'd) before too (who tried
> to debug the "insane amount of host_state_reload" issue. This is
> a default openbsd install from their current installation cdrom,
> so anyone can create their own disk image too, obviously.
>
> I run it just like "kvm -hda obsd4.8-32bit.qcow2 -snapshot -net none"
> (and it can use rtl8139 NIC).  Root password is "12", but there's no
> need to login since all the problems happens before login.
>
> In order to trigger the error in $subject, wait till it's idle
> (which happens right after "login:" prompt) and send
> "system_powerdown" command (I use -monitor stdio) - in about
> 5 seconds from there it'll error out.  In order to catch this
> error it's better to use kvm 0.12 (it works with current seabios
> under freebsd since graphics mode isn't used) -- current 0.14
> behaves badly after "KVM internal error" (which needs to be
> improved a bit too, I think)
>
> >>  47965.428799: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff8 val 0x0
> >>  47965.428801: kvm_mmio: mmio read len 4 gpa 0xbfff8 val 0x30
> >>  47965.428801: kvm_entry: vcpu 0
> >>  47965.428802: kvm_exit: reason vintr rip 0xd0202041
> >>  47965.428802: kvm_inj_virq: irq 81
> >>  47965.428802: kvm_inj_virq: irq 81
> >>  47965.428803: kvm_entry: vcpu 0
> >>  47965.428803: kvm_exit: reason npf rip 0xd0202041
> >>  47965.428804: kvm_page_fault: address bfffc error_code 6
> >>  47965.428804: kvm_emulate_insn: 0:d0202041: cf (prot32)
> >>  47965.428805: kvm_emulate_insn: 0:d0202041: cf (prot32) failed
> >
> >  We don't emulate IRET-with-mmio-stack.
>
> Note that the whole this story - two issues with OpenBSD - is
> pure my "luck" - I don't use openbsd, never used it before, and
> don't actually plan to use in a near future.  We debugged an
> unrelated problem (a bug in linux nfs server) and tried to
> perform various interoperability tests (installing various
> operating systems in kvm), and found out that OpenBSD behaves
> somewhat.. unexpectedly in kvm.  So I went on and performed
> a few tests locally (installing OpenBSD for the first time
> ever), which resulted in 2 my "bugreports".
>
> I'm not sure how important OpenBSD support for kvm is, and if
> it's something which better be done in OpenBSD itself instead
> of kvm.

There's no such thing as OpenBSD support.  We emulate a PC, and OpenBSD 
runs on a PC.  If it doesn't work well, there's a bug in one or the other.

It's true that the bug has relatively low priority if it's just OpenBSD 
that triggers it.

> (This all is not to say I wont help resolving these issues -
> quite the opposite, I'm willing to help, but I think my help
> in a form of broken phone isn't of much value :)

Yes, it's better if we can reproduce this, and I understand from Gleb's 
message that we can.

-- 
error compiling committee.c: too many arguments to function

Re: openbsd system_powerdown: "KVM internal error. Suberror: 1"

[Gleb Natapov]

On Mon, Mar 21, 2011 at 12:28:56PM +0200, Avi Kivity wrote:
> >(This all is not to say I wont help resolving these issues -
> >quite the opposite, I'm willing to help, but I think my help
> >in a form of broken phone isn't of much value :)
> 
> Yes, it's better if we can reproduce this, and I understand from
> Gleb's message that we can.
> 
https://bugzilla.redhat.com/show_bug.cgi?id=508801#c34

--
			Gleb.

Re: openbsd system_powerdown: "KVM internal error. Suberror: 1"

[Avi Kivity]

On 03/21/2011 12:41 PM, Gleb Natapov wrote:
> On Mon, Mar 21, 2011 at 12:28:56PM +0200, Avi Kivity wrote:
> >  >(This all is not to say I wont help resolving these issues -
> >  >quite the opposite, I'm willing to help, but I think my help
> >  >in a form of broken phone isn't of much value :)
> >
> >  Yes, it's better if we can reproduce this, and I understand from
> >  Gleb's message that we can.
> >
> https://bugzilla.redhat.com/show_bug.cgi?id=508801#c34
>

Well, that says it's fixed, no?

-- 
error compiling committee.c: too many arguments to function

Re: openbsd system_powerdown: "KVM internal error. Suberror: 1"

[Gleb Natapov]

On Mon, Mar 21, 2011 at 12:47:39PM +0200, Avi Kivity wrote:
> On 03/21/2011 12:41 PM, Gleb Natapov wrote:
> >On Mon, Mar 21, 2011 at 12:28:56PM +0200, Avi Kivity wrote:
> >>  >(This all is not to say I wont help resolving these issues -
> >>  >quite the opposite, I'm willing to help, but I think my help
> >>  >in a form of broken phone isn't of much value :)
> >>
> >>  Yes, it's better if we can reproduce this, and I understand from
> >>  Gleb's message that we can.
> >>
> >https://bugzilla.redhat.com/show_bug.cgi?id=508801#c34
> >
> 
> Well, that says it's fixed, no?
> 
No. It says it is fixed for all but SCI interrupt. See comment 32 which the link
above points to.

--
			Gleb.