Re: KVM problems with Xeon L5530
2010/2/7 Avi Kivity a...@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. -- 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
Re: KVM problems with Xeon L5530
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]: 8010 extra data[1]: 8b0d rip 014a rflags 00010002 cs c000 (000c/ 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 -- 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
Re: KVM problems with Xeon L5530
2010/1/28 Brian Jackson i...@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. -- 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
Re: KVM problems with Xeon L5530
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]: 8010 extra data[1]: 8b0d rax 0003 rbx 0065 rcx rdx 03ce rsi rdi 7ad0 rsp 6eb0 rbp r8 r9 r10 r11 r12 r13 r14 r15 rip 014a rflags 00010002 cs c000 (000c/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ds (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) es f000 (000f/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ss (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) fs (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) gs (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) tr (feffd000/2088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt (/ 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 -- 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
Re: KVM problems with Xeon L5530
2010/1/28 Matteo Ghezzi tenyos...@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 -- 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
KVM problems with Xeon L5530
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 0x800d intr info 0x8b0d 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: KVM problems with Xeon L5530
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 0x800d intr info 0x8b0d 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- 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
