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.
Motto: 00 00 != add %al,(%bx,%si)
We bug because RHEL7 qemu does not migrate all RHEL6 memory to its previous location, which leads to infinite loops or emulation errors if there suddenly are zeroes at instruction pointer in early boot.
[issue 'c' and 'stop' qemu commands quickly]
(qemu) x /16 0xc0000
00000000000c0000: 0xe946aa55 0x00000121 0x00000000 0x00000000
00000000000c0010: 0x00000000 0x00000000 0x0000010f 0x42490000
00000000000c0020: 0x6c50004d 0x36387865 0x636f422f 0x56207368
00000000000c0030: 0x69424147 0x2820736f 0x29494350 0x75630020
[migrate]
(qemu) x /16 0xc0000
00000000000c0000: 0x00000000 0x00000000 0x00000000 0x00000000
00000000000c0010: 0x00000000 0x00000000 0x00000000 0x00000000
00000000000c0020: 0x00000000 0x00000000 0x00000000 0x00000000
00000000000c0030: 0x00000000 0x00000000 0x00000000 0x00000000
We don't use this memory for normal operation, so if we migrate after few seconds, everything works, not ... I originally missed the possibility of reboots/sleep, so fixing this didn't seem critical, but luckily, Laszlo worked on it under a different bug.
(Network device and missing disk image were ruses -- the guest boots faster and
tests didn't catch this broken state.)
*** This bug has been marked as a duplicate of bug 1027565 ***