Il 22/09/2014 21:08, Chris Webb ha scritto:
> > Do you by chance have CONFIG_DEBUG_RODATA set? In that case, the fix is
> > simply not to set it.
>
> Absolutely right: my host and guest kernels do have CONFIG_DEBUG_RODATA set!
>
> Your patch to use alternatives for VMCALL vs VMMCALL definitely f
Paolo Bonzini wrote:
> Il 11/09/2014 19:03, Chris Webb ha scritto:
>> Paolo Bonzini wrote:
>>
>>> This is a hypercall that should have kicked VCPU 3 (see rcx).
>>>
>>> Can you please apply this patch and gather a trace of the host
>>> (using "trace-cmd -e kvm qemu-kvm ")?
>>
>> Sure, no probl
Il 11/09/2014 19:03, Chris Webb ha scritto:
> Paolo Bonzini wrote:
>
>> This is a hypercall that should have kicked VCPU 3 (see rcx).
>>
>> Can you please apply this patch and gather a trace of the host
>> (using "trace-cmd -e kvm qemu-kvm ")?
>
> Sure, no problem. I've built the trace-cmd tool
Paolo Bonzini wrote:
> This is a hypercall that should have kicked VCPU 3 (see rcx).
>
> Can you please apply this patch and gather a trace of the host
> (using "trace-cmd -e kvm qemu-kvm ")?
Sure, no problem. I've built the trace-cmd tool against udis86 (I hope) and
have put the resulting trac
Il 08/09/2014 15:28, Chris Webb ha scritto:
> divide error: [#1] PREEMPT SMP
> Modules linked in:
> CPU: 0 PID: 743 Comm: syslogd Not tainted 3.16.2-guest #2
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS
> rel-1.7.5-0-ge51488c-20140602_164612-nilsson.home.kraxel.org 04/01/2014
>
I've reported this bug before, which reliably crashes a guest kernel shortly
after boot, but have just reconfirmed that it is still present with Linux
3.16.2 guest and host kernels and Qemu 2.1.
Running a 3.16.2 x86-64 SMP guest kernel on qemu-2.1, with kvm enabled and
-cpu host on a 3.16.2 AMD Op
I see kernel 3.15 is now out, so I retested with 3.15 guest and host. I'm
still getting exactly the same guest kernel panic: a divide error in
kvm_unlock_kick with -cpu host, but not with -cpu qemu64:
divide error: [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 781 Comm: mkdir Not ta
I realised my original bug report was for a guest kernel compiled without
frame pointers which might be unhelpful, so I enabled CONFIG_DEBUG_INFO and
CONFIG_FRAME_POINTER, but I don't think this has made the backtrace any more
detailed.
Is there anything more I can do to pinpoint what might be goi
Paolo Bonzini wrote:
> Il 29/05/2014 19:45, Chris Webb ha scritto:
>> Chris Webb wrote:
>>
>>> My CPU flags inside the crashing guest look like this:
>>>
>>> fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36
>>> clflush
>>> mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
Il 29/05/2014 19:45, Chris Webb ha scritto:
Chris Webb wrote:
My CPU flags inside the crashing guest look like this:
fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush
mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb lm rep_good nopl
extd_apicid pni pclmulq
Chris Webb wrote:
> My CPU flags inside the crashing guest look like this:
>
> fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36
> clflush
> mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb lm rep_good nopl
> extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2
Running a 3.14.4 x86-64 SMP guest kernel on qemu-2.0, with kvm enabled and
-cpu host on a 3.14.4 AMD Opteron host, I'm seeing a reliable kernel panic from
the guest shortly after boot. I think is happening in kvm_unlock_kick() in the
paravirt_ops code:
divide error: [#1] PREEMPT SMP
Modules
12 matches
Mail list logo
