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.
Description of problem:
when using "-realtime mlock=on" and "-sandbox on" at the same time, qemu-kvm will hang.
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.2.0-5.el7.x86_64
host kernel:
3.10.0-230.el7.x86_64
Guest kernel:
3.10.0-230.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.boot guest with "-realtime mlock=on" and "-sandbox on". cli as followings:
# /usr/libexec/qemu-kvm -realtime mlock=on -sandbox on -monitor stdio
2.
3.
Actual results:
After step 1, qemu-kvm will hang.
Expected results:
After step 1, qemu-kvm works well.
Additional info:
Reproduce this bug on qemu-kvm-rhev-2.2.0-9.el7.x86_64.
Host:
qemu-kvm-rhev-2.2.0-9.el7.x86_64
3.10.0-262.el7.x86_64
Steps:
Start qemu-kvm with:
/usr/libexec/qemu-kvm -realtime mlock=on -sandbox on -monitor stdio
Result:
qemu-kvm hang.
# ps ax |grep qemu
19960 pts/0 Zl+ 0:00 [qemu-kvm] <defunct>
Verify this bug on qemu-kvm-rhev-2.3.0-2.el7.
Result:
qemu-kvm works well.
# /usr/libexec/qemu-kvm -realtime mlock=on -sandbox on -monitor stdio
QEMU 2.3.0 monitor - type 'help' for more information
(qemu) VNC server running on `::1:5900'
(qemu)
(qemu) info status
VM status: running
So this bug has been fixed.
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://rhn.redhat.com/errata/RHBA-2015-2546.html