Description of problem: rhel5.5.0 enabled barrerirs unconditionally. Indeed when migrating from 5.4.0 (that don't have barrers). Correct behaviour is: - update the vmstate with a value indicating if barriers are enabled - when migrating from 5.4.0 disable barriers. Patch is posted to fix this. This patch is important because without it, we can't waranty block layer integrity. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
New patch was received for this BZ. Reopening.
Retest migration guest from kvm-83-105.el5_4.13 to kvm-83-147, pass kvm-83-147.el5 kvm-83-105.el5_4.13 steps: 1.start guest in rhel5.4: /usr/libexec/qemu-kvm -drive file=win23k-64-virtio.qcow2,if=virtio,boot=on -no-hpet -rtc-td-hack -usbdevice tablet -startdate now -smp 2 -m 2G -net nic,macaddr=20:20:20:11:23:66,vlan=0 -net tap,vlan=0,script=/etc/qemu-ifup -cpu qemu64,+sse2 -monitor stdio -vnc :1 2.start listening mode in rhel5.5: /usr/libexec/qemu-kvm -drive file=win23k-64-virtio.qcow2,if=virtio,boot=on -no-hpet -rtc-td-hack -usbdevice tablet -startdate now -smp 2 -m 2G -net nic,macaddr=20:20:20:11:23:66,vlan=0 -net tap,vlan=0,script=/etc/qemu-ifup -cpu qemu64,+sse2 -monitor stdio -vnc :1 -incoming tcp:0:5889 -M rhel5.4.0 3. start migration. Actual result: migration complete successfully, and guest can be operated normally.
*** Bug 552474 has been marked as a duplicate of this bug. ***
*** Bug 550269 has been marked as a duplicate of this bug. ***
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0271.html