Bug 435164

Summary: qemu-dm redirects all stderr to /var/log/xen/qemu-dm-DOMID.log preventing libvirt seeing logs via Xenner
Product: [Fedora] Fedora Reporter: Daniel Berrangé <berrange>
Component: xenAssignee: Daniel Berrangé <berrange>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: xen-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-27 20:50:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 435137    
Bug Blocks: 435059    
Attachments:
Description Flags
Let XenD setup qemu logfiles none

Description Daniel Berrangé 2008-02-27 18:30:25 UTC 
Description of problem:
The Xen qemu-dm process re-opens stderr and directs it to a logfile
/var/log/xen/qemu-dm-DOMID.log.

When libvirtd spawns QEMU guests though it expects to be able to capture
messages on stderr, and send them to its own logfile
/var/log/libvirt/qemu/{DOMNAME}.log

So, since Xen is capturing stderr already, when you launch qemu-dm via Xenner we
never get any log messages fed back to libvirt's logfile.

Xen's should qemu-dm should simply not capture the stderr. This functionality
should be moved into XenD itself, allowing calls of qemu-dm to deal with logs as
they see fit.

Version-Release number of selected component (if applicable):
xen-3.2.0

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Daniel Berrangé 2008-02-27 20:35:06 UTC 
Created attachment 296115 [details]
Let XenD setup qemu logfiles
Comment 2 Daniel Berrangé 2008-02-27 20:50:59 UTC 
Fix built into rawhide xen-3.2.0-9.fc9