[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot mes
From: |
Daniel Berrange |
Subject: |
[Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message |
Date: |
Wed, 27 Jul 2016 15:58:49 -0000 |
Ok, so the problem is a difference in behaviour for virtio-console vs
serial ports.
For plain x86 serial ports, if there's no client connected to the
backend, any data is just discarded.
For virtio-console, if there's no client connected to the backend, it'll
refuse to send data, hence we never get to log it either.
What i'm not sure on is whether this is supposed to work this way. The
virtio-console device actually provides two separate services - a
paravirt serial port and a paravirt interactive console. The paravirt
serial port mode, certainly requires this behaviour, but I'm not
convinced the console mode should do this.
--
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
- [Qemu-devel] [Bug 1599214] [NEW] virtlogd: qemu 2.6.0 doesn't log boot message, Markus Zoeller \(markus_z\), 2016/07/05
- [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message, Daniel Berrange, 2016/07/05
- [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message, Markus Zoeller \(markus_z\), 2016/07/05
- [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message, Daniel Berrange, 2016/07/26
- [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message, Markus Zoeller \(markus_z\), 2016/07/27
- [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message, Daniel Berrange, 2016/07/27
- [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message, Markus Zoeller \(markus_z\), 2016/07/27
- [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message, Markus Zoeller \(markus_z\), 2016/07/27
- [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message,
Daniel Berrange <=
- [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message, Daniel Berrange, 2016/07/29