Fix in 2.7.0 release thanks to
commit bce6261eb2d879625126485d4ddd28cacb93152e
Author: Daniel P. Berrange
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 c
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 Q
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 g
The char device in the libvirt domain XML is this:
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:
vi
> 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 does
Ok, relevant part of command line is
-add-fd set=2,fd=33
-chardev
socket,id=charconsole0,host=9.152.151.129,port=1,server,nowait,logfile=/dev/fdset/2,logappend=on
-device virtconsole,chardev=charconsole0,id=console0
-chardev pty,id=charconsole1
-device sclpconsole,chardev=charconsole1,id=cons
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 lo
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:
and confirmed that the log file gets written, even when no client is
connected to the UNIX domain socket.
** Chan
** 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 wi
** 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 Q
10 matches
Mail list logo
