kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Thomas Treutner <thomas@scripty.at>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: 2.6.38.1 general protection fault
Date: Wed, 20 Apr 2011 12:54:33 +0200	[thread overview]
Message-ID: <4DAEBB69.4010604@wpkg.org> (raw)
In-Reply-To: <4DAEA72A.9080102@scripty.at>

On 20.04.2011 11:28, Thomas Treutner wrote:
> On 03/28/2011 10:14 PM, Tomasz Chmielewski wrote:
>> On 28.03.2011 22:04, Andrea Arcangeli wrote:
>>
>>> Tomasz, how easily can you reproduce?
>>
>> Well, this server runs 10 VMs or so, and it happens after 1-2 days of
>> uptime.
>>
>> I reverted now to a 2.6.35.x, as it had enough downtime with 2.6.38
>> already ;) so I'd rather not experiment anymore for some time with a
>> kernel known to cause problems.
>
> Tomasz, to which exact kernel version (host+guests) did you switch and
> is it now stable?

I've switched the host to the latest 2.6.35.x and it's stable.

Guest kernel doesn't seem to make a difference here, but majority of 
them are running 2.6.38.x kernel (had some weird issues with "events/0", 
taking 100% CPU on guests when I used 2.6.35, which made the guests 
crawling slow).


-- 
Tomasz Chmielewski
http://wpkg.org

  reply	other threads:[~2011-04-20 10:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25  9:32 2.6.38.1 general protection fault Tomasz Chmielewski
2011-03-26  9:15 ` Avi Kivity
2011-03-26 10:42   ` Tomasz Chmielewski
2011-03-27  9:42     ` Avi Kivity
2011-03-28  6:24       ` Tomasz Chmielewski
2011-03-28  9:19         ` Avi Kivity
2011-03-28 17:54           ` Andrea Arcangeli
2011-03-28 18:02             ` Avi Kivity
2011-03-28 20:04               ` Andrea Arcangeli
2011-03-28 20:14                 ` Tomasz Chmielewski
2011-04-20  9:28                   ` Thomas Treutner
2011-04-20 10:54                     ` Tomasz Chmielewski [this message]
2011-03-29 13:34           ` Marcelo Tosatti

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=4DAEBB69.4010604@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=kvm@vger.kernel.org \
    --cc=thomas@scripty.at \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).