From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Segfault starting vcpu thread
Date: Wed, 11 Jul 2012 14:58:20 +0300 [thread overview]
Message-ID: <4FFD6A5C.4060808@redhat.com> (raw)
In-Reply-To: <4FFD69A9.2050504@siemens.com>
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
next prev parent reply other threads:[~2012-07-11 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 11:46 [Qemu-devel] Segfault starting vcpu thread Avi Kivity
2012-07-11 11:55 ` Jan Kiszka
2012-07-11 11:58 ` Avi Kivity [this message]
2012-07-11 11:59 ` Jan Kiszka
2012-07-11 12:04 ` Avi Kivity
2012-07-11 12:08 ` Avi Kivity
2012-07-11 12:40 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FFD6A5C.4060808@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).