Bug 469337 - [Chapter 29.2] libvirt directories are missing
Summary: [Chapter 29.2] libvirt directories are missing
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: doc-Virtualization_Guide
Version: 5.3
Hardware: All
OS: Linux
medium
low
Target Milestone: rc
: ---
Assignee: Christopher Curran
QA Contact: Lawrence Lim
URL:
Whiteboard:
Depends On:
Blocks: 449674
TreeView+ depends on / blocked
 
Reported: 2008-10-31 11:30 UTC by Kazuo Moriwaka
Modified: 2014-03-26 00:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-27 04:54:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Kazuo Moriwaka 2008-10-31 11:30:32 UTC
Description of problem:


29.2 describes xen directories and logs only.

/etc/libvirt  -- libvirt configuration top dir.
/etc/libvirt/qemu/networks/ -- libvirtd network settings dir.
/var/log/messages -- libvirtd messages in it.

Comment 1 Christopher Curran 2009-06-29 04:36:47 UTC
Hugh,

Are there other log files and directories which should be included for libvirt and KVM?


The location has changed too, the section from the bug is now here:
http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Virtualization/sect-Virtualization-Troubleshooting_Red_Hat_Virtualization-Log_files_overview.html

Comment 2 Kazuo Moriwaka 2009-07-03 05:15:57 UTC
I found /var/log/libvirt/qemu/ contains logs of qemu for each VM in F11.

regards,

Comment 3 Christopher Curran 2009-10-07 01:25:20 UTC
I've tested this. Adding it in.

Comment 4 Michael Hideo 2009-12-14 01:38:04 UTC
Hi Chris,

Need a pointer for this

Comment 5 Christopher Curran 2009-12-14 07:04:11 UTC
The files in /etc/libvirt are not recommended for editing. Almost every part of those files can be modified with virsh so we should not cover that directory.

/var/log/libvirt/qemu/ and /var/log/messages are covered better in build 81.

Chris


Note You need to log in before you can comment on or make changes to this bug.