Re: kvm-85 sometimes not starting on 2.6.30-rc5

[Nikola Ciprich <extmaillist@linuxbox.cz>]

Hi,
somehow this thread ended without any conclusion. Today I noticed
that 
BUG: MAX_LOCK_DEPTH too low! 
still shows up when starting kvm on 2.6.31-rc8

So is increasing MAX_LOCK_DEPTH to say 96 good way to go?
If yes, shouldn't we set this for upstream kernel?
thanks
nik


On Sun, May 24, 2009 at 12:47:49PM +0300, Avi Kivity wrote:
> Andrea Arcangeli wrote:
>> On Sun, May 17, 2009 at 11:27:42PM +0300, Avi Kivity wrote:
>>   
>>> Andrea, looks like the mother of all locks below.
>>>     
>>
>> eheh yes that really is the mother of all locks ;).
>>
>> So the thing is, like BUG says MAX_LOCK_DEPTH is too low, to fix you
>> should rebuild after increasing it in include/linux/sched.h to say 96.
>>
>> Likely somebody changed qemu-kvm over time in a way that allocates
>> more vmas than before.
>>   
>
> It does, we now have a vma for each discontiguous memory region (640K,  
> vga bios, bios, 1M+ memory, framebuffer, 4G+ memory).
>
> Still, we have a lot more vmas in qemu for the various dynamic  
> libraries, etc.  I'm surprised it made such a difference.
>
> -- 
> 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 majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

-- 
-------------------------------------
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:    +420 596 621 273
mobil:  +420 777 093 799
www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------