Hello people.
I had 4 servers (bart,homer, lisa and abraham) where livemigrate
went without problems: I was able to make them play beach-volley
with a vm instance whose image is on an NFS file system.
Then I add a couple more, marge and maggie. I can do thi
> "CC" == saint writes:
> "CC" == saint writes:
CC> I can livemigrate w/o problems between any two from red9, red10
CC> and red11, I can livemigrate from either red9, red10 or red11 to
CC> red3 but I can't livemigrate to any other blade from red3.
*wears the dunce cap*
It was a damn
> "CC" == saint writes:
> "CC" == saint writes:
CC> I can livemigrate w/o problems between any two from red9, red10
CC> and red11, I can livemigrate from either red9, red10 or red11 to
CC> red3 but I can't livemigrate to any other blade from red3.
I TCP-dumped the dialog from both a
> "CC" == saint writes:
CC> I can livemigrate w/o problems between any two from red9, red10
CC> and red11, I can livemigrate from either red9, red10 or red11 to
CC> red3 but I can't livemigrate to any other blade from red3.
That's a selection of lines from red9 log when red10 succeeds
hello everybody and happy new year!
I am a newbie in libvirt use, and I use it mostrly throught OpenNebula.
Anyway, I noticed that one of the nodes can be a destination of a
livemigrate but not the source.
This is the environment:
4 blades nicknamed(*) red3, red9, red10, red11, each wi
