All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 51301] New: [-next-20121129] memory leak/page allocator fragmentation?
Date: Tue,  4 Dec 2012 16:08:46 +0000 (UTC)	[thread overview]
Message-ID: <bug-51301-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=51301

           Summary: [-next-20121129] memory leak/page allocator
                    fragmentation?
           Product: Virtualization
           Version: unspecified
    Kernel Version: -next-20121129
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
        AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
        ReportedBy: peter@hurleysoftware.com
        Regression: No


With a single 2Gb/4-core VM on a 10Gb/8-core host, the _host_ ran out of 32kb
page blocks. I can't be certain that it was kvm because the OOM condition
triggered a GP fault in the SLUB allocator. (The other suspect is nouveau.)

I have attached the kernel log and a SysRq Show Memory dump of the machine
shortly after boot without running kvm.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

             reply	other threads:[~2012-12-04 16:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 16:08 bugzilla-daemon [this message]
2012-12-04 16:09 ` [Bug 51301] [-next-20121129] memory leak/page allocator fragmentation? bugzilla-daemon
2012-12-04 16:11 ` bugzilla-daemon
2012-12-04 16:23 ` bugzilla-daemon
2012-12-04 16:48 ` bugzilla-daemon
2012-12-04 21:42 ` bugzilla-daemon
2012-12-04 21:53 ` bugzilla-daemon

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=bug-51301-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.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.