All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: David Brown <dmlb2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: kernel page request failure
Date: Thu, 09 Aug 2007 17:49:04 +0300	[thread overview]
Message-ID: <46BB2960.3040201@qumranet.com> (raw)
In-Reply-To: <9c21eeae0708061020i3aea7489ia2964eca04b144fc-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

David Brown wrote:
> On 8/5/07, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
>   
>> David Brown wrote:
>>     
>>> I was running a guest os using kvm and I got this kernel page request
>>> failure using kvm 33 and 2.6.22.1 host.
>>>
>>>
>>>       
>> Is this 2.6.22.1's modules (i.e. --with-patched-kernel) or kvm-33's modules?
>>     
>
> This is built with kvm-33 modules.
>
>   
>> What guest are you running?
>>     
>
> Also the same crazy sourced based distro (Source Mage).
>
> I don't remember what it was trying to rebuild I think it might have
> been gcc. The guest has 1G ram and 1G swap. Also I found that the
> guest (if there isn't any swap available) will die if all the memory
> fills up. kvm had issues when that happened and it didn't release any
> of the memory back to the host when the guest died and the process was
> killed. I'm not sure if this had something to do with it or not gcc
> does tend to generate some huge DFA's when it compiles and could have
> filled up 2G with of memory and swap...  I wasn't paying attention
> enough to notice if that was the case...
>
>   

Is this the same issue or a different issue?  Did the oops happen when 
the host was loaded?

Please try to characterize one issue at a time, completely.



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

  parent reply	other threads:[~2007-08-09 14:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05 23:23 kernel page request failure David Brown
     [not found] ` <9c21eeae0708051623r31ae0e06hfdaff4f4f491b37c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-06  6:12   ` Avi Kivity
     [not found]     ` <46B6BBCC.2080201-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-06 17:20       ` David Brown
     [not found]         ` <9c21eeae0708061020i3aea7489ia2964eca04b144fc-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-09 14:49           ` Avi Kivity [this message]
     [not found]             ` <46BB2960.3040201-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-09 21:23               ` David Brown
     [not found]                 ` <9c21eeae0708091423u106efeacy34e8814de55f5418-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-09 21:30                   ` Avi Kivity
     [not found]                     ` <46BB8758.6090700-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-10  4:25                       ` David Brown

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=46BB2960.3040201@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=dmlb2000-Re5JQEeQqe8AvxtiuMwx3w@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.