virtlogd: qemu 2.6.0 doesn't log boot message
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Fix Released
|
Undecided
|
Daniel Berrange |
Bug Description
This report is related to the OpenStack Nova bug [1].
OpenStack tries to utilize the "virtlogd" feature of libvirt which gets provided by qemu with [2].
steps to reproduce:
1) launch a quest with qemu 2.6.0 which uses virtlogd for the stdout/stderr of its char device
2) check the contents of the backing file of that char device
expected result:
The boot messages of the guest are logged in this file
actual result:
The file is empty
notes:
When I'm connected to that char device and reboot the guest, I see the boot messages in the terminal and also in the backing log file.
References:
[1] https:/
[2] http://
Changed in qemu: | |
assignee: | nobody → Daniel Berrange (berrange) |
description: | updated |
Can you provide the full QEMU command line arguments you're using to reproduce this problem. I tested a guest with the following console config:
<serial type='unix'> var/lib/ libvirt/ qemu/f25- console. sock'/> var/lib/ libvirt/ qemu/f25- console. log'/>
<source mode='bind' path='/
<log file='/
<target port='1'/>
<alias name='serial1'/>
</serial>
and confirmed that the log file gets written, even when no client is connected to the UNIX domain socket.