Segfault starting vcpu thread
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.
Signature · 1 line
error compiling committee.c: too many arguments to function
Quoted 18 lines · Avi Kivity
Current qemu-kvm master merged with latest upstream fails on startup:
(gdb) bt
#00x00007fdcd4a047a0inkvm_vcpu_ioctl(env=0x0, type=-1071075694) at/home/tlv/akivity/qemu/kvm-all.c:1602
#10x00007fdcd49c9fdainkvm_apic_enable_tpr_reporting(s=0x7fdcd75af6c0, enable=false) at/home/tlv/akivity/qemu/hw/i386/../kvm/apic.c:107
#20x00007fdcd4993d71inflush_queued_work(env=0x7fdcd75a0c70) at/home/tlv/akivity/qemu/cpus.c:680
#30x00007fdcd4993e23inqemu_wait_io_event_common(env=0x7fdcd75a0c70) at/home/tlv/akivity/qemu/cpus.c:694
#40x00007fdcd4993f61inqemu_kvm_wait_io_event(env=0x7fdcd75a0c70) at/home/tlv/akivity/qemu/cpus.c:725
#50x00007fdcd499408cinqemu_kvm_cpu_thread_fn(arg=0x7fdcd75a0c70) at/home/tlv/akivity/qemu/cpus.c:757
#60x00007fdcd2e72d14instart_thread() from/lib64/libpthread.so.0
Quoted 3 lines
APICCommonState::cpu_envin 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? Any specific command line or guest?
Jan
Signature · 2 lines
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE Corporate Competence Center Embedded Linux
Quoted 19 lines · Jan Kiszka
Quoted 18 lines · Avi Kivity
Current qemu-kvm master merged with latest upstream fails on startup:
(gdb) bt
#00x00007fdcd4a047a0inkvm_vcpu_ioctl(env=0x0, type=-1071075694) at/home/tlv/akivity/qemu/kvm-all.c:1602
#10x00007fdcd49c9fdainkvm_apic_enable_tpr_reporting(s=0x7fdcd75af6c0, enable=false) at/home/tlv/akivity/qemu/hw/i386/../kvm/apic.c:107
#20x00007fdcd4993d71inflush_queued_work(env=0x7fdcd75a0c70) at/home/tlv/akivity/qemu/cpus.c:680
#30x00007fdcd4993e23inqemu_wait_io_event_common(env=0x7fdcd75a0c70) at/home/tlv/akivity/qemu/cpus.c:694
#40x00007fdcd4993f61inqemu_kvm_wait_io_event(env=0x7fdcd75a0c70) at/home/tlv/akivity/qemu/cpus.c:725
#50x00007fdcd499408cinqemu_kvm_cpu_thread_fn(arg=0x7fdcd75a0c70) at/home/tlv/akivity/qemu/cpus.c:757
#60x00007fdcd2e72d14instart_thread() from/lib64/libpthread.so.0
Quoted 5 lines
Quoted 3 lines
APICCommonState::cpu_envin 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.
Quoted 2 lines
Any
specific command line or guest?
qemu-system-x86_64
Signature · 1 line
error compiling committee.c: too many arguments to function
Quoted 20 lines · Avi Kivity
Quoted 19 lines · Jan Kiszka
Quoted 18 lines · Avi Kivity
Current qemu-kvm master merged with latest upstream fails on startup:
(gdb) bt
#00x00007fdcd4a047a0inkvm_vcpu_ioctl(env=0x0, type=-1071075694) at/home/tlv/akivity/qemu/kvm-all.c:1602
#10x00007fdcd49c9fdainkvm_apic_enable_tpr_reporting(s=0x7fdcd75af6c0, enable=false) at/home/tlv/akivity/qemu/hw/i386/../kvm/apic.c:107
#20x00007fdcd4993d71inflush_queued_work(env=0x7fdcd75a0c70) at/home/tlv/akivity/qemu/cpus.c:680
#30x00007fdcd4993e23inqemu_wait_io_event_common(env=0x7fdcd75a0c70) at/home/tlv/akivity/qemu/cpus.c:694
#40x00007fdcd4993f61inqemu_kvm_wait_io_event(env=0x7fdcd75a0c70) at/home/tlv/akivity/qemu/cpus.c:725
#50x00007fdcd499408cinqemu_kvm_cpu_thread_fn(arg=0x7fdcd75a0c70) at/home/tlv/akivity/qemu/cpus.c:757
#60x00007fdcd2e72d14instart_thread() from/lib64/libpthread.so.0
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
APICCommonState::cpu_envin 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.
A rare moment, I guess. ;)
Quoted 5 lines
Quoted 3 lines
Any
specific command line or guest?qemu-system-x86_64
Just did the same, but it's all fine here.
Jan
Signature · 2 lines
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE Corporate Competence Center Embedded Linux
Quoted 7 lines · Jan Kiszka
Quoted 5 lines
Quoted 2 lines
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.
A rare moment, I guess. ;)
I'll put it down to random chance until we can figure out who's responsible.
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
Any
specific command line or guest?qemu-system-x86_64
Just did the same, but it's all fine here.
Ok, I'll debug it. Probably something stupid like a miscompile.
Signature · 1 line
error compiling committee.c: too many arguments to function
Quoted 7 lines · Avi Kivity
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
specific command line or guest?
qemu-system-x86_64
Just did the same, but it's all fine here.
Ok, I'll debug it. Probably something stupid like a miscompile.
Indeed, a simple clean build fixed it up. Paolo, it looks like autodependencies are still broken.
Signature · 1 line
error compiling committee.c: too many arguments to function
Paolo Bonzini
maintainerIl 11/07/2012 14:08, Avi Kivity ha scritto:
Quoted 9 lines
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
Quoted 5 lines
specific command line or guest?
Quoted 2 lines
Quoted 2 lines
qemu-system-x86_64
Just did the same, but it's all fine here.
Ok, I'll debug it. Probably something stupid like a miscompile.
Indeed, a simple clean build fixed it up. Paolo, it looks like autodependencies are still broken.
Hmm, I think everything happened while I was away. I'll take a look.
Paolo