Re: [Qemu-devel] Segfault starting vcpu thread

[Avi Kivity]

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