qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerhard Wiesinger <lists@wiesinger.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Kernel Panic on Yum update
Date: Fri, 15 May 2015 16:31:59 +0200	[thread overview]
Message-ID: <5556035F.8020403@wiesinger.com> (raw)
In-Reply-To: <5555AA09.3090709@redhat.com>

On 15.05.2015 10:10, Paolo Bonzini wrote:
>
> On 15/05/2015 09:37, Gerhard Wiesinger wrote:
>> Yes, yum takes memory. But there is ~2.2 GB virt memory available. That
>> should be enough. Therefore I think it is a kernel problem. As in
>> previous crashes on the mailing list there is a lot of swap available
>> (2GB) which isn't touched in ANY way.
>>
>> Under normal conditions without yum:
>> free
>>                total        used        free      shared buff/cache
>> available
>> Mem:         243036      132540       12716       15520 97780       74964
>> Swap:       2064380           0     2064380
> Not all memory is the same.  Some memory cannot be swapped, and some
> memory can be swapped to disk without a swap file (e.g. executables).

Yes, I know the different memory types (pageable, non pageable, etc.).

> Failing an order 0 allocation is weird indeed, but this is a GFP_ATOMIC
> allocation so it's a bit less weird.

Nevertheless the kernel should never go out of non pageable memory if a 
USER process requires memory (which is of course pageable).

Ciao,
Gerhard

      reply	other threads:[~2015-05-15 14:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  6:34 [Qemu-devel] Kernel Panic on Yum update Gerhard Wiesinger
2015-05-15  6:51 ` Paolo Bonzini
2015-05-15  7:37   ` Gerhard Wiesinger
2015-05-15  8:10     ` Paolo Bonzini
2015-05-15 14:31       ` Gerhard Wiesinger [this message]

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=5556035F.8020403@wiesinger.com \
    --to=lists@wiesinger.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 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).