From mboxrd@z Thu Jan 1 00:00:00 1970 From: Izik Eidus Subject: Re: Oops on 2.6.23.11 with KVM 57 Date: Fri, 28 Dec 2007 22:53:53 +0200 Message-ID: <47756261.4000104@qumranet.com> References: <20071221132611.GA11812@bogon.ms20.nix> <476D6CAF.2030009@qumranet.com> <20071227094136.GB824@bogon.ms20.nix> <47737FD2.1060802@qumranet.com> <20071228202510.GA2980@bogon.ms20.nix> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Avi Kivity To: Guido Guenther Return-path: In-Reply-To: <20071228202510.GA2980-DVvpyRRQz99DDGxTMhc9XQ@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org 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 problem. >> > kvm-58 doesn't show this problem, thanks! The host runs stable now. > > 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 different guest kernels and qemu network adapter > emulations though (current one is ne2k using a bridge on the host). The > > there are known problems with ne2k, please rtl8139 and report if it work ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/