Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 549938

Summary:	Maintain barrier state after migration
Product:	Red Hat Enterprise Linux 5	Reporter:	Juan Quintela <quintela>
Component:	kvm	Assignee:	Juan Quintela <quintela>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	high
Version:	5.5	CC:	ehabkost, llim, michen, tburke, virt-maint, ykaul, yzhou
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	kvm-83-145.el5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-03-30 07:54:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	556823

Description Juan Quintela 2009-12-23 00:48:33 UTC

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:

Comment 3 Eduardo Habkost 2010-01-05 14:06:39 UTC

New patch was received for this BZ. Reopening.

Comment 8 Miya Chen 2010-01-15 10:47:56 UTC

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.

Comment 9 Juan Quintela 2010-01-21 13:04:02 UTC

*** Bug 552474 has been marked as a duplicate of this bug. ***

Comment 11 Bill Burns 2010-03-04 13:33:31 UTC

*** Bug 550269 has been marked as a duplicate of this bug. ***

Comment 13 errata-xmlrpc 2010-03-30 07:54:17 UTC

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