[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kvm
Subject:    Re: random crash in post_kvm_run()
From:       BuraphaLinux Server <buraphalinuxserver () gmail ! com>
Date:       2010-06-30 18:32:08
Message-ID: AANLkTilkOZNr2LJ0LDq9zmGaRvY3GKo2i17Z72DF1bFI () mail ! gmail ! com
[Download RAW message or body]

On 7/1/10, Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 06/28/2010 12:28 PM, BuraphaLinux Server wrote:
>> Hello,
>>
>>      I have tried qemu_kvm 0.12.4 release and also git from about 1/2
>> an hour ago.  In both cases, I crash in the post_kvm_run() function on
>> the line about:
>>
>> pthread_mutex_lock(&qemu_mutex);
>>
>> The command I use to run qemu worked great with
>> glibc-2.11.1,linux-2.6.32.14,and gcc-4.4.3,
>> but I have upgraded to glibc-2.11.2, linux-2.6.34, and gcc-4.4.4 and get
>> this:
>>
>> (gdb) bt
>> #0  post_kvm_run (kvm=0x84cde04, env=0x84e7168)
>>      at /tmp/qemu-kvm-201006282359/qemu-kvm.c:566
>> #1  0x08086ccf in kvm_run (env=0x84e7168)
>>      at /tmp/qemu-kvm-201006282359/qemu-kvm.c:619
>> #2  0x080882d0 in kvm_cpu_exec (env=0x84e7168)
>>      at /tmp/qemu-kvm-201006282359/qemu-kvm.c:1238
>> #3  0x08088cf6 in kvm_main_loop_cpu (env=0x84e7168)
>>      at /tmp/qemu-kvm-201006282359/qemu-kvm.c:1495
>> #4  0x08088e72 in ap_main_loop (_env=0x84e7168)
>>      at /tmp/qemu-kvm-201006282359/qemu-kvm.c:1541
>> #5  0x55598690 in start_thread () from /lib/libpthread.so.0
>> #6  0x55a8ca7e in clone () from /lib/libc.so.6
>> (gdb) list
>> 561     in /tmp/qemu-kvm-201006282359/qemu-kvm.c
>> (gdb) print qemu_mutex
>> $1 = {__data = {__lock = 0, __count = 0, __owner = 0, __kind = 0,
>>      __nusers = 0, {__spins = 0, __list = {__next = 0x0}}},
>>    __size = '\000'<repeats 23 times>, __align = 0}
>> (gdb)
>>
>> I rebuilt the kernel, then glibc, then the entire graphics stack, then
>> qemu_kvm to try and be sure I have no problems about headers.  All my
>> other software works, but qemu_kvm does not.  About 1 time in 10 it
>> will actually run fine, but the other times it will crash as shown.  I
>> use a dedicated LV for this.  I have a 32bit userland with a 64bit
>> kernel.
>
> This is an unusual configuration.  Is it possible try try a 64-bit userland?
>
> Regards,
>
> Anthony Liguori

Not at this time, since I haven't ever built a 64bit userland with my
32bit userland yet.  The purpose of getting things working in KVM (for
me) is laregely to support a 'safe' place to experiment with creating
such a 64bit userland.  Unfortunately I've hit this snag.  However.
thank you for the suggestion.

JGH
--
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
[prev in list] [next in list] [prev in thread] [next in thread]