KVM problems with Xeon L5530

KVM problems with Xeon L5530

[Matteo Ghezzi]

Hi!

I'm a long time KVM user, but I've encountered a problem that I couldn't solve.
I've switched my good old Core2 Quad with gentoo (2.6.27 kernel) for a
Dual Xeon L5530 with Arch (2.6.32 kernel).
I've tried starting the old vmachines on the new hardware but if I
enable kvm acceleration in qemu I got a black screen via vnc, and the
logs are filled with this message:

handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d

I've tried creating new virtual machines directly on the new hardware
but with the same result.
I've tried any combination of virtualization options in the bios,
tested any bios revision for my motherboard (Asus Z8DNA-D6), checked
the ram on another system... all in vain.

If I've to provide more info please let me know.
Thanks for your help.

Re: KVM problems with Xeon L5530

[Brian Jackson]

On Wednesday 27 January 2010 05:37:14 pm Matteo Ghezzi wrote:
> Hi!
> 
> I'm a long time KVM user, but I've encountered a problem that I couldn't
> solve. I've switched my good old Core2 Quad with gentoo (2.6.27 kernel)
> for a Dual Xeon L5530 with Arch (2.6.32 kernel).
> I've tried starting the old vmachines on the new hardware but if I
> enable kvm acceleration in qemu I got a black screen via vnc, and the
> logs are filled with this message:

What version of qemu-kvm?

There was a similar thread a while back, maybe you could try some of the 
suggestions and/or info gathering tips from it.

http://www.mail-archive.com/kvm@vger.kernel.org/msg24304.html

> 
> handle_exception: unexpected, vectoring info 0x8000000d intr info
> 0x80000b0d
> 
> I've tried creating new virtual machines directly on the new hardware
> but with the same result.
> I've tried any combination of virtualization options in the bios,
> tested any bios revision for my motherboard (Asus Z8DNA-D6), checked
> the ram on another system... all in vain.
> 
> If I've to provide more info please let me know.
> Thanks for your help.
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: KVM problems with Xeon L5530

[Matteo Ghezzi]

2010/1/28 Brian Jackson <iggy@theiggy.com>:
> What version of qemu-kvm?

qemu-kvm 0.12.2-1

> There was a similar thread a while back, maybe you could try some of the
> suggestions and/or info gathering tips from it.

tried every suggestion form that thread... contacted the original
poster and narrowed down the problem:
we both have an Intel engineering sample and not a finalized cpu.
I'll buy a new one and re-check.
Thanks for your help.

Re: KVM problems with Xeon L5530

[Matteo Ghezzi]

Upgraded to 2.6.33-rc5, same qemu-kvm version, same hardware.
The Vnc screen is still black and the virtual machine, but now I don't
have anymore messages in the logs but directly at standard output:

KVM internal error. Suberror: 2
extra data[0]: 80000010
extra data[1]: 80000b0d
rax 0000000000000003 rbx 0000000000000065 rcx 0000000000000000 rdx
00000000000003ce
rsi 0000000000000000 rdi 0000000000007ad0 rsp 0000000000006eb0 rbp
0000000000000000
r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11
0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15
0000000000000000
rip 000000000000014a rflags 00010002
cs c000 (000c0000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
ds 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
es f000 (000f0000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
ss 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
fs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
gs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
tr 0000 (feffd000/00002088 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 0/3ff
cr0 10 cr2 0 cr3 0 cr4 0 cr8 0 efer 0

Re: KVM problems with Xeon L5530

[Avi Kivity]

On 01/28/2010 01:02 PM, Matteo Ghezzi wrote:
> Upgraded to 2.6.33-rc5, same qemu-kvm version, same hardware.
> The Vnc screen is still black and the virtual machine, but now I don't
> have anymore messages in the logs but directly at standard output:
>
> KVM internal error. Suberror: 2
> extra data[0]: 80000010
> extra data[1]: 80000b0d
>
> rip 000000000000014a rflags 00010002
> cs c000 (000c0000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
>    

That is basically the same error.

The guest runs the vga vios and hangs.  Please try with a production 
processor.

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

Re: KVM problems with Xeon L5530

[Matteo Ghezzi]

2010/2/7 Avi Kivity <avi@redhat.com>

> That is basically the same error.
>
> The guest runs the vga vios and hangs.  Please try with a production processor.

Working fine with a retail E5520. Thanks for your help.

Re: KVM problems with Xeon L5530

[Kenni Lund]

2010/1/28 Matteo Ghezzi <tenyosama@gmail.com>:
<SNIP>
> I've tried starting the old vmachines on the new hardware but if I
> enable kvm acceleration in qemu I got a black screen via vnc, and the

Enable kvm in qemu? KVM should always be enabled in Arch, when you run
qemu-kvm. You're not running [qemu-executable] --enable-kvm from the
qemu package, right? Last time I checked, the KVM support in upstream
qemu wasn't very good and gave me various errors. Make sure you have
the qemu-kvm package installed and not the qemu package (which also
has KVM support).

Best Regards
Kenni Lund