Il 11/07/2012 14:08, Avi Kivity ha scritto:
> 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.
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 0x7fdcd4a047a0 in kvm_vcpu_ioctl (env=0x0, type=-1071075694) at
>> /home/tlv/akivity/qemu/kvm-all.c:1602
>> #1 0x00
On 07/11/2012 03:04 PM, Avi Kivity wrote:
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
autodep
On 07/11/2012 02:59 PM, Jan Kiszka wrote:
>>>
>>> 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
On 2012-07-11 13:58, Avi Kivity wrote:
> 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 0x7fdcd4a047a0 in kvm_vcpu_ioctl (env=0x0, type=-1071075694) at
>>> /ho
On 2012-07-11 13:46, Avi Kivity wrote:
> Current qemu-kvm master merged with latest upstream fails on startup:
>
> (gdb) bt
> #0 0x7fdcd4a047a0 in kvm_vcpu_ioctl (env=0x0, type=-1071075694) at
> /home/tlv/akivity/qemu/kvm-all.c:1602
> #1 0x7fdcd49c9fda in kvm_apic_enable_tpr_reporting
>
Current qemu-kvm master merged with latest upstream fails on startup:
(gdb) bt
#0 0x7fdcd4a047a0 in kvm_vcpu_ioctl (env=0x0, type=-1071075694) at
/home/tlv/akivity/qemu/kvm-all.c:1602
#1 0x7fdcd49c9fda in kvm_apic_enable_tpr_reporting
(s=0x7fdcd75af6c0, enable=false) at
/home/tlv/akivity
