On 08/21/2009 10:14 AM, Xu, Jiajun wrote:
I found the migration failure is caused by a configuration mistake on our testing machine. Now 64-bit migration works well. But I found on PAE host, migration will cause host kernel call trace.
Pid: 12053, comm: qemu-system-x86 Tainted: G D (2.6.31-rc2 #1) EIP: 0060:[<c043e023>] EFLAGS: 00210202 CPU: 0 EIP is at lock_hrtimer_base+0x11/0x33 EAX: f5d1541c EBX: 00000010 ECX: 000004a9 EDX: f5c1bc7c ESI: f5d1541c EDI: f5c1bc7c EBP: f5c1bc74 ESP: f5c1bc68 DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Process qemu-system-x86 (pid: 12053, ti=f5c1b000 task=f61cb410 task.ti=f5c1b000) Stack: f5d1541c ffffffff 000004a9 f5c1bc8c c043e097 f9b7f7cb f5d1541c 00000000 <0> 000004a9 f5c1bc98 c043e0f0 f5d153d0 f5c1bcb0 f9b9b4df 00000000 bfd8a102 <0> f3c1e000 f5d15440 f5c1bcc0 f9b9b56d bfd8a10c f3c1e000 f5c1bda0 f9b8c26b Call Trace: [<c043e097>] ? hrtimer_try_to_cancel+0x16/0x62 [<f9b7f7cb>] ? kvm_flush_remote_tlbs+0xd/0x1a [kvm] [<c043e0f0>] ? hrtimer_cancel+0xd/0x18 [<f9b9b4df>] ? pit_load_count+0x98/0x9e [kvm] [<f9b9b56d>] ? kvm_pit_load_count+0x21/0x35 [kvm]
Marcelo, any idea? Looks like the PIT was reloaded, but the hrtimer wasn't initialized?
-- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
