All of lore.kernel.org
 help / color / mirror / Atom feed
From: Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Guido Guenther <agx-wGvLLbajjwFAfugRpC6u6w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Subject: Re: Oops on 2.6.23.11 with KVM 57
Date: Fri, 28 Dec 2007 22:53:53 +0200	[thread overview]
Message-ID: <47756261.4000104@qumranet.com> (raw)
In-Reply-To: <20071228202510.GA2980-DVvpyRRQz99DDGxTMhc9XQ@public.gmane.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/

  parent reply	other threads:[~2007-12-28 20:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 13:26 Oops on 2.6.23.11 with KVM 57 Guido Guenther
     [not found] ` <20071221132611.GA11812-DVvpyRRQz99DDGxTMhc9XQ@public.gmane.org>
2007-12-22 19:59   ` Avi Kivity
     [not found]     ` <476D6CAF.2030009-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-27  9:41       ` Guido Guenther
     [not found]         ` <20071227094136.GB824-DVvpyRRQz99DDGxTMhc9XQ@public.gmane.org>
2007-12-27 10:34           ` Avi Kivity
     [not found]             ` <47737FD2.1060802-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-28 20:25               ` Guido Guenther
     [not found]                 ` <20071228202510.GA2980-DVvpyRRQz99DDGxTMhc9XQ@public.gmane.org>
2007-12-28 20:53                   ` Izik Eidus [this message]
     [not found]                     ` <47756261.4000104-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-03  9:47                       ` [PATCH] use rtl8139 as default network adapter Guido Guenther
     [not found]                         ` <20080103094752.GA6778-DVvpyRRQz99DDGxTMhc9XQ@public.gmane.org>
2008-01-03 12:43                           ` Avi Kivity
2008-01-08 11:22                           ` [PATCH] use rtl8139 for bootp too and adjust docs accordingly Guido Guenther
     [not found]                             ` <20080108112255.GB6651-DVvpyRRQz99DDGxTMhc9XQ@public.gmane.org>
2008-01-08 13:51                               ` Avi Kivity
2007-12-28 22:43                   ` Oops on 2.6.23.11 with KVM 57 Yves Dorfsman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47756261.4000104@qumranet.com \
    --to=izike-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=agx-wGvLLbajjwFAfugRpC6u6w@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.