*** This bug is a duplicate of bug 1599214 ***
https://bugs.launchpad.net/bugs/1599214
Marked as duplicate. The issue was in qemu and got fixed with v2.7.0.
Also, Nova doesn't yet have a dependency to virtlogd. This is still
under development with https://review.openstack.org/#/c/323765/
** This bug has been marked a duplicate of bug 1599214
virtlogd: qemu 2.6.0 doesn't log boot message
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1597789
Title:
libvirt: virtlogd: qemu 2.6.0 doesn't log boot message
Status in OpenStack Compute (nova):
Confirmed
Bug description:
Description
===========
With libvirt 1.3.3 and Qemu 2.6.0 char devices are able to log their
stdout/stderr into a log file via a "<log>" XML element in the domain XML.
This feature solves the long standing bug 832507 (which can flood the log)
by a built-in log rotation. It also removes the mutually exclusivity of
"serial console" and "get console output".
Unfortunately, an (assumed) issue in Qemu prevents the logging of the
boot messages of the guest *unless* the connection to the char device is
already established.
Steps to reproduce
==================
A chronological list of steps which will bring off the
issue you noticed:
* Ensure to have the code of https://review.openstack.org/#/c/323765/14
applied
* Ensure to have libvirt 1.3.3 and qemu 2.6.0
* Launch an instance
* execute: nova console-log <server>
Expected result
===============
The CLI returns the boot messages.
Actual result
=============
The result is an empty string.
If I connect to the used console (via Horizon for example), execute
"echo 'foo'" and things like that, the next call of "nova console-log
<server>" *does* return those executed commands (but still not the
boot messages). If I reboot withing the console, *then* the boot
messages will be logged too.
Environment
===========
1. OpenStack version: master (Newton)
$ git log --oneline -4
201e231 libvirt: virtlogd: use virtlogd for char devices
73e931a libvirt: simplify "get_console_output" interface
ec94d7b libvirt: fix live-migration with serial console check
fcb3dbf Merge "Fix error message for VirtualInterfaceUnplugException"
2. Which hypervisor did you use?
libvirt 1.3.3 and kvm-qemu 2.6.0
2. Which storage type did you use?
(For example: Ceph, LVM, GPFS, ...)
What's the version of that?
3. Which networking type did you use?
neutron + ovs
Logs & Configs
==============
N/A
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1597789/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
