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:
'lock' mode memoryBacking will make qemu-kvm crashed.

Version-Release number of selected component (if applicable):
libvirt-1.1.1-13.el7.x86_64
qemu-kvm-rhev-1.5.3-20.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. define a guest with this:
# virsh edit kvm-rhel6.5-x86_64-qcow2-virtio
...
  <memory unit='KiB'>3049024</memory>  // the memory of guest is enough
  <currentMemory unit='KiB'>3049024</currentMemory>
  <memoryBacking>
  <locked/>
  </memoryBacking>
...

2. start it
# virsh start kvm-rhel6.5-x86_64-qcow2-virtio

3. after grub stage, guest will shutdown.
check out qemu.log
# tail /var/log/libvirt/qemu/kvm-rhel6.5-x86_64-qcow2-virtio.log
2013-11-28 09:39:23.710+0000: 30844: debug : virCommandHandshakeChild:388 : Handshake with parent is done
char device redirected to /dev/pts/1 (label charserial0)
GLib (gthread-posix.c): Unexpected error from C library during 'malloc': Resource temporarily unavailable.  Aborting.
2013-11-28 09:39:36.517+0000: shutting down

Actual results:
guest start fails

Expected results:
guest start success

Additional info:
Starting guest only using qemu command line will not crash.

You also need to set memtune/hard_limit. But as I can see, there's no documentation about it, which needs to be fixed.

The documentation is now fixed upstream by v1.2.0-72-g24fbbb8:

commit 24fbbb82636ee00a5f5ac3c960459696e96f2911
Author: Jiri Denemark <jdenemar>
Date:   Mon Dec 9 15:42:15 2013 +0100

    docs: Enhance memoryBacking/locked documentation
    
    Mention the need to set memtune/hard_limit.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1035954

we can see the patch is applied http://libvirt.org/formatdomain.html#elementsMemoryBacking

When I add hard_limit to 2894304KiB, the guest can boot:
  <memory unit='KiB'>1048576</memory>
  <currentMemory unit='KiB'>1048576</currentMemory>
  <memtune>
    <hard_limit unit='KiB'>2894304</hard_limit>
  </memtune>
  <memoryBacking>
    <locked/>
  </memoryBacking>

So I change the status to VERIFIED.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.