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 718664 - Migration from host RHEL6.1+ to host RHEL6.0.z failed with floppy
Summary: Migration from host RHEL6.1+ to host RHEL6.0.z failed with floppy
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
high
high
Target Milestone: rc
: ---
Assignee: jason wang
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 713389
Blocks: 743047
TreeView+ depends on / blocked
 
Reported: 2011-07-04 08:06 UTC by jason wang
Modified: 2013-01-10 00:02 UTC (History)
16 users (show)

Fixed In Version: qemu-kvm-0.12.1.2-2.187.el6
Doc Type: Bug Fix
Doc Text:
Cause: In order to save media_changed flag of floppy across migration, a new subsection were introduced, and the subsection were sent when the floppy were not changed ( media_changed is zero ). This would as the subsection would be sent almost every time. Consequence: As qemu-kvm would fail the migration when it met the subsection it does not recongize, this would cause the migration from newer qemu-kvm version to elder version with floppy fail. Fix: In order to keep the migration compatibility, the fix only accept the subseciont but do nothing and also disable the sending of the subsection. Result: The migration between any version of qemu-kvm with floopy would success.
Clone Of: 713389
Environment:
Last Closed: 2011-12-06 15:53:04 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

Comment 8 langfang 2011-09-21 08:37:17 UTC 
Reproduced this issue with hostA(rhel6.2):qemu-kvm-0.12.1.2-2.184.el6.x86_64 kernel:2.6.32-198.el6.x86_64 hostB(rhel6.0.z):qemu-kvm-0.12.1.2-2.113.el6.x86_64 kernel:2.6.32-71.31.1.el6.x86_64
steps:
1.boot guest with floopy 
  #/usr/libexec/qemu-kvm ...-drive file=/mnt/virtio-driver-1.vfd,if=floppy,format=raw
2.do migrate form hostA to hostB

Results:migrate failed
show the below fail message
qemu: warning: error while loading state for instance 0x0 of device 'ram'
load of migration failed


Veriry this issue with hostA(rhel6.2):qemu-kvm-0.12.1.2-2.190.el6.x86_64
kernel:2.6.32-198.el6.x86_64 hostB(rhel6.0.z):qemu-kvm-0.12.1.2-2.113.el6.x86_64 kernel:2.6.32-71.31.1.el6.x86_64 using steps as same as reproduce

Results:show the same error as same as reproduce

Actual results:
migrate successful


Above all,this issue still have problem,there have a bug698936 about the same problem, Maybe this bug should modify first,then this issue will be resolved.Or this is a new bug?thanks~~
Comment 9 jason wang 2011-09-21 09:45:15 UTC 
(In reply to comment #8)
> Reproduced this issue with hostA(rhel6.2):qemu-kvm-0.12.1.2-2.184.el6.x86_64
> kernel:2.6.32-198.el6.x86_64
> hostB(rhel6.0.z):qemu-kvm-0.12.1.2-2.113.el6.x86_64
> kernel:2.6.32-71.31.1.el6.x86_64
> steps:
> 1.boot guest with floopy 
>   #/usr/libexec/qemu-kvm ...-drive
> file=/mnt/virtio-driver-1.vfd,if=floppy,format=raw
> 2.do migrate form hostA to hostB
> 
> Results:migrate failed
> show the below fail message
> qemu: warning: error while loading state for instance 0x0 of device 'ram'
> load of migration failed
> 
> 
> Veriry this issue with hostA(rhel6.2):qemu-kvm-0.12.1.2-2.190.el6.x86_64
> kernel:2.6.32-198.el6.x86_64
> hostB(rhel6.0.z):qemu-kvm-0.12.1.2-2.113.el6.x86_64
> kernel:2.6.32-71.31.1.el6.x86_64 using steps as same as reproduce
> 
> Results:show the same error as same as reproduce
> 
> Actual results:
> migrate successful
> 
> 
> Above all,this issue still have problem,there have a bug698936 about the same
> problem, Maybe this bug should modify first,then this issue will be resolved.Or
> this is a new bug?thanks~~

Looks realted, And can you try doing an offline migration to test this bz?
Just stop the machine before doing the migration.
Thanks
Comment 10 langfang 2011-09-21 11:35:43 UTC 
Reproduced this issue with hostA(rhel6.2):qemu-kvm-0.12.1.2-2.184.el6.x86_64
kernel:2.6.32-198.el6.x86_64
hostB(rhel6.0.z):qemu-kvm-0.12.1.2-2.113.el6.x86_64
kernel:2.6.32-71.31.1.el6.x86_64
steps:
1.boot guest with floopy 
  #/usr/libexec/qemu-kvm ...-drive file=/mnt/virtio-driver-1.vfd,if=none,id=drive-fdc0-0-0,format=raw,cache=none -global isa-fdc.driveA=drive-fdc0-0-0
2.do migrate form hostA to hostB

Results:migrate failed
show the below fail message
qemu-kvm-0.12.1.2-2.184.el6.x86_64
qemu: warning: error while loading state for instance 0x3f0 of device 'fdc'
load of migration failed

Veriry this issue with hostA(rhel6.2):qemu-kvm-0.12.1.2-2.189.el6.x86_64
kernel:2.6.32-198.el6.x86_64
hostB(rhel6.0.z):qemu-kvm-0.12.1.2-2.113.el6.x86_64
kernel:2.6.32-71.31.1.el6.x86_64 using steps as same as reproduce

Results:
migrate successful

Above all,this issue have been fixed.
addtional info:
this kind of migration only support vnc boot guest,not support spice.
Comment 12 jason wang 2011-11-18 01:54:37 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause:

In order to save media_changed flag of floppy across migration, a new subsection were introduced, and the subsection were sent when the floppy were not changed ( media_changed is zero ). This would as the subsection would be sent almost every time. 

Consequence:

As qemu-kvm would fail the migration when it met the subsection it does not recongize, this would cause the migration from newer qemu-kvm version to elder version with floppy fail.

Fix:

In order to keep the migration compatibility, the fix only accept the subseciont but do nothing and also disable the sending of the subsection.

Result:

The migration between any version of qemu-kvm with floopy would success.
Comment 13 errata-xmlrpc 2011-12-06 15:53:04 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.