From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: Seabios incompatible with Linux 2.6.26 host? Date: Fri, 05 Feb 2010 16:07:52 +0100 Message-ID: <4B6C3448.8010204@siemens.com> References: <4B6C2F2B.4050303@siemens.com> <3D47E453-3C6B-467C-B38C-28FD9EA6C3B4@irisa.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: KVM list To: Pierre Riteau Return-path: Received: from thoth.sbs.de ([192.35.17.2]:18675 "EHLO thoth.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932268Ab0BEPHz (ORCPT ); Fri, 5 Feb 2010 10:07:55 -0500 In-Reply-To: <3D47E453-3C6B-467C-B38C-28FD9EA6C3B4@irisa.fr> Sender: kvm-owner@vger.kernel.org List-ID: Pierre Riteau wrote: > On 5 f=E9vr. 2010, at 15:46, Jan Kiszka wrote: >=20 >> Pierre Riteau wrote: >>> On 4 f=E9vr. 2010, at 15:34, Pierre Riteau wrote: >>> >>>> Hello, >>>> I'm having trouble running the latest qemu-kvm code on Debian Lenn= y (Linux 2.6.26). >>>> qemu-kvm dies with an error like this one: >>>> exception 13 (0) >>>> rax 0000000000000010 rbx 0000000000008c00 rcx 0000000000006ebe rdx= 00000000000c8c00 >>>> rsi 00000000e2010000 rdi 00000000000c0000 rsp 0000000000006eb4 rbp= 00000000e2010000 >>>> r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11= 0000000000000000 >>>> r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15= 0000000000000000 >>>> rip 00000000000fdeb0 rflags 00033002 >>>> cs 0000 (00000000/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 0000 (00000000/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 f8aa0/0 >>>> cr0 10 cr2 0 cr3 0 cr4 0 cr8 0 efer 0 >>>> code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 = --> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0= 0 00 00 00 00 00 00 00 >>>> >>>> I think I traced back the issue to the switch from Bochs BIOS to S= eabios. By forcing the usage of Bochs BIOS 5f08bb45861f54be478b25075b90= d2406a0f8bb3 works, while it dies without the -bios override. >>>> Unfortunately, newer versions don't seem to work with Bochs BIOS. >>>> >>>> Upgrading the host kernel to 2.6.32 (Debian Squeeze) solves the is= sue. No problem on Fedora 12 as well. >>> >>> Am I the only one to see this issue? >>> >> The oldest kernels I've running here are 2.6.27. They all run kvm-km= od, >> and they are all happy (mostly). >> >> Are you using the KVM support 2.6.26 provided or are you on some rec= ent >> kvm-kmod? The latter is highly recommended for tons of reasons. >> >> Jan >=20 >=20 > I use the KVM modules provided by the distribution. >=20 Then it makes some sense to try with kvm-kmod first. I do not know what KVM patches debian people back-ported to their kernel, maybe you run into long-fixed bugs. Jan --=20 Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux