Re: [ANNOUNCE] kvm-46 release

Avi Kivity
2007-10-13T07:18:40Z

Farkas Levente wrote:
> Avi Kivity wrote:
>
>> Farkas Levente wrote:
>>
>>>>> we did a quick test against this version and it's turn out the smp
>>>>> guests are still not working. even if we start only one linux guest
>>>>> with
>>>>> 4cpu on 4cpu host the guest kernel hangs at random stages of the kernel
>>>>> loading process (if we run more smp guests then they hang earlier, but
>>>>> different random stage), but it's never reach the end of the kernel so
>>>>> hang somewhere inside the kernel. and the cpu usage of these process
>>>>> goes up to until the qemu-kvm processes eat all cpus (ie. 100%). t
>>>>>
>>>>>
>>>> What host cpu are you using? What guest kernel version? 32-bit or
>>>> 64-bit?
>>>>
>>>> I have no problems running a 4-way Linux guest here.
>>>>
>>>>
>>> - host:
>>> - Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
>>> - Intel S3000AHV
>>> - 8GB RAM
>>> - CentOS-5
>>> - kernel-2.6.18-8.1.14.el5 x86_64 64bit
>>> - guest-1:
>>> - CentOS-5
>>> - kernel-2.6.18-8.1.14.el5 i386 32bit
>>> - guest-2:
>>> - CentOS-5
>>> - kernel-2.6.18-8.1.14.el5 x86_64 64bit
>>> - guest-3:
>>> - Mandrake-9
>>> - kernel-2.4.19.16mdk-1-1mdk 32bit
>>> - guest-4:
>>> - Windows XP Professional 32bit
>>>
>>> start the first guest-1 with 4cpu produce the above hang. (and of course
>>> using kvm-46:-)
>>>
>>>
>>>
>> Is it the only guest that hangs with -smp 4? Or all of them?
>>
>
> if i start this guest alone it's hang. if i start all guest-{1,2,3,4}
> than all linux guest hangs expect windows which runs but see only one
> cpu. ok now i try it for you:-) so:
>
> - host + guest-1 -> hang
>
> - host + guest-2 -> hang
> in this case i've got a stack trace too on the host, and the host
> working 2 more minutes (!?) so i see the top part of the stack
> (shift-pageup) but when i try to take a picture the host crash and i can
> only see the end:-( but next time i bale to catch it:
> -----------------------------------------------
> BUG: soft lockup detected on CPU#0!
>

Yunfeng reports that this has been fixed, can you try the latest
snapshot from http://people.qumranet.com/avi/snapshots/?

--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.