Bug 1112280
| Summary: | windows server 2012 guest w/ 256GB memory always be killed only when numad is enabled on host(w/ 512GB memory) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Kurik <jkurik> |
| Component: | numad | Assignee: | Jan Synacek <jsynacek> |
| Status: | CLOSED ERRATA | QA Contact: | Jakub Prokes <jprokes> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.4 | CC: | acathrow, andebjor, areis, bcao, bgray, bsarathy, cpelland, ddumas, drjones, jherrman, jprokes, jsynacek, juzhang, leiwang, lijin, lnovich, michen, mkenneth, nobody, perfbz, pm-eus, psklenar, qe-baseos-daemons, qzhang, sradvan, ttracy, virt-maint, xfu |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | 872524 | Environment: | |
| Last Closed: | 2014-08-05 10:39:00 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 872524 | ||
| Bug Blocks: | |||
|
Description
Jan Kurik
2014-06-23 13:28:01 UTC
Note the recent numad changes should get some test time in the official 6.6 environment before going out in 6.5z. Thanks! 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. http://rhn.redhat.com/errata/RHBA-2014-1005.html Clearing need info flag as this BZ has been closed |