Hi,

when migrating ancient machine to become KVM guest, I am facing a problem 
that KVM gives me the error below when being passed oldish vmlinuz image:

=== 
# qemu-kvm -kernel vmlinuz-2.4.33
KVM internal error. Suberror: 1
rax 0000000000000000 rbx 000000000000003e rcx 0000000000000000 rdx 
00000000c1485180
rsi 00000000c00b8000 rdi 00000000c1485180 rsp 00000000c0305f70 rbp 
0000000000000fa0
r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 
0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 
0000000000000000
rip 00000000c027a841 rflags 00000006
cs 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
ds 0018 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
es 0018 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
ss 0018 (00000000/bfffffff p 1 dpl 0 db 1 s 1 type 7 l 0 g 1 avl 0)
fs 0018 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
gs 0018 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
tr 0060 (c0301d80/000000eb p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
ldt 0068 (c0289020/00000027 p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0)
gdt c0288860/7f
idt c0288000/7ff
cr0 80050033 cr2 0 cr3 287000 cr4 90 cr8 0 efer 0
emulation failure, check dmesg for details
===

There is no message emitted in dmesg. 
The instructions around eip look reasonably valid from a quick look (this 
is monitor output from the time it crashes):

===
(qemu) x/5i $eip
0x00000000c027a841:  movq   (%esi),%mm0
0x00000000c027a844:  movq   0x8(%esi),%mm1
0x00000000c027a848:  movq   0x10(%esi),%mm2
0x00000000c027a84c:  movq   0x18(%esi),%mm3
0x00000000c027a850:  movq   %mm0,(%edx)
===

Is there any issue with emulating MMX?

This is with 0.12.3 KVM module on 2.6.32.

The kernel image which triggers this can be downloaded from

        http://www.jikos.cz/jikos/junk/vmlinuz-2.4.33

Thanks,

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to