kvm.git next: KVM internal error. Suberror: 1

DISCUSSION Jan Kiszka 3 participants 7 messages Feb 8, 2010 KVM

Share & tools

Jan Kiszka

author

2010-02-08 12:05 UTC #0 lore raw

Avi,

with 2c8232f over kvm-kmod and "qemu-system-x86_64 -m 256 vm-image.qcow2 -snapshot -serial stdio -s -smp 2" I just got this:

KVM internal error. Suberror: 1
rax 0000000000000000 rbx 0000000000006f08 rcx 0000000000000000 rdx 0000000000000052 rsi 0000000000000000 rdi 00000000000f4fd4 rsp 0000000000006ed8 rbp 00000000000f7280 r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000 r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000 rip 00000000f000ff53 rflags 00010016
cs 0008 (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 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
gs 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
tr 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) gdt f7a20/37
idt f8aa0/0
cr0 11 cr2 0 cr3 0 cr4 0 cr8 0 efer 0
emulation failure

Before that run, I started the very same VM and shut it down via system_powerdown. This is reproducible!

Maybe it's the same issue that causes the #UD regression with -no-kvm-irqchip.

Jan

Signature · 2 lines

Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

Avi Kivity

2010-02-08 12:11 UTC #1 lore raw

Quoted 5 lines · Jan Kiszka

Avi,
with 2c8232f over kvm-kmod and "qemu-system-x86_64 -m 256 vm-image.qcow2 -snapshot -serial stdio -s -smp 2" I just got this:

What is vm-image.qcow2?

Quoted 7 lines

KVM internal error. Suberror: 1
rax 0000000000000000 rbx 0000000000006f08 rcx 0000000000000000 rdx 0000000000000052 rsi 0000000000000000 rdi 00000000000f4fd4 rsp 0000000000006ed8 rbp 00000000000f7280 r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000 r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000 rip 00000000f000ff53 rflags 00010016

ffffff53 is an 'iret'. But f000ff53 doesn't make sense.

Quoted 13 lines

cs 0008 (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 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) gs 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) tr 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) gdt f7a20/37
idt f8aa0/0
cr0 11 cr2 0 cr3 0 cr4 0 cr8 0 efer 0
emulation failure

Quoted 3 lines

Before that run, I started the very same VM and shut it down via system_powerdown. This is reproducible!

Not sure I understand. This is with -snapshot, so how can a previous run have any effect?

Quoted 2 lines

Maybe it's the same issue that causes the #UD regression with -no-kvm-irqchip.

I wasn't able to reproduce.

Signature · 1 line

error compiling committee.c: too many arguments to function

Jan Kiszka

author

2010-02-08 12:45 UTC #2 lore raw

Quoted 36 lines · Avi Kivity

Quoted 5 lines · Jan Kiszka
Avi,
with 2c8232f over kvm-kmod and "qemu-system-x86_64 -m 256 vm-image.qcow2 -snapshot -serial stdio -s -smp 2" I just got this:
What is vm-image.qcow2?
Quoted 7 lines
KVM internal error. Suberror: 1
rax 0000000000000000 rbx 0000000000006f08 rcx 0000000000000000 rdx 0000000000000052 rsi 0000000000000000 rdi 00000000000f4fd4 rsp 0000000000006ed8 rbp 00000000000f7280 r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000 r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000 rip 00000000f000ff53 rflags 00010016
ffffff53 is an 'iret'. But f000ff53 doesn't make sense.
Quoted 13 lines
cs 0008 (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 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) gs 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) tr 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) gdt f7a20/37
idt f8aa0/0
cr0 11 cr2 0 cr3 0 cr4 0 cr8 0 efer 0
emulation failure
Quoted 3 lines
Before that run, I started the very same VM and shut it down via system_powerdown. This is reproducible!

Quoted 8 lines

Not sure I understand. This is with -snapshot, so how can a previous run have any effect?
Quoted 2 lines
Maybe it's the same issue that causes the #UD regression with -no-kvm-irqchip.
I wasn't able to reproduce.

Looks like tried to outsource my own bugs: I was on queues/vcpu-state, ie. my state writeback rework, and I'm unable to reproduce over qemu-kvm master. Will do my homework.

Still, the issue around -no-kvm-irqchip exists with master.

Jan

Signature · 2 lines

Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

Gleb Natapov

2010-02-08 12:55 UTC #3 lore raw

Quoted 43 lines · Jan Kiszka

