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.
DescriptionRichard W.M. Jones
2022-05-12 12:42:25 UTC
Description of problem:
In https://bugzilla.redhat.com/show_bug.cgi?id=2082806 we are
tracking an insidious qemu bug which intermittently prevents the
libguestfs appliance from starting. The symptoms are that SeaBIOS
starts and displays its messages, but the kernel isn't reached. We
found that the kernel does in fact start, but when it tries to set up
page tables and jump to protected mode it gets a triple fault which
causes the emulated CPU in qemu to reset (qemu exits).
This seems to only affect TCG (not KVM).
This is caused by using -cpu max which enables the "la57" feature
(5-level page tables[0]), and that we can make the problem go away
using -cpu max,la57=off.
Note this is only a workaround for bug 2082806. We may in future
fix that bug properly (in qemu). However the proposed workaround
for libguestfs should not have any negative effects.
This bug affects all versions of libguestfs that run qemu with
-cpu max or the libvirt equivalent <cpu mode="maximum"/>, which
includes RHEL 8.7 (not 8.6), and RHEL 9.0 and 9.1.
Version-Release number of selected component (if applicable):
libguestfs-1.44.0-6.el8
How reproducible:
100%
Steps to Reproduce:
These two commands test the libvirt and direct paths (which are
fixed separately):
while LIBGUESTFS_BACKEND_SETTINGS=force_tcg ./run libguestfs-test-tool >&/tmp/log ; do echo -n . ; done
while LIBGUESTFS_BACKEND=direct LIBGUESTFS_BACKEND_SETTINGS=force_tcg ./run libguestfs-test-tool >&/tmp/log ; do echo -n . ; done
Upstream bug fix:
https://listman.redhat.com/archives/libguestfs/2022-May/028853.html
Verified with the following packages on RHEL8.7 host:
kernel-4.18.0-390.el8.x86_64
libguestfs-1.44.0-7.module+el8.7.0+15229+b143b6f1.x86_64
libvirt-8.0.0-7.module+el8.7.0+15262+04e62783.x86_64
qemu-kvm-6.2.0-13.module+el8.7.0+15131+941fbd8d.x86_64
seabios-bin-1.16.0-1.module+el8.7.0+15006+42c9ed21.noarch
# while LIBGUESTFS_BACKEND_SETTINGS=force_tcg libguestfs-test-tool >&/tmp/log ; do echo -n . ; done
.................................................
# while LIBGUESTFS_BACKEND=direct LIBGUESTFS_BACKEND_SETTINGS=force_tcg libguestfs-test-tool >&/tmp/log ; do echo -n . ; done
.............................................
The above two commands worked fine.
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 (Low: virt:rhel and virt-devel:rhel security, bug fix, and enhancement update), 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/RHSA-2022:7472