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.
Bug 725565 - migration subsections are still broken
Summary: migration subsections are still broken
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Juan Quintela
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 748554
TreeView+ depends on / blocked
 
Reported: 2011-07-25 20:49 UTC by Paolo Bonzini
Modified: 2013-01-10 00:09 UTC (History)
8 users (show)

Fixed In Version: qemu-kvm-0.12.1.2-2.206.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 15:54:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:1531 0 normal SHIPPED_LIVE Moderate: qemu-kvm security, bug fix, and enhancement update 2011-12-06 01:23:30 UTC

Description Paolo Bonzini 2011-07-25 20:49:10 UTC 
While a few subsection problems involving bogus migration failures have been fixed in 6.1, others remain in the form of silent migration success when only part of the data stream has been read.  The problem occurs when the destination expects no subsections and reads one into subsequent fields of the data stream. If a zero byte happens at the right time, it is interpreted as end-of-data and migration erroneously succeeds.

The fix is to add explicit end-of-subsections markers so that unexpected subsections can cause migration to fail.

Kevin reproduced this on a 6.2 to 6.1 migration, but no testcase is available right now. It is possible to construct one artificially; if required, patched packages triggering the bug can be provided to QE.
Comment 1 Kevin Wolf 2011-07-26 08:14:54 UTC 
(In reply to comment #0)
> Kevin reproduced this on a 6.2 to 6.1 migration, but no testcase is available
> right now. It is possible to construct one artificially; if required, patched
> packages triggering the bug can be provided to QE.

For the record: This was an IDE disk with werror=stop,rerror=stop, VM stopped after an artificially provoked I/O error and migration while the VM was still stopped. This means that the error_status subsection is transferred, which 6.1 doesn't know.

I think this way of reproducing it should still work.
Comment 2 Paolo Bonzini 2011-07-26 09:16:23 UTC 
Yes, the problem is that you need the rhel6.2.0 machine in order to trigger the new migration format.  So migrating to 6.1 would fail anyway due to the unknown machine type.  I was thinking of giving QE a patched 6.1 package which also defines the rhel6.2.0 machine type, so that they can reproduce the bug.
Comment 7 Shaolong Hu 2011-10-20 13:06:06 UTC 
Reproduce on qemu-kvm-0.12.1.2-2.196.el6.x86_64:

Steps:
--------
1.boot guest on src with:
/usr/libexec/qemu-kvm -enable-kvm -M rhel6.2.0 -smp 4 -m 6G -name rhel6.2 -uuid 3f2ea5cd-3d29-48ff-aab2-23df1b6ae213 -drive file=RHEL-Server-6.2-64-virtio.qcow2,cache=none,if=none,rerror=stop,werror=stop,id=drive-virtio-disk0,format=qcow2 -device ide-drive,drive=drive-virtio-disk0,id=device-virtio-disk0 -boot order=cd -monitor stdio -vnc :10

2.boot guest on des with same command line except for "-M rhel6.1.0 -incoming tcp:0:5555"

3.consume guest block space to cause guest paused:
(qemu) block I/O error in device 'drive-virtio-disk0': No space left on device (28)

4.migrate to des, migration succeeds.


Verify on:
---------------
src host: qemu-kvm-0.12.1.2-2.199.el6.x86_64
des host: qemu-kvm-0.12.1.2-2.160.el6.shu.bz725565.x86_64

http://brewweb.devel.redhat.com/brew/taskinfo?taskID=3726275

*This scratch build based on qemu-kvm-0.12.1.2-2.160.el6_1.8, patched with patches in Comment 4 and patch "pc: add rhel 6.2 pc and make it the default".

After step 4, migration fails, on des:
(qemu) qemu: warning: error while loading state for instance 0x0 of device '0000:00:01.1/ide'
load of migration failed

On src:
(qemu) info migrate
Migration status: completed

Better on src, info migrate shows migration failed, however, this won't keep the bug from verified.


Additional info:
--------------------
"-M rhel6.2.0" to "-M rhel6.1.0" migration fails if add device has unknown feature, like in step 1, if add a virtio NIC, migration fails, so i think as long as migration can succeed, this is enough to reproduce the bug.

However, to verify the bug, need using the scratch build on des.
Comment 10 Eduardo Habkost 2011-10-28 17:59:10 UTC 
Moving to ON_QA because Errata Tool did not do it
Comment 12 errata-xmlrpc 2011-12-06 15:54:32 UTC 
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.

http://rhn.redhat.com/errata/RHSA-2011-1531.html
Note You need to log in before you can comment on or make changes to this bug.