Description of problem:
In order to have kernel oopsen, panics and other console output logged, to help
with the analysis of why a virtual machine got into trouble, it would be
extremely useful if Xen could log the paravirt console output to a file.
The best way is probably to have one file per virtual machine, with automatic
log rotating like ttywatch does...
This is a big issue, and should probably be fixed before RHEL5 GA goes out.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Created attachment 155846 [details]
Patch against 3.1.0 to add logging of guest & hv
NB. this patch will require some small work to backport to xen 3.1.0. We will
also need to play with initscripts to provide a way to start the xenconsoled
with logging arguments on its command line.
Patch is now upstream
Created attachment 156582 [details]
Add persistent logging of guest consoles
Build xen-3.0.3-29.el5 built into dist-5E-qu-candidate now has support for
persistent logging of guest consoles. It is not enabled by default. To test try
1. Edit /etc/sysconfig/xend and XENCONSOLED_LOG_GUESTS=yes
3. Start a guest
4. Look at /var/log/xen/console/guest-[name].log
The guest-[name].log file should contain all data you'd otherwise see on 'virsh
console [name]'. The data should be logged even if you are connected via the
change QA contact
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.