Bug 1435681

Summary: <console><log> doesn't work on aarch64
Product: Red Hat Enterprise Linux 7 Reporter: Andrea Bolognani <abologna>
Component: libvirtAssignee: Andrea Bolognani <abologna>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: crobinso, drjones, dzheng, gsun, jcm, jsuchane, rbalakri
Target Milestone: rc   
Target Release: ---   
Hardware: aarch64   
OS: Linux   
Whiteboard:
Fixed In Version: libvirt-3.2.0-16.el7a Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1456882 (view as bug list) Environment:
Last Closed: 2017-11-09 11:26:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1456882    
Bug Blocks: 1173757    

Description Andrea Bolognani 2017-03-24 14:10:14 UTC
Configuring a guest with

  <console type='pty'>
    <log file='...'/>
  </console>

fails on aarch64 with

  error: unsupported configuration: logfile not supported
         in this QEMU binary

The underlying issue is that, unlike what happens for x86
and ppc64, the guest-side serial console (pl011) is
instantiated implicitly, even when -nodefaults is used, so
libvirt doesn't have a way to assign it a chardev with the
logfile property configured.

Comment 2 Andrea Bolognani 2017-03-24 14:35:02 UTC
A way to work around the issue is to use the VirtIO-based
console instead:

  <console type='pty'>
    <log file='...'/>
    <target type='virtio'/>
  </console>

However, that has its own drawbacks, such as not being able
to access early boot or even the bootloader.

Comment 3 Andrea Bolognani 2017-06-27 05:33:26 UTC
Cole just posted some patches for this upstream:

  https://www.redhat.com/archives/libvir-list/2017-June/msg01128.html

Comment 4 Andrea Bolognani 2017-07-11 06:47:39 UTC
The fix has now been merged upstream.

commit 426dc5eb28bade109bf27bdd10d7305a040b4a3e
Author: Cole Robinson <crobinso>
Date:   Mon Jun 26 14:01:52 2017 -0400

    qemu: command: support -chardev for platform devices
    
    Some qemu arch/machine types have built in platform devices that
    are always implicitly available. For platform serial devices, the
    current code assumes that only old style -serial config can be
    used for these devices.
    
    Apparently though since -chardev was introduced, we can use -chardev
    in these cases, like this:
    
      -chardev pty,id=foo
      -serial chardev:foo
    
    Since -chardev enables all sorts of modern features, use this method
    for platform devices.
    
    Reviewed-by: Andrea Bolognani <abologna>
    Signed-off-by: Cole Robinson <crobinso>

v3.5.0-28-g426dc5e

Comment 7 Andrea Bolognani 2017-08-08 13:10:04 UTC
I have confirmed the issue has indeed been addressed.

Please move this bug to VERIFIED.

Comment 8 Dan Zheng 2017-08-23 07:38:35 UTC
Regarding comment 7,  we verify it now.

Comment 10 errata-xmlrpc 2017-11-09 11:26:03 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3174