This report is related to the OpenStack Nova bug [1].
OpenStack tries to utilize the "virtlogd" feature of qemu [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.
This report is related to the OpenStack Nova bug [1].
OpenStack tries to utilize the "virtlogd" feature of qemu [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: /bugs.launchpad .net/nova/ +bug/1597789 git.qemu. org/?p= qemu.git; a=blobdiff; f=qemu- char.c; h=11caa5648de99 c9e0ee158f280fb c02ab05915d3; hp=d7be1851e5e9 d268aa924a05958 da292b048839c; hb=d0d7708ba29c bcc343364a46bff 981e0ff88366f; hpb=f1c17521e79 df863a5771d9697 4fab0d07f02be0
[1] https:/
[2] http://