Bugs item #1831825, was opened at 2007-11-14 17:08 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1831825&group_id=180599
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Technologov (technologov) Assigned to: Nobody/Anonymous (nobody) Summary: [Feature Request] KVM should have log files Initial Comment: Currently the only way to debug KVM is via kernel log files, such as: netconsole,dmesg,/var/log/messages It would be much easier to debug KVM if he had better logging of what user does wrong. The log file must include date/time, KVM userspace & KVM kernelspace versions, host kernel & arch, host CPU (especially VT-related abilities), RAM, kernel messages, and the user command passed to Qemu/KVM. This will allow KVM developers to better understand & analyze KVM problems, even when reported by third-party. -Alexey. 14.11.2007. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1831825&group_id=180599 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
