From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48610) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bKSmO-0000Qo-83 for qemu-devel@nongnu.org; Tue, 05 Jul 2016 12:00:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bKSmK-0003fs-4P for qemu-devel@nongnu.org; Tue, 05 Jul 2016 12:00:55 -0400 Received: from indium.canonical.com ([91.189.90.7]:54861) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bKSmJ-0003fc-Tv for qemu-devel@nongnu.org; Tue, 05 Jul 2016 12:00:52 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.76 #1 (Debian)) id 1bKSmJ-0005eZ-BI for ; Tue, 05 Jul 2016 16:00:51 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id C78452E80CC for ; Tue, 5 Jul 2016 16:00:49 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Tue, 05 Jul 2016 15:54:16 -0000 From: "Markus Zoeller \(markus_z\)" Reply-To: Bug 1599214 <1599214@bugs.launchpad.net> Sender: bounces@canonical.com References: <20160705154632.23878.8490.malonedeb@gac.canonical.com> Message-Id: <20160705155416.23182.1540.launchpad@gac.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ** 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/stde= rr 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 bo= ot 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=3Dqemu.git;a=3Dblobdiff;f=3Dqemu-char.c;h=3D11= caa5648de99c9e0ee158f280fbc02ab05915d3;hp=3Dd7be1851e5e9d268aa924a05958da29= 2b048839c;hb=3Dd0d7708ba29cbcc343364a46bff981e0ff88366f;hpb=3Df1c17521e79df= 863a5771d96974fab0d07f02be0 -- = 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/stde= rr 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 bo= ot 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=3Dqemu.git;a=3Dblobdiff;f=3Dqemu-char.c;h=3D11= caa5648de99c9e0ee158f280fbc02ab05915d3;hp=3Dd7be1851e5e9d268aa924a05958da29= 2b048839c;hb=3Dd0d7708ba29cbcc343364a46bff981e0ff88366f;hpb=3Df1c17521e79df= 863a5771d96974fab0d07f02be0 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1599214/+subscriptions