summary refs log tree commit diff stats
path: root/results/scraper/launchpad-without-comments/1599214
diff options
context:
space:
mode:
Diffstat (limited to 'results/scraper/launchpad-without-comments/1599214')
-rw-r--r--results/scraper/launchpad-without-comments/159921422
1 files changed, 22 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/1599214 b/results/scraper/launchpad-without-comments/1599214
new file mode 100644
index 000000000..eab191134
--- /dev/null
+++ b/results/scraper/launchpad-without-comments/1599214
@@ -0,0 +1,22 @@
+virtlogd: qemu 2.6.0 doesn't log boot message
+
+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:
+[1] https://bugs.launchpad.net/nova/+bug/1597789
+[2] http://git.qemu.org/?p=qemu.git;a=blobdiff;f=qemu-char.c;h=11caa5648de99c9e0ee158f280fbc02ab05915d3;hp=d7be1851e5e9d268aa924a05958da292b048839c;hb=d0d7708ba29cbcc343364a46bff981e0ff88366f;hpb=f1c17521e79df863a5771d96974fab0d07f02be0
\ No newline at end of file