On Fri, 2008-05-02 at 13:12 +0300, Avi Kivity wrote: > > Call Trace: > > [<c0146d5b>] kmem_cache_create+0x15e/0x410 > > Code: c3 57 56 53 89 c6 9c 5f fa 8b 08 83 39 00 74 12 c7 41 0c 01 00 00 > > 00 8b 01 > > 48 89 01 8b 5c 81 10 eb 07 e8 a5 fb ff ff 89 c3 57 9d <0f> 0d 0b 90 85 > > db 74 1b > > 8b 56 10 31 c0 89 d1 c1 e9 02 89 df f3 > > EIP: [<c01467be>] kmem_cache_zalloc+0x2a/0x53 SS:ESP 0068:c030ff80 > > <0>Kernel panic - not syncing: Attempted to kill the idle task! > > > 0f 0d 0b prefetchw (%ebx) > > This is an AMD 3Dnow! instruction, which is not supported on Intel > processors. I guess the 3Dnow! cpuid bit leaked in via the qemu merge. > > I guess two fixes are needed: > - remove the 3Dnow! bit > - add emulation for prefetchw (easy, as it doesn't need to do anything) > to support live migration from AMD to Intel
This problem still occours with kvm-68. Which CPUs will be affected by this (is it only the Core Duo)? I'm currently delaying the upload of a new kvm package to debian because of this. Thanks, Jan ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
