Bug 549938 – Maintain barrier state after migration

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 549938 - Maintain barrier state after migration

Summary:	Maintain barrier state after migration

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 5
Classification:	Red Hat
Component:	kvm (Show other bugs)
Sub Component:
Version:	5.5
Hardware:	All Linux

Priority	high Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Juan Quintela
QA Contact:	Virtualization Bugs
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	550269 552474 (view as bug list)
Depends On:
Blocks:	556823
	Show dependency tree / graph

Reported:	2009-12-22 19:48 EST by Juan Quintela
Modified:	2013-01-09 17:08 EST (History)
CC List:	7 users (show)

See Also:
Fixed In Version:	kvm-83-145.el5
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-03-30 03:54:17 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2010:0271	normal	SHIPPED_LIVE	Important: kvm security, bug fix and enhancement update	2010-03-29 09:19:48 EDT

Groups: None (edit)

Description Juan Quintela 2009-12-22 19:48:33 EST

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 09:06:39 EST

New patch was received for this BZ. Reopening.

Comment 8 Miya Chen 2010-01-15 05:47:56 EST

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 08:04:02 EST

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

Comment 11 Bill Burns 2010-03-04 08:33:31 EST

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

Comment 13 errata-xmlrpc 2010-03-30 03:54:17 EDT

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

Note You need to log in before you can comment on or make changes to this bug.