Bug 1112280 - windows server 2012 guest w/ 256GB memory always be killed only when numad is enabled on host(w/ 512GB memory) [NEEDINFO]
Summary: windows server 2012 guest w/ 256GB memory always be killed only when numad is...
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: numad
Version: 6.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: Jakub Prokes
Depends On: 872524
TreeView+ depends on / blocked
Reported: 2014-06-23 13:28 UTC by Jan Kurik
Modified: 2014-08-05 10:39 UTC (History)
28 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, running the numad daemon on a system executing a process with very large resident memory (such as a Windows Server 2012 guest) could cause memory swapping. As a consequence, significant latencies under some circumstances occurred on the system, which could in turn lead to other processes (such as qemu-kvm) becoming unresponsive. With this update, numad no longer causes memory swapping in the above scenario, and the consequent latencies and hangs no longer occur.
Clone Of: 872524
Last Closed: 2014-08-05 10:39:00 UTC
jprokes: needinfo? (ttracy)

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1005 normal SHIPPED_LIVE numad bug fix update 2014-08-05 14:38:47 UTC

Description Jan Kurik 2014-06-23 13:28:01 UTC
This bug has been copied from bug #872524 and has been proposed
to be backported to 6.5 z-stream (EUS).

Comment 3 Bill Gray 2014-06-23 20:25:14 UTC
Note the recent numad changes should get some test time in the official 6.6 environment before going out in 6.5z.  Thanks!

Comment 9 errata-xmlrpc 2014-08-05 10:39:00 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.