Bug 819284
Summary: | RHEL5 Xen: hypervisor conring_size too small when loglevel=all, missing logs | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Pasi Karkkainen <pasik> |
Component: | xen | Assignee: | Xen Maintainance List <xen-maint> |
Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.8 | CC: | drjones, leiwang, lersek, moli, qguan, qwan, xen-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-09 06:52:54 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
Pasi Karkkainen
2012-05-06 09:29:06 UTC
Generally whenever we want to do anything with the Xen dmesg, we capture it over the serial console (sometimes with "sync_console" on the hv command line), and ask customers to do the same, since that's the only "sure" way to save it (if there are boot problems eg.) If you redirect the messages to "/var/log/xen/console/hypervisor.log" with setting XENCONSOLED_LOG_HYPERVISOR=yes in "/etc/sysconfig/xend", does the truncation still occur? (I would guess so; by the time xend starts in the boot process we must have lost the first messages.) On the surface this seems to be an easy convenience backport, but a quick hg blame + grep identified the following patches: http://xenbits.xensource.com/hg/xen-unstable.hg/rev/19543 http://xenbits.xensource.com/hg/xen-unstable.hg/rev/20130 http://xenbits.xensource.com/hg/xen-unstable.hg/rev/20133 http://xenbits.xensource.com/hg/xen-unstable.hg/rev/20374 http://xenbits.xensource.com/hg/xen-unstable.hg/rev/21038 http://xenbits.xensource.com/hg/xen-unstable.hg/rev/21225 These patches appear a bit turbulent for functionality I'd expect to be "simple" and "convenience". Xen team, thoughts? I thought about doubling the ring size in the HV once because it appears that the tools already support 32k. However, we dropped the idea since the benefit wasn't worth the risk. As Laszlo said, we can already capture all logs by using serial. I'm closing this as WONTFIX. It's too late in RHEL5's lifecycle to churn much code for minimal feature gain. |