* Seabios incompatible with Linux 2.6.26 host?
@ 2010-02-04 14:34 Pierre Riteau
2010-02-05 14:27 ` Pierre Riteau
2010-02-05 15:08 ` Christoph Hellwig
0 siblings, 2 replies; 11+ messages in thread
From: Pierre Riteau @ 2010-02-04 14:34 UTC (permalink / raw)
To: KVM list
Hello,
I'm having trouble running the latest qemu-kvm code on Debian Lenny (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 00 00 00 00 00 00 00 00
I think I traced back the issue to the switch from Bochs BIOS to Seabios. By forcing the usage of Bochs BIOS 5f08bb45861f54be478b25075b90d2406a0f8bb3 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 issue. No problem on Fedora 12 as well.
--
Pierre Riteau -- PhD student, Myriads team, IRISA, Rennes, France
http://perso.univ-rennes1.fr/pierre.riteau/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Seabios incompatible with Linux 2.6.26 host?
2010-02-04 14:34 Seabios incompatible with Linux 2.6.26 host? Pierre Riteau
@ 2010-02-05 14:27 ` Pierre Riteau
2010-02-05 14:46 ` Jan Kiszka
2010-02-05 15:08 ` Christoph Hellwig
1 sibling, 1 reply; 11+ messages in thread
From: Pierre Riteau @ 2010-02-05 14:27 UTC (permalink / raw)
To: KVM list
On 4 févr. 2010, at 15:34, Pierre Riteau wrote:
> Hello,
> I'm having trouble running the latest qemu-kvm code on Debian Lenny (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 00 00 00 00 00 00 00 00
>
> I think I traced back the issue to the switch from Bochs BIOS to Seabios. By forcing the usage of Bochs BIOS 5f08bb45861f54be478b25075b90d2406a0f8bb3 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 issue. No problem on Fedora 12 as well.
Am I the only one to see this issue?
--
Pierre Riteau -- PhD student, Myriads team, IRISA, Rennes, France
http://perso.univ-rennes1.fr/pierre.riteau/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Seabios incompatible with Linux 2.6.26 host?
2010-02-05 14:27 ` Pierre Riteau
@ 2010-02-05 14:46 ` Jan Kiszka
2010-02-05 15:05 ` Pierre Riteau
0 siblings, 1 reply; 11+ messages in thread
From: Jan Kiszka @ 2010-02-05 14:46 UTC (permalink / raw)
To: Pierre Riteau; +Cc: KVM list
Pierre Riteau wrote:
> On 4 févr. 2010, at 15:34, Pierre Riteau wrote:
>
>> Hello,
>> I'm having trouble running the latest qemu-kvm code on Debian Lenny (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 00 00 00 00 00 00 00 00
>>
>> I think I traced back the issue to the switch from Bochs BIOS to Seabios. By forcing the usage of Bochs BIOS 5f08bb45861f54be478b25075b90d2406a0f8bb3 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 issue. 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-kmod,
and they are all happy (mostly).
Are you using the KVM support 2.6.26 provided or are you on some recent
kvm-kmod? The latter is highly recommended for tons of reasons.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Seabios incompatible with Linux 2.6.26 host?
2010-02-05 14:46 ` Jan Kiszka
@ 2010-02-05 15:05 ` Pierre Riteau
2010-02-05 15:07 ` Jan Kiszka
0 siblings, 1 reply; 11+ messages in thread
From: Pierre Riteau @ 2010-02-05 15:05 UTC (permalink / raw)
To: Jan Kiszka; +Cc: KVM list
On 5 févr. 2010, at 15:46, Jan Kiszka wrote:
> Pierre Riteau wrote:
>> On 4 févr. 2010, at 15:34, Pierre Riteau wrote:
>>
>>> Hello,
>>> I'm having trouble running the latest qemu-kvm code on Debian Lenny (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 00 00 00 00 00 00 00 00
>>>
>>> I think I traced back the issue to the switch from Bochs BIOS to Seabios. By forcing the usage of Bochs BIOS 5f08bb45861f54be478b25075b90d2406a0f8bb3 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 issue. 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-kmod,
> and they are all happy (mostly).
>
> Are you using the KVM support 2.6.26 provided or are you on some recent
> kvm-kmod? The latter is highly recommended for tons of reasons.
>
> Jan
I use the KVM modules provided by the distribution.
--
Pierre Riteau -- PhD student, Myriads team, IRISA, Rennes, France
http://perso.univ-rennes1.fr/pierre.riteau/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Seabios incompatible with Linux 2.6.26 host?
2010-02-05 15:05 ` Pierre Riteau
@ 2010-02-05 15:07 ` Jan Kiszka
2010-02-08 11:05 ` Pierre Riteau
0 siblings, 1 reply; 11+ messages in thread
From: Jan Kiszka @ 2010-02-05 15:07 UTC (permalink / raw)
To: Pierre Riteau; +Cc: KVM list
Pierre Riteau wrote:
> On 5 févr. 2010, at 15:46, Jan Kiszka wrote:
>
>> Pierre Riteau wrote:
>>> On 4 févr. 2010, at 15:34, Pierre Riteau wrote:
>>>
>>>> Hello,
>>>> I'm having trouble running the latest qemu-kvm code on Debian Lenny (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 00 00 00 00 00 00 00 00
>>>>
>>>> I think I traced back the issue to the switch from Bochs BIOS to Seabios. By forcing the usage of Bochs BIOS 5f08bb45861f54be478b25075b90d2406a0f8bb3 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 issue. 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-kmod,
>> and they are all happy (mostly).
>>
>> Are you using the KVM support 2.6.26 provided or are you on some recent
>> kvm-kmod? The latter is highly recommended for tons of reasons.
>>
>> Jan
>
>
> I use the KVM modules provided by the distribution.
>
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
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Seabios incompatible with Linux 2.6.26 host?
2010-02-05 15:07 ` Jan Kiszka
@ 2010-02-08 11:05 ` Pierre Riteau
2010-02-08 11:13 ` Jan Kiszka
0 siblings, 1 reply; 11+ messages in thread
From: Pierre Riteau @ 2010-02-08 11:05 UTC (permalink / raw)
To: Jan Kiszka; +Cc: KVM list
On 5 févr. 2010, at 16:07, Jan Kiszka wrote:
> Pierre Riteau wrote:
>> On 5 févr. 2010, at 15:46, Jan Kiszka wrote:
>>
>>> Pierre Riteau wrote:
>>>> On 4 févr. 2010, at 15:34, Pierre Riteau wrote:
>>>>
>>>>> Hello,
>>>>> I'm having trouble running the latest qemu-kvm code on Debian Lenny (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 00 00 00 00 00 00 00 00
>>>>>
>>>>> I think I traced back the issue to the switch from Bochs BIOS to Seabios. By forcing the usage of Bochs BIOS 5f08bb45861f54be478b25075b90d2406a0f8bb3 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 issue. 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-kmod,
>>> and they are all happy (mostly).
>>>
>>> Are you using the KVM support 2.6.26 provided or are you on some recent
>>> kvm-kmod? The latter is highly recommended for tons of reasons.
>>>
>>> Jan
>>
>>
>> I use the KVM modules provided by the distribution.
>>
>
> 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.
I confirm that this exception does not happen with kvm-kmod-2.6.33-rc6.
However, after I run and stop a guest VM just executing the bios sequence (no disk/CD image attached), I get this kind of errors on the host when untar a small archive (less than 1MB, about 300 files):
Feb 8 12:00:32 paraquad-7 kernel: [ 200.073865] Bad page state in process 'gzip'
Feb 8 12:00:32 paraquad-7 kernel: [ 200.073867] page:ffffe200040c4638 flags:0x020000000000001c mapping:0000000000000000 mapcount:0 count:0
Feb 8 12:00:32 paraquad-7 kernel: [ 200.102991] Trying to fix it up, but a reboot is needed
Feb 8 12:00:32 paraquad-7 kernel: [ 200.102992] Backtrace:
Feb 8 12:00:32 paraquad-7 kernel: [ 200.129821] Pid: 3559, comm: gzip Tainted: P 2.6.26-2-amd64 #1
Feb 8 12:00:32 paraquad-7 kernel: [ 200.143267]
Feb 8 12:00:32 paraquad-7 kernel: [ 200.143268] Call Trace:
Feb 8 12:00:32 paraquad-7 kernel: [ 200.156024] [<ffffffff8022f0d2>] hrtick_set+0x88/0xf7
Feb 8 12:00:32 paraquad-7 kernel: [ 200.167250] [<ffffffff8027504d>] bad_page+0x6b/0x95
Feb 8 12:00:32 paraquad-7 kernel: [ 200.179879] [<ffffffff80276482>] get_page_from_freelist+0x3e1/0x606
Feb 8 12:00:32 paraquad-7 kernel: [ 200.195345] [<ffffffff80276929>] __alloc_pages_internal+0xd6/0x3bf
Feb 8 12:00:32 paraquad-7 kernel: [ 200.210580] [<ffffffff80281707>] handle_mm_fault+0x244/0x867
Feb 8 12:00:32 paraquad-7 kernel: [ 200.223694] [<ffffffff8027313a>] filemap_fault+0x1c2/0x33c
Feb 8 12:00:32 paraquad-7 kernel: [ 200.237948] [<ffffffff80221fbc>] do_page_fault+0x5d8/0x9c8
Feb 8 12:00:32 paraquad-7 kernel: [ 200.251793] [<ffffffff8042a599>] error_exit+0x0/0x60
Feb 8 12:00:32 paraquad-7 kernel: [ 200.265754] [<ffffffff80270df1>] file_read_actor+0x52/0x125
Feb 8 12:00:32 paraquad-7 kernel: [ 200.278595] [<ffffffff802764fb>] get_page_from_freelist+0x45a/0x606
Feb 8 12:00:32 paraquad-7 kernel: [ 200.294022] [<ffffffff80272c03>] generic_file_aio_read+0x29e/0x4ae
Feb 8 12:00:32 paraquad-7 kernel: [ 200.309319] [<ffffffff8029ae47>] do_sync_read+0xc9/0x10c
Feb 8 12:00:32 paraquad-7 kernel: [ 200.322816] [<ffffffff80246221>] autoremove_wake_function+0x0/0x2e
Feb 8 12:00:32 paraquad-7 kernel: [ 200.338051] [<ffffffff80221fbc>] do_page_fault+0x5d8/0x9c8
Feb 8 12:00:32 paraquad-7 kernel: [ 200.351919] [<ffffffff8029b638>] vfs_read+0xaa/0x152
Feb 8 12:00:32 paraquad-7 kernel: [ 200.366108] [<ffffffff8029ba19>] sys_read+0x45/0x6e
Feb 8 12:00:32 paraquad-7 kernel: [ 200.378750] [<ffffffff8020beca>] system_call_after_swapgs+0x8a/0x8f
--
Pierre Riteau -- PhD student, Myriads team, IRISA, Rennes, France
http://perso.univ-rennes1.fr/pierre.riteau/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Seabios incompatible with Linux 2.6.26 host?
2010-02-08 11:05 ` Pierre Riteau
@ 2010-02-08 11:13 ` Jan Kiszka
2010-02-08 12:21 ` Avi Kivity
0 siblings, 1 reply; 11+ messages in thread
From: Jan Kiszka @ 2010-02-08 11:13 UTC (permalink / raw)
To: Pierre Riteau; +Cc: KVM list
Pierre Riteau wrote:
> On 5 févr. 2010, at 16:07, Jan Kiszka wrote:
>
>> Pierre Riteau wrote:
>>> On 5 févr. 2010, at 15:46, Jan Kiszka wrote:
>>>
>>>> Pierre Riteau wrote:
>>>>> On 4 févr. 2010, at 15:34, Pierre Riteau wrote:
>>>>>
>>>>>> Hello,
>>>>>> I'm having trouble running the latest qemu-kvm code on Debian Lenny (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 00 00 00 00 00 00 00 00
>>>>>>
>>>>>> I think I traced back the issue to the switch from Bochs BIOS to Seabios. By forcing the usage of Bochs BIOS 5f08bb45861f54be478b25075b90d2406a0f8bb3 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 issue. 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-kmod,
>>>> and they are all happy (mostly).
>>>>
>>>> Are you using the KVM support 2.6.26 provided or are you on some recent
>>>> kvm-kmod? The latter is highly recommended for tons of reasons.
>>>>
>>>> Jan
>>>
>>> I use the KVM modules provided by the distribution.
>>>
>> 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.
>
>
> I confirm that this exception does not happen with kvm-kmod-2.6.33-rc6.
>
> However, after I run and stop a guest VM just executing the bios sequence (no disk/CD image attached), I get this kind of errors on the host when untar a small archive (less than 1MB, about 300 files):
>
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.073865] Bad page state in process 'gzip'
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.073867] page:ffffe200040c4638 flags:0x020000000000001c mapping:0000000000000000 mapcount:0 count:0
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.102991] Trying to fix it up, but a reboot is needed
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.102992] Backtrace:
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.129821] Pid: 3559, comm: gzip Tainted: P 2.6.26-2-amd64 #1
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.143267]
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.143268] Call Trace:
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.156024] [<ffffffff8022f0d2>] hrtick_set+0x88/0xf7
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.167250] [<ffffffff8027504d>] bad_page+0x6b/0x95
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.179879] [<ffffffff80276482>] get_page_from_freelist+0x3e1/0x606
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.195345] [<ffffffff80276929>] __alloc_pages_internal+0xd6/0x3bf
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.210580] [<ffffffff80281707>] handle_mm_fault+0x244/0x867
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.223694] [<ffffffff8027313a>] filemap_fault+0x1c2/0x33c
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.237948] [<ffffffff80221fbc>] do_page_fault+0x5d8/0x9c8
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.251793] [<ffffffff8042a599>] error_exit+0x0/0x60
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.265754] [<ffffffff80270df1>] file_read_actor+0x52/0x125
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.278595] [<ffffffff802764fb>] get_page_from_freelist+0x45a/0x606
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.294022] [<ffffffff80272c03>] generic_file_aio_read+0x29e/0x4ae
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.309319] [<ffffffff8029ae47>] do_sync_read+0xc9/0x10c
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.322816] [<ffffffff80246221>] autoremove_wake_function+0x0/0x2e
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.338051] [<ffffffff80221fbc>] do_page_fault+0x5d8/0x9c8
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.351919] [<ffffffff8029b638>] vfs_read+0xaa/0x152
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.366108] [<ffffffff8029ba19>] sys_read+0x45/0x6e
> Feb 8 12:00:32 paraquad-7 kernel: [ 200.378750] [<ffffffff8020beca>] system_call_after_swapgs+0x8a/0x8f
>
Haven't seen this before. Can you reproduce it with
a) kvm-kmod-2.6.32.7?
b) a host kernel >= 2.6.27?
Thanks,
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Seabios incompatible with Linux 2.6.26 host?
2010-02-08 11:13 ` Jan Kiszka
@ 2010-02-08 12:21 ` Avi Kivity
2010-02-09 22:49 ` Pierre Riteau
0 siblings, 1 reply; 11+ messages in thread
From: Avi Kivity @ 2010-02-08 12:21 UTC (permalink / raw)
To: Jan Kiszka; +Cc: Pierre Riteau, KVM list
On 02/08/2010 01:13 PM, Jan Kiszka wrote:
>>
>> I confirm that this exception does not happen with kvm-kmod-2.6.33-rc6.
>>
>> However, after I run and stop a guest VM just executing the bios sequence (no disk/CD image attached), I get this kind of errors on the host when untar a small archive (less than 1MB, about 300 files):
>>
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.073865] Bad page state in process 'gzip'
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.073867] page:ffffe200040c4638 flags:0x020000000000001c mapping:0000000000000000 mapcount:0 count:0
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.102991] Trying to fix it up, but a reboot is needed
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.102992] Backtrace:
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.129821] Pid: 3559, comm: gzip Tainted: P 2.6.26-2-amd64 #1
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.143267]
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.143268] Call Trace:
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.156024] [<ffffffff8022f0d2>] hrtick_set+0x88/0xf7
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.167250] [<ffffffff8027504d>] bad_page+0x6b/0x95
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.179879] [<ffffffff80276482>] get_page_from_freelist+0x3e1/0x606
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.195345] [<ffffffff80276929>] __alloc_pages_internal+0xd6/0x3bf
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.210580] [<ffffffff80281707>] handle_mm_fault+0x244/0x867
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.223694] [<ffffffff8027313a>] filemap_fault+0x1c2/0x33c
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.237948] [<ffffffff80221fbc>] do_page_fault+0x5d8/0x9c8
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.251793] [<ffffffff8042a599>] error_exit+0x0/0x60
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.265754] [<ffffffff80270df1>] file_read_actor+0x52/0x125
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.278595] [<ffffffff802764fb>] get_page_from_freelist+0x45a/0x606
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.294022] [<ffffffff80272c03>] generic_file_aio_read+0x29e/0x4ae
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.309319] [<ffffffff8029ae47>] do_sync_read+0xc9/0x10c
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.322816] [<ffffffff80246221>] autoremove_wake_function+0x0/0x2e
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.338051] [<ffffffff80221fbc>] do_page_fault+0x5d8/0x9c8
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.351919] [<ffffffff8029b638>] vfs_read+0xaa/0x152
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.366108] [<ffffffff8029ba19>] sys_read+0x45/0x6e
>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.378750] [<ffffffff8020beca>] system_call_after_swapgs+0x8a/0x8f
>>
>>
> Haven't seen this before. Can you reproduce it with
>
> a) kvm-kmod-2.6.32.7?
> b) a host kernel>= 2.6.27?
>
Good guess - perhaps we are busted without mmu notifiers. For b),
please ensure CONFIG_MMU_NOTIFIER is enabled in the host kernel
configuration.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Seabios incompatible with Linux 2.6.26 host?
2010-02-08 12:21 ` Avi Kivity
@ 2010-02-09 22:49 ` Pierre Riteau
0 siblings, 0 replies; 11+ messages in thread
From: Pierre Riteau @ 2010-02-09 22:49 UTC (permalink / raw)
To: Avi Kivity; +Cc: Jan Kiszka, KVM list
On 8 févr. 2010, at 13:21, Avi Kivity wrote:
> On 02/08/2010 01:13 PM, Jan Kiszka wrote:
>>>
>>> I confirm that this exception does not happen with kvm-kmod-2.6.33-rc6.
>>>
>>> However, after I run and stop a guest VM just executing the bios sequence (no disk/CD image attached), I get this kind of errors on the host when untar a small archive (less than 1MB, about 300 files):
>>>
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.073865] Bad page state in process 'gzip'
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.073867] page:ffffe200040c4638 flags:0x020000000000001c mapping:0000000000000000 mapcount:0 count:0
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.102991] Trying to fix it up, but a reboot is needed
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.102992] Backtrace:
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.129821] Pid: 3559, comm: gzip Tainted: P 2.6.26-2-amd64 #1
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.143267]
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.143268] Call Trace:
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.156024] [<ffffffff8022f0d2>] hrtick_set+0x88/0xf7
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.167250] [<ffffffff8027504d>] bad_page+0x6b/0x95
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.179879] [<ffffffff80276482>] get_page_from_freelist+0x3e1/0x606
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.195345] [<ffffffff80276929>] __alloc_pages_internal+0xd6/0x3bf
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.210580] [<ffffffff80281707>] handle_mm_fault+0x244/0x867
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.223694] [<ffffffff8027313a>] filemap_fault+0x1c2/0x33c
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.237948] [<ffffffff80221fbc>] do_page_fault+0x5d8/0x9c8
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.251793] [<ffffffff8042a599>] error_exit+0x0/0x60
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.265754] [<ffffffff80270df1>] file_read_actor+0x52/0x125
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.278595] [<ffffffff802764fb>] get_page_from_freelist+0x45a/0x606
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.294022] [<ffffffff80272c03>] generic_file_aio_read+0x29e/0x4ae
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.309319] [<ffffffff8029ae47>] do_sync_read+0xc9/0x10c
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.322816] [<ffffffff80246221>] autoremove_wake_function+0x0/0x2e
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.338051] [<ffffffff80221fbc>] do_page_fault+0x5d8/0x9c8
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.351919] [<ffffffff8029b638>] vfs_read+0xaa/0x152
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.366108] [<ffffffff8029ba19>] sys_read+0x45/0x6e
>>> Feb 8 12:00:32 paraquad-7 kernel: [ 200.378750] [<ffffffff8020beca>] system_call_after_swapgs+0x8a/0x8f
>>>
>>>
>> Haven't seen this before. Can you reproduce it with
>>
>> a) kvm-kmod-2.6.32.7?
Same problem with this version loaded in the 2.6.26 kernel.
>> b) a host kernel>= 2.6.27?
>>
>
> Good guess - perhaps we are busted without mmu notifiers. For b), please ensure CONFIG_MMU_NOTIFIER is enabled in the host kernel configuration.
Very good guess indeed!
2.6.27 with KVM enabled (so CONFIG_MMU_NOTIFIER=y) and kvm-kmod-2.6.33-rc6 works OK.
2.6.27 with KVM disabled (so CONFIG_MMU_NOTIFIER is also disabled) and kvm-kmod-2.6.33-rc6 shows the Bad page state errors.
--
Pierre Riteau -- PhD student, Myriads team, IRISA, Rennes, France
http://perso.univ-rennes1.fr/pierre.riteau/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Seabios incompatible with Linux 2.6.26 host?
2010-02-04 14:34 Seabios incompatible with Linux 2.6.26 host? Pierre Riteau
2010-02-05 14:27 ` Pierre Riteau
@ 2010-02-05 15:08 ` Christoph Hellwig
2010-02-05 16:53 ` Jan Kiszka
1 sibling, 1 reply; 11+ messages in thread
From: Christoph Hellwig @ 2010-02-05 15:08 UTC (permalink / raw)
To: Pierre Riteau; +Cc: KVM list
On Thu, Feb 04, 2010 at 03:34:24PM +0100, Pierre Riteau wrote:
> I think I traced back the issue to the switch from Bochs BIOS to Seabios. By forcing the usage of Bochs BIOS 5f08bb45861f54be478b25075b90d2406a0f8bb3 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 issue. No problem on Fedora 12 as well.
Even Linux 2.6.31 stopped working as a host for me since that commit.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Seabios incompatible with Linux 2.6.26 host?
2010-02-05 15:08 ` Christoph Hellwig
@ 2010-02-05 16:53 ` Jan Kiszka
0 siblings, 0 replies; 11+ messages in thread
From: Jan Kiszka @ 2010-02-05 16:53 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: Pierre Riteau, KVM list
Christoph Hellwig wrote:
> On Thu, Feb 04, 2010 at 03:34:24PM +0100, Pierre Riteau wrote:
>> I think I traced back the issue to the switch from Bochs BIOS to Seabios. By forcing the usage of Bochs BIOS 5f08bb45861f54be478b25075b90d2406a0f8bb3 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 issue. No problem on Fedora 12 as well.
>
> Even Linux 2.6.31 stopped working as a host for me since that commit.
At least kvm-kmod-2.6.31.6 worked fine here, just recently run it with
various versions of qemu-kvm.
Does it bail out at the same address like Pierre? Looking at the code
that fails, ljmp $0xf000,$0xdeb5, it might be affected by the KVM commit
ee3d29e8be (KVM: x86 emulator: fix jmp far decoding (opcode 0xea)) which
predates 2.6.31.1...
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2010-02-09 22:49 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-02-04 14:34 Seabios incompatible with Linux 2.6.26 host? Pierre Riteau
2010-02-05 14:27 ` Pierre Riteau
2010-02-05 14:46 ` Jan Kiszka
2010-02-05 15:05 ` Pierre Riteau
2010-02-05 15:07 ` Jan Kiszka
2010-02-08 11:05 ` Pierre Riteau
2010-02-08 11:13 ` Jan Kiszka
2010-02-08 12:21 ` Avi Kivity
2010-02-09 22:49 ` Pierre Riteau
2010-02-05 15:08 ` Christoph Hellwig
2010-02-05 16:53 ` Jan Kiszka
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox