Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 552529 - kvm: migration: mechanism to make older savevm versions to be emitted on some cases
kvm: migration: mechanism to make older savevm versions to be emitted on some...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kvm (Show other bugs)
5.5
All Linux
high Severity medium
: rc
: ---
Assigned To: Juan Quintela
Virtualization Bugs
: ZStream
Depends On: 541731
Blocks: 553441
  Show dependency treegraph
 
Reported: 2010-01-05 07:23 EST by RHEL Product and Program Management
Modified: 2013-01-09 17:10 EST (History)
11 users (show)

See Also:
Fixed In Version: kvm-83-105.el5_4.16
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-02-09 05:02:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0088 normal SHIPPED_LIVE Important: kvm security and bug fix update 2010-02-09 05:01:51 EST

  None (edit)
Description RHEL Product and Program Management 2010-01-05 07:23:21 EST
This bug has been copied from bug #541731 and has been proposed
to be backported to 5.4 z-stream (EUS).
Comment 9 Juan Quintela 2010-01-25 10:41:54 EST
5.5.4 is 5.4.4 I would guess.
Fix is needed for 5.4.4, not sure if that impacts RHEV-2.1.
Comment 13 Juan Quintela 2010-01-25 11:35:23 EST
    What are you using for testing?

    Case 8 works for me (5.5.0 -> 5.5.0) both started with -M rhel5.4.4

    Packages installed are:

    [root@ninfa ~]# rpm -qa kvm kmod-kvm
    kmod-kvm-83-147.el5
    kvm-83-147.el5
    [root@ninfa ~]# uname -a
    Linux ninfa.mitica 2.6.18-185.el5 #1 SMP Thu Jan 14 16:44:40 EST 2010 x86_64
    x86_64 x86_64 GNU/Linux

    Installing 5.4.4 to be able to test case 10.
Comment 15 Lawrence Lim 2010-01-25 21:19:55 EST
(In reply to comment #9)
> 5.5.4 is 5.4.4 I would guess.
> Fix is needed for 5.4.4, not sure if that impacts RHEV-2.1.    

Yes, there will be impact, as a respin of kvm would require a respin of RHEV-2.1 as well to include the latest kvm package.
Comment 16 lihuang 2010-01-26 00:20:16 EST
(In reply to comment #13)
>     What are you using for testing?
> 
>     Case 8 works for me (5.5.0 -> 5.5.0) both started with -M rhel5.4.4

Hi
Case 8 is 5.5.0->5.4.4 both started with -M rhel5.4.4, "load of migration failed" error won't be reported on qemu monitor. but if you connect to dst's vnc,you can find there is only black screen. ( sorry,Case 8 and Case 10 has different result,I should clarify early )

and 5.5.0->5.5.0 both started with -M rhel5.4.4 also works for us.


> 
>     Packages installed are:
> 
>     [root@ninfa ~]# rpm -qa kvm kmod-kvm
>     kmod-kvm-83-147.el5
>     kvm-83-147.el5
>     [root@ninfa ~]# uname -a
>     Linux ninfa.mitica 2.6.18-185.el5 #1 SMP Thu Jan 14 16:44:40 EST 2010
> x86_64
>     x86_64 x86_64 GNU/Linux
> 
>     Installing 5.4.4 to be able to test case 10.
Comment 20 Juan Quintela 2010-01-26 08:23:30 EST
Noticed that this bugzilla is for 5.4.z.  Problem and patch is fixed in 5.5.  5.4.z has nothing to change to fix this bug.  Should I close this bug?
557327 is a 5.5 bug already.
Comment 21 Eduardo Habkost 2010-01-26 08:41:51 EST
This bug may be moved back to ON_QA so it can be tested. But please note that full testing of this depends on fixing the -M 5.4.4 code on RHEL-5.5 (bug 557327).
Comment 24 errata-xmlrpc 2010-02-09 05:02:45 EST
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-0088.html

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