[kvm-devel] Oops on 2.6.23.11 with KVM 57

2007-12-21 Thread Guido Guenther
Hi, I got the Oops below on an Dual CPU Dual-Core AMD Opteron(tm) Processor 2220 running a 32bit kernel. Kernel is 2.6.23.11, kvm version 57. Doesn't happen all the time but usually right at VM startup. Seems to be easier to trigger when starting up several VMs in row. Does it help to post more of

Re: [kvm-devel] Oops on 2.6.23.11 with KVM 57

2007-12-22 Thread Avi Kivity
Guido Guenther wrote: > Hi, > I got the Oops below on an Dual CPU Dual-Core AMD Opteron(tm) Processor > 2220 running a 32bit kernel. Kernel is 2.6.23.11, kvm version 57. > Doesn't happen all the time but usually right at VM startup. Seems to be > easier to trigger when starting up several VMs in ro

Re: [kvm-devel] Oops on 2.6.23.11 with KVM 57

2007-12-27 Thread Guido Guenther
On Sat, Dec 22, 2007 at 09:59:43PM +0200, Avi Kivity wrote: > Guido Guenther wrote: > > Hi, > > I got the Oops below on an Dual CPU Dual-Core AMD Opteron(tm) Processor > > 2220 running a 32bit kernel. Kernel is 2.6.23.11, kvm version 57. > > Doesn't happen all the time but usually right at VM start

Re: [kvm-devel] Oops on 2.6.23.11 with KVM 57

2007-12-27 Thread Avi Kivity
Guido Guenther wrote: > On Sat, Dec 22, 2007 at 09:59:43PM +0200, Avi Kivity wrote: > >> Guido Guenther wrote: >> >>> Hi, >>> I got the Oops below on an Dual CPU Dual-Core AMD Opteron(tm) Processor >>> 2220 running a 32bit kernel. Kernel is 2.6.23.11, kvm version 57. >>> Doesn't happen all

Re: [kvm-devel] Oops on 2.6.23.11 with KVM 57

2007-12-28 Thread Guido Guenther
On Thu, Dec 27, 2007 at 12:34:58PM +0200, Avi Kivity wrote: > Looks like memory corruption; this was a call through a function pointer > that pointed into userspace. > > Please try kvm-58, that has a fix for preemption notifiers on AMD; this may > solve the problem. kvm-58 doesn't show this probl

Re: [kvm-devel] Oops on 2.6.23.11 with KVM 57

2007-12-28 Thread Izik Eidus
Guido Guenther wrote: > On Thu, Dec 27, 2007 at 12:34:58PM +0200, Avi Kivity wrote: > >> Looks like memory corruption; this was a call through a function pointer >> that pointed into userspace. >> >> Please try kvm-58, that has a fix for preemption notifiers on AMD; this may >> solve the probl

Re: [kvm-devel] Oops on 2.6.23.11 with KVM 57

2007-12-28 Thread Yves Dorfsman
On Fri, 28 Dec 2007, Guido Guenther wrote: > I'm still seeing network stalls on large transfers in the guest though. > Ifup/ifdown'ing the interface in the guest gets things going again until > it stops again. There's nothing in dmesg of either host or guest. I still > have to check with differen