[Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message

[Daniel Berrange <1599214@bugs.launchpad.net>]

Ok, relevant part of command line is

-add-fd set=2,fd=33
-chardev socket,id=charconsole0,host=9.152.151.129,port=10000,server,nowait,logfile=/dev/fdset/2,logappend=on
-device virtconsole,chardev=charconsole0,id=console0
-chardev pty,id=charconsole1
-device sclpconsole,chardev=charconsole1,id=console1


Which shows a TCP based serial console with log file

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1599214

Title:
  virtlogd: qemu 2.6.0 doesn't log boot message

Status in QEMU:
  New

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://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

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1599214/+subscriptions