From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Segfault starting vcpu thread Date: Wed, 11 Jul 2012 14:58:20 +0300 Message-ID: <4FFD6A5C.4060808@redhat.com> References: <4FFD67B2.5090306@redhat.com> <4FFD69A9.2050504@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: KVM list , qemu-devel To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:50703 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753659Ab2GKL61 (ORCPT ); Wed, 11 Jul 2012 07:58:27 -0400 In-Reply-To: <4FFD69A9.2050504@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On 07/11/2012 02:55 PM, Jan Kiszka wrote: > On 2012-07-11 13:46, Avi Kivity wrote: >> Current qemu-kvm master merged with latest upstream fails on startup: >> >> (gdb) bt >> #0 0x00007fdcd4a047a0 in kvm_vcpu_ioctl (env=0x0, type=-1071075694) at >> /home/tlv/akivity/qemu/kvm-all.c:1602 >> #1 0x00007fdcd49c9fda in kvm_apic_enable_tpr_reporting >> (s=0x7fdcd75af6c0, enable=false) at >> /home/tlv/akivity/qemu/hw/i386/../kvm/apic.c:107 >> #2 0x00007fdcd4993d71 in flush_queued_work (env=0x7fdcd75a0c70) at >> /home/tlv/akivity/qemu/cpus.c:680 >> #3 0x00007fdcd4993e23 in qemu_wait_io_event_common (env=0x7fdcd75a0c70) >> at /home/tlv/akivity/qemu/cpus.c:694 >> #4 0x00007fdcd4993f61 in qemu_kvm_wait_io_event (env=0x7fdcd75a0c70) at >> /home/tlv/akivity/qemu/cpus.c:725 >> #5 0x00007fdcd499408c in qemu_kvm_cpu_thread_fn (arg=0x7fdcd75a0c70) at >> /home/tlv/akivity/qemu/cpus.c:757 >> #6 0x00007fdcd2e72d14 in start_thread () from /lib64/libpthread.so.0 >> >> APICCommonState::cpu_env in frame 1 is NULL. I'm looking at it, but if >> you have a quick fix, all the better. >> > > I will try to reproduce. Is there a tree of the merge available? I just merged upstream into qemu-kvm master. For some reason there were no conflicts. > Any > specific command line or guest? qemu-system-x86_64 -- error compiling committee.c: too many arguments to function From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:54855) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sovmb-0001vA-RM for qemu-devel@nongnu.org; Wed, 11 Jul 2012 08:12:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SovmV-00005B-J8 for qemu-devel@nongnu.org; Wed, 11 Jul 2012 08:12:41 -0400 Received: from mx1.redhat.com ([209.132.183.28]:46434) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SovmV-00004r-BH for qemu-devel@nongnu.org; Wed, 11 Jul 2012 08:12:35 -0400 Message-ID: <4FFD6A5C.4060808@redhat.com> Date: Wed, 11 Jul 2012 14:58:20 +0300 From: Avi Kivity MIME-Version: 1.0 References: <4FFD67B2.5090306@redhat.com> <4FFD69A9.2050504@siemens.com> In-Reply-To: <4FFD69A9.2050504@siemens.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Segfault starting vcpu thread List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: qemu-devel , KVM list On 07/11/2012 02:55 PM, Jan Kiszka wrote: > On 2012-07-11 13:46, Avi Kivity wrote: >> Current qemu-kvm master merged with latest upstream fails on startup: >> >> (gdb) bt >> #0 0x00007fdcd4a047a0 in kvm_vcpu_ioctl (env=0x0, type=-1071075694) at >> /home/tlv/akivity/qemu/kvm-all.c:1602 >> #1 0x00007fdcd49c9fda in kvm_apic_enable_tpr_reporting >> (s=0x7fdcd75af6c0, enable=false) at >> /home/tlv/akivity/qemu/hw/i386/../kvm/apic.c:107 >> #2 0x00007fdcd4993d71 in flush_queued_work (env=0x7fdcd75a0c70) at >> /home/tlv/akivity/qemu/cpus.c:680 >> #3 0x00007fdcd4993e23 in qemu_wait_io_event_common (env=0x7fdcd75a0c70) >> at /home/tlv/akivity/qemu/cpus.c:694 >> #4 0x00007fdcd4993f61 in qemu_kvm_wait_io_event (env=0x7fdcd75a0c70) at >> /home/tlv/akivity/qemu/cpus.c:725 >> #5 0x00007fdcd499408c in qemu_kvm_cpu_thread_fn (arg=0x7fdcd75a0c70) at >> /home/tlv/akivity/qemu/cpus.c:757 >> #6 0x00007fdcd2e72d14 in start_thread () from /lib64/libpthread.so.0 >> >> APICCommonState::cpu_env in frame 1 is NULL. I'm looking at it, but if >> you have a quick fix, all the better. >> > > I will try to reproduce. Is there a tree of the merge available? I just merged upstream into qemu-kvm master. For some reason there were no conflicts. > Any > specific command line or guest? qemu-system-x86_64 -- error compiling committee.c: too many arguments to function