On 16 March 2015 at 18:01, Jan Kiszka <jan.kiszka@xxxxxxxxxxx> wrote: > Can't comment if it's known but, from x86 experiences, such a pattern is > usually related to inconsistency between "get kvm state" and "put kvm > state" in QEMU or the related kernel interfaces: > > QEMU obtains the in-kernel CPU state when you issue "info cpus", marks > it as "dirty" (in case other QEMU functions will manipulate it - won't > happen in this case) and then writes it back to the kernel once the > guest is resumed on that vcpu. If the state you get is not fully > reflecting what you will write back, you corrupt the guest. There are some known issues with migration/state save/load for ARM -- try with Alex Bennee's kernel and QEMU patches that are on the list right now? -- PMM _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
