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:
Boot guest with hugepage and guest total memory is not a multiple of pagesize, then do local migration, migration fail and destination qemu process quit with error message:
(qemu) qemu-kvm: Illegal RAM offset 40100000
qemu-kvm: error while loading state section id 4(ram)
qemu-kvm: load of migration failed: Invalid argument
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.9.0-3.el7
3.10.0-661.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. Set hugepage on host
# cat /proc/meminfo | grep -i huge
AnonHugePages: 1705984 kB
HugePages_Total: 3000
HugePages_Free: 3000
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
# mount | grep mnt
none on /mnt/kvm_hugepage type hugetlbfs (rw,relatime,seclabel)
2. Boot src guest with hugepage and '-m 1025'
# /usr/libexec/qemu-kvm -m 1025 rhel74-1-1.qcow2 -mem-path /mnt/kvm_hugepage -monitor stdio -vnc :0
3. Boot dst guest with same cmdline and '-incoming tcp:0:5555'
# /usr/libexec/qemu-kvm -m 1025 rhel74-1-1.qcow2 -mem-path /mnt/kvm_hugepage -monitor stdio -vnc :1 -incoming tcp:0:5555
4. Do migration from src guest
(qemu) migrate -d tcp:127.0.0.1:5555
Actual results:
Dst qemu quit with:
(qemu) qemu-kvm: Illegal RAM offset 40100000
qemu-kvm: error while loading state section id 4(ram)
qemu-kvm: load of migration failed: Invalid argument
Expected results:
Migration success and guest work well.
Additional info:
1. Hit same issue with both 2M and 1G hugepage
2. Can NOT reproduce with qemu-kvm-rhev-2.6.0-28.el7
Comment 4Dr. David Alan Gilbert
2017-05-16 17:32:25 UTC
Yes, I can repeat that here. 2.6->2.9 works.
2.9->2.9 fails
2.9->2.6 fails
I think the problem is that the new code makes sure it sends whole hugepages, but in this case the usedlength is probably not a multiple of a hugepage.
There's then a fun question of what happens on postcopy.
Comment 5Dr. David Alan Gilbert
2017-05-17 17:04:54 UTC
QE reproduced the bug on builds
qemu-kvm-rhev-2.9.0-3.el7
Steps,please refer to comment0
Actual results,
[root@hp-dl385pg8-13 home]# /usr/libexec/qemu-kvm -m 1025 rhel74.qcow2 -mem-path /mnt/kvm_hugepage -monitor stdio -vnc :1 -incoming tcp:0:5555
QEMU 2.9.0 monitor - type 'help' for more information
(qemu) qemu-kvm: Illegal RAM offset 40100000
qemu-kvm: error while loading state section id 4(ram)
qemu-kvm: load of migration failed: Invalid argument
Expected results,
There is no error and migration should succeed
QE verified the bug on the builds
qemu-kvm-rhev-2.9.0-7.el7.x86_64
kernel-3.10.0-671.el7.x86_64
Steps please refer to comment0
Actual results,
Migration succeeded
Expected results,
Migration succeeded
In brief,the bug has been fixed already,thanks.
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/RHSA-2017:2392