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: