[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [rhelv5-list] Live migration of Xen domains in a cluster - SOLVED



We have seen this problem also with my customer. The problem they have, because vm.sh is not a config file, when we modify the vm.sh script it "breaks" the back-end support from Red Hat. Potentially, a yum update could fail because the file has been changed. Could this parameter be configurable parameter selectable from Conga?

Zavodsky, Daniel (GE Money) wrote:
Hello,
	Thank you very much, the suggested change in vm.sh script did
the trick!

Best regards,
Daniel Zavodsky
-----Original Message-----
From: rhelv5-list-bounces redhat com
[mailto:rhelv5-list-bounces redhat com] On Behalf Of Jan Mark Holzer
Sent: Thursday, December 06, 2007 12:23 PM
To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list
Subject: Re: [rhelv5-list] Live migration of Xen domains in a cluster

Hi,

    you might be running into the case where the cluster script in
/usr/share/cluster/vm.sh
    is not using the '-l' option for the "xm migrate" command .
    If you edit the above script and change line 382 to add the '-l'
flag to
    the "xm migrate" command it will then use live migration .
    Remember to make the change on all nodes in your cluster :)

Hth,

- Jan

Zavodsky, Daniel (GE Money) wrote:
Greetings,
I am using RHEL 5 update 1 and I am having trouble getting "real" live migration to work in a cluster environment.
    When I do this on member2:
# clusvcadm -M guest1 -m member1 The guest1 is first suspended on member2, its memory copied over to member1 and then started on member1. With several gigabytes of RAM in the guest, this amounts to an outage of more than one minute (on gigabit ethernet), losing network connections etc.. When I do this on member2: # xm migrate guest1 member1 -l The guest1 continues running while its memory is being copied over to member1, there is only a brief pause at the end of the copying process. It looks like as if clusvcadm did migration without the "-l"
parameter...
Is this behaviour configurable or is this not supported by clusvcadm in RHEL 5 update 1 yet? How do you solve this issue in your cluster?
Thank you very much for any advice.
Best regards,
    Daniel Zavodsky
----------------------------------------------------------------------
--

_______________________________________________
rhelv5-list mailing list
rhelv5-list redhat com
https://www.redhat.com/mailman/listinfo/rhelv5-list

_______________________________________________
rhelv5-list mailing list
rhelv5-list redhat com
https://www.redhat.com/mailman/listinfo/rhelv5-list



_______________________________________________
rhelv5-list mailing list
rhelv5-list redhat com
https://www.redhat.com/mailman/listinfo/rhelv5-list
begin:vcard
fn:Leo J Pleiman, RHCE
n:Pleiman;Leo J
org:410-688-3873;GPS Federal
email;internet:lpleiman redhat com
title:Senior Consultant
tel;work:301.763.3527
tel;cell:410.688.3873
version:2.1
end:vcard


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]