Bug 817236
Summary: | Regression since 2.6.32-266.el6 AMD host writes 150+ GB dmesg logs | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Xiaoqing Wei <xwei> |
Component: | kernel | Assignee: | Marcelo Tosatti <mtosatti> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.3 | CC: | atodorov, juzhang, knoel, michen, qzhang, shuang, sluo, tburke, yunzheng |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | kernel-2.6.32-270.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-20 14:00:03 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Xiaoqing Wei
2012-04-28 07:49:21 UTC
this probably introduced by the fix of Bug 807215 - after host S4 the guest can not work normally Patch(es) available on kernel-2.6.32-270.el6 *** Bug 821365 has been marked as a duplicate of this bug. *** Reproduced on kernel-2.6.32-268.el6 and verified pass on kernel-2.6.32-270.el6. Steps: 1. Boot a guest on host. 2. On host: # du -hs /var/log/messages 3. Repeat step 2. on kernel-2.6.32-268.el6, after step 3: The file size on step 2 keep increasing and there's lots of Call Trace in the dmesg of guest. on kernel-2.6.32-270.el6, after step 3: [root@intel-q9400-8-1 ~]# du -hs /var/log/messages 116K /var/log/messages And this bug is reproduced only on an AMD host, and verified passed on both Intel and AMD host with RHEL6.3 and winxp guests. So, this bug is fixed, setting to VERIFIED. 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/RHSA-2012-0862.html |