This bug has been copied from bug #541731 and has been proposed
to be backported to 5.4 z-stream (EUS).
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.
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
[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.
(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.
(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
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
> [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 GNU/Linux
> Installing 5.4.4 to be able to test case 10.
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.
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).
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.