* [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message
2016-07-05 15:46 [Qemu-devel] [Bug 1599214] [NEW] virtlogd: qemu 2.6.0 doesn't log boot message Markus Zoeller (markus_z)
@ 2016-07-05 15:51 ` Daniel Berrange
2016-07-05 15:54 ` Markus Zoeller (markus_z)
` (8 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Daniel Berrange @ 2016-07-05 15:51 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu
Assignee: (unassigned) => Daniel Berrange (berrange)
--
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message
2016-07-05 15:46 [Qemu-devel] [Bug 1599214] [NEW] virtlogd: qemu 2.6.0 doesn't log boot message Markus Zoeller (markus_z)
2016-07-05 15:51 ` [Qemu-devel] [Bug 1599214] " Daniel Berrange
@ 2016-07-05 15:54 ` Markus Zoeller (markus_z)
2016-07-26 16:13 ` Daniel Berrange
` (7 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Markus Zoeller (markus_z) @ 2016-07-05 15:54 UTC (permalink / raw)
To: qemu-devel
** Description changed:
This report is related to the OpenStack Nova bug [1].
- OpenStack tries to utilize the "virtlogd" feature of qemu [2].
+ 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
--
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message
2016-07-05 15:46 [Qemu-devel] [Bug 1599214] [NEW] virtlogd: qemu 2.6.0 doesn't log boot message Markus Zoeller (markus_z)
2016-07-05 15:51 ` [Qemu-devel] [Bug 1599214] " Daniel Berrange
2016-07-05 15:54 ` Markus Zoeller (markus_z)
@ 2016-07-26 16:13 ` Daniel Berrange
2016-07-27 12:47 ` Markus Zoeller (markus_z)
` (6 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Daniel Berrange @ 2016-07-26 16:13 UTC (permalink / raw)
To: qemu-devel
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'>
<source mode='bind' path='/var/lib/libvirt/qemu/f25-console.sock'/>
<log file='/var/lib/libvirt/qemu/f25-console.log'/>
<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.
** Changed in: qemu
Status: New => Incomplete
--
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:
Incomplete
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message
2016-07-05 15:46 [Qemu-devel] [Bug 1599214] [NEW] virtlogd: qemu 2.6.0 doesn't log boot message Markus Zoeller (markus_z)
` (2 preceding siblings ...)
2016-07-26 16:13 ` Daniel Berrange
@ 2016-07-27 12:47 ` Markus Zoeller (markus_z)
2016-07-27 12:59 ` Daniel Berrange
` (5 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Markus Zoeller (markus_z) @ 2016-07-27 12:47 UTC (permalink / raw)
To: qemu-devel
qemu log:
http://paste.openstack.org/show/542559/
** Changed in: qemu
Status: Incomplete => New
--
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message
2016-07-05 15:46 [Qemu-devel] [Bug 1599214] [NEW] virtlogd: qemu 2.6.0 doesn't log boot message Markus Zoeller (markus_z)
` (3 preceding siblings ...)
2016-07-27 12:47 ` Markus Zoeller (markus_z)
@ 2016-07-27 12:59 ` Daniel Berrange
2016-07-27 13:40 ` Markus Zoeller (markus_z)
` (4 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Daniel Berrange @ 2016-07-27 12:59 UTC (permalink / raw)
To: qemu-devel
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message
2016-07-05 15:46 [Qemu-devel] [Bug 1599214] [NEW] virtlogd: qemu 2.6.0 doesn't log boot message Markus Zoeller (markus_z)
` (4 preceding siblings ...)
2016-07-27 12:59 ` Daniel Berrange
@ 2016-07-27 13:40 ` Markus Zoeller (markus_z)
2016-07-27 14:17 ` Markus Zoeller (markus_z)
` (3 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Markus Zoeller (markus_z) @ 2016-07-27 13:40 UTC (permalink / raw)
To: qemu-devel
> Which shows a TCP based serial console with log file
Yes, that's true. It's also on the s390x architecture.
--
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message
2016-07-05 15:46 [Qemu-devel] [Bug 1599214] [NEW] virtlogd: qemu 2.6.0 doesn't log boot message Markus Zoeller (markus_z)
` (5 preceding siblings ...)
2016-07-27 13:40 ` Markus Zoeller (markus_z)
@ 2016-07-27 14:17 ` Markus Zoeller (markus_z)
2016-07-27 15:58 ` Daniel Berrange
` (2 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Markus Zoeller (markus_z) @ 2016-07-27 14:17 UTC (permalink / raw)
To: qemu-devel
The char device in the libvirt domain XML is this:
<console type="tcp">
<source host="9.152.151.133" mode="bind" service="10000"/>
<log file="/opt/stack/data/nova/instances/40fd2986-69f3-4db5-a17f-fd9ef1c69350/console.log" append="off"/>
</console>
Full domain XML: http://paste.openstack.org/show/542597/
--
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message
2016-07-05 15:46 [Qemu-devel] [Bug 1599214] [NEW] virtlogd: qemu 2.6.0 doesn't log boot message Markus Zoeller (markus_z)
` (6 preceding siblings ...)
2016-07-27 14:17 ` Markus Zoeller (markus_z)
@ 2016-07-27 15:58 ` Daniel Berrange
2016-07-29 12:03 ` Daniel Berrange
2016-09-14 14:54 ` Daniel Berrange
9 siblings, 0 replies; 11+ messages in thread
From: Daniel Berrange @ 2016-07-27 15:58 UTC (permalink / raw)
To: qemu-devel
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message
2016-07-05 15:46 [Qemu-devel] [Bug 1599214] [NEW] virtlogd: qemu 2.6.0 doesn't log boot message Markus Zoeller (markus_z)
` (7 preceding siblings ...)
2016-07-27 15:58 ` Daniel Berrange
@ 2016-07-29 12:03 ` Daniel Berrange
2016-09-14 14:54 ` Daniel Berrange
9 siblings, 0 replies; 11+ messages in thread
From: Daniel Berrange @ 2016-07-29 12:03 UTC (permalink / raw)
To: qemu-devel
Patch at https://lists.gnu.org/archive/html/qemu-
devel/2016-07/msg06708.html
--
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message
2016-07-05 15:46 [Qemu-devel] [Bug 1599214] [NEW] virtlogd: qemu 2.6.0 doesn't log boot message Markus Zoeller (markus_z)
` (8 preceding siblings ...)
2016-07-29 12:03 ` Daniel Berrange
@ 2016-09-14 14:54 ` Daniel Berrange
9 siblings, 0 replies; 11+ messages in thread
From: Daniel Berrange @ 2016-09-14 14:54 UTC (permalink / raw)
To: qemu-devel
Fix in 2.7.0 release thanks to
commit bce6261eb2d879625126485d4ddd28cacb93152e
Author: Daniel P. Berrange <berrange@redhat.com>
Date: Wed Aug 3 17:22:36 2016 +0100
virtio-console: set frontend open permanently for console devs
The virtio-console.c file handles both serial consoles
and interactive consoles, since they're backed by the
same device model.
Since serial devices are expected to be reliable and
need to notify the guest when the backend is opened
or closed, the virtio-console.c file wires up support
for chardev events. This affects both serial consoles
and interactive consoles, using a network connection
based chardev backend such as 'socket', but not when
using a PTY based backend or plain 'file' backends.
When the host side is not connected the handle_output()
method in virtio-serial-bus.c will drop any data sent
by the guest, before it even reaches the virtio-console.c
code. This means that if the chardev has a logfile
configured, the data will never get logged.
Consider for example, configuring a x86_64 guest with a
plain UART serial port
-chardev socket,id=charserial1,host=127.0.0.1,port=9001,server,nowait,logfile=console1.log,logappend=on
-device isa-serial,chardev=charserial1,id=serial1
vs a s390 guest which has to use the virtio-console port
-chardev socket,id=charconsole1,host=127.0.0.1,port=9000,server,nowait,logfile=console2.log,logappend=on
-device virtconsole,chardev=charconsole1,id=console1
The isa-serial one gets data written to the log regardless
of whether a client is connected, while the virtioconsole
one only gets data written to the log when a client is
connected.
There is no need for virtio-serial-bus.c to aggressively
drop the data for console devices, as the chardev code is
prefectly capable of discarding the data itself.
So this patch changes virtconsole devices so that they
are always marked as having the host side open. This
ensures that the guest OS will always send any data it
has (Linux virtio-console hvc driver actually ignores
the host open state and sends data regardless, but we
should not rely on that), and also prevents the
virtio-serial-bus code prematurely discarding data.
The behaviour of virtserialport devices is *not* changed,
only virtconsole, because for the former, it is important
that the guest OSknow exactly when the host side is opened
/ closed so it can do any protocol re-negotiation that may
be required.
Fixes bug: https://bugs.launchpad.net/qemu/+bug/1599214
Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1470241360-3574-2-git-send-email-berrange@redhat.com>
Signed-off-by: Amit Shah <amit.shah@redhat.com>
** Changed in: qemu
Status: New => Fix Released
--
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:
Fix Released
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
^ permalink raw reply [flat|nested] 11+ messages in thread