Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionAndrea 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.
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.
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
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
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.