Il 11/09/2014 19:03, Chris Webb ha scritto:
Paolo Bonzini pbonz...@redhat.com 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 arguments)?
Sure, no problem. I've built the
Paolo Bonzini pbonz...@redhat.com wrote:
Il 11/09/2014 19:03, Chris Webb ha scritto:
Paolo Bonzini pbonz...@redhat.com 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
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 fixed
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
Paolo Bonzini pbonz...@redhat.com 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 arguments)?
Sure, no problem. I've built the trace-cmd tool against udis86 (I hope) and
have
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