Quoted 42 lines · Avi Kivity
Quoted 5 lines · Jan Kiszka
Avi,
with 2c8232f over kvm-kmod and "qemu-system-x86_64 -m 256 vm-image.qcow2 -snapshot -serial stdio -s -smp 2" I just got this:
What is vm-image.qcow2?
Quoted 7 lines
KVM internal error. Suberror: 1
rax 0000000000000000 rbx 0000000000006f08 rcx 0000000000000000 rdx 0000000000000052 rsi 0000000000000000 rdi 00000000000f4fd4 rsp 0000000000006ed8 rbp 00000000000f7280 r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000 r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000 rip 00000000f000ff53 rflags 00010016
ffffff53 is an 'iret'. But f000ff53 doesn't make sense.
Quoted 13 lines
cs 0008 (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 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) gs 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) tr 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) gdt f7a20/37
idt f8aa0/0
cr0 11 cr2 0 cr3 0 cr4 0 cr8 0 efer 0
emulation failure
Quoted 3 lines
Before that run, I started the very same VM and shut it down via system_powerdown. This is reproducible!
Not sure I understand. This is with -snapshot, so how can a previous run have any effect?
Quoted 2 lines
Maybe it's the same issue that causes the #UD regression with -no-kvm-irqchip.

Quoted 7 lines

Quoted 2 lines
I wasn't able to reproduce.
Looks like tried to outsource my own bugs: I was on queues/vcpu-state, ie. my state writeback rework, and I'm unable to reproduce over qemu-kvm master. Will do my homework.

Saw this behaviour in my testing. Sometimes during startup I get similar errors. Wasn't sure that this is not my fault, so didn't report.

--
Gleb.

Jan Kiszka

author

2010-02-08 12:59 UTC #4 lore raw

Quoted 40 lines · Gleb Natapov

Quoted 39 lines · Jan Kiszka
Quoted 38 lines · Avi Kivity
Quoted 5 lines · Jan Kiszka
Avi,
with 2c8232f over kvm-kmod and "qemu-system-x86_64 -m 256 vm-image.qcow2 -snapshot -serial stdio -s -smp 2" I just got this:
What is vm-image.qcow2?
Quoted 7 lines
KVM internal error. Suberror: 1
rax 0000000000000000 rbx 0000000000006f08 rcx 0000000000000000 rdx 0000000000000052 rsi 0000000000000000 rdi 00000000000f4fd4 rsp 0000000000006ed8 rbp 00000000000f7280 r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000 r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000 rip 00000000f000ff53 rflags 00010016
ffffff53 is an 'iret'. But f000ff53 doesn't make sense.
Quoted 13 lines
cs 0008 (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 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) gs 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) tr 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) gdt f7a20/37
idt f8aa0/0
cr0 11 cr2 0 cr3 0 cr4 0 cr8 0 efer 0
emulation failure
Quoted 3 lines
Before that run, I started the very same VM and shut it down via system_powerdown. This is reproducible!
Not sure I understand. This is with -snapshot, so how can a previous run have any effect?
Quoted 2 lines
Maybe it's the same issue that causes the #UD regression with -no-kvm-irqchip.

Quoted 8 lines

Quoted 6 lines
Quoted 2 lines
I wasn't able to reproduce.
Looks like tried to outsource my own bugs: I was on queues/vcpu-state, ie. my state writeback rework, and I'm unable to reproduce over qemu-kvm master. Will do my homework.
Saw this behaviour in my testing. Sometimes during startup I get similar errors. Wasn't sure that this is not my fault, so didn't report.

So far it looks like the final patch is yet too early, something of the initialization is still fragile.

Jan

Signature · 2 lines

Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

Avi Kivity

2010-02-08 13:48 UTC #5 lore raw

In reply to Jan Kiszka

Quoted 5 lines · Jan Kiszka

Looks like tried to outsource my own bugs: I was on queues/vcpu-state, ie. my state writeback rework, and I'm unable to reproduce over qemu-kvm master.

I do that all the time.

Quoted 2 lines

Still, the issue around -no-kvm-irqchip exists with master.

I see it now. I guess -no-kvm-irqchip triggers a lot of KVM_SET_SREGS, and that something is wrong there. Will look further.

Signature · 1 line

error compiling committee.c: too many arguments to function

Avi Kivity

2010-02-08 14:12 UTC #6 lore raw

Quoted 5 lines · Avi Kivity

Quoted 2 lines
Still, the issue around -no-kvm-irqchip exists with master.
I see it now. I guess -no-kvm-irqchip triggers a lot of KVM_SET_SREGS, and that something is wrong there. Will look further.

Fix in next, bug too embarrassing to detail.

Signature · 1 line

error compiling committee.c: too many arguments to function