Re: Fwd: VirtualDomain broken for live migration.

Thanks Kristoffer, Cédric, and Dejan for your help.

On 19 August 2014 08:00, Dejan Muhamedagic <[email protected]> wrote:
> I was not able to find any information on this. In libvirt
> v1.2.5 the --live option still exists for the migrate command.

I'm using libvirt 1.1.1 which is the latest release in the CentOS7 yum repo.

There is no mention at all of a "--live" option on the libvirt Wiki

  http://libvirt.org/migration.html

and it's not mentioned in "virsh help".  Although I see it is
mentioned in the man page, so it is still there but it doesn't help
with the problem.

VirtualDomain appears to be forming a virsh command that looks like this

  # virsh --connect=qemu:///system --quiet migrate --live VMname
qemu+ssh://newhost/system

which gives me the following error

  error: unable to connect to server at 'newhost:49152': No route to host

because it's not using SSH it's trying to do a native migration over
TCP connection which is blocked by the firewall.

In order to tell virsh to use SSH I need to pass the "--tunnelled"
parameter, which in turn then requires the "--p2p" parameter.

  # virsh --connect=qemu:///system --quiet migrate --live --tunnelled
--p2p VMname qemu+ssh://newhost/system

Which correctly migrates the guest.  How do I get VirtualDomain to
pass the "--tunnelled --p2p" options to make it actually use ssh as
required by the remote URI?

When I do a manual migration it does leave behind the source config,
and doesn't create a config on the new host.  The guest goes from
"persistent" to "transient" as described in the table on the libvirt
Wiki.  I've tried to pass the --undefine-source and --persist options
to make it transfer the config and go from "persistent" to
"persistent", but that doesn't work either.  I get either

  error: unsupported option '--undefine-source'. See --help.

or

  error: command 'migrate' doesn't support option --undefine-source

depending on whether I try to put the option before or after the
"migrate" command.  Looking at the help like it says doesn't help.

  # virsh --help | grep source
      find-storage-pool-sources-as   find potential storage pool sources
      find-storage-pool-sources      discover potential storage pool sources

which tells me nothing about the --undefine-source option.

Of course, this is nothing to do with Pacemaker.  I only bring it up
as an example of where the libvirt documentation appears to be
completely wrong, hence my thinking that --live didn't appear to be
doing anything either.

> Yes, it is. Isn't there some information in the resource-agents
> package where the software lives and where to get support?

Yes, I see now the link to the Github repo is provided in the package
information.  Thanks.  I hadn't seen that.  I'd only been looking at
the ha-linux Wiki which doesn't seem to have been updated since 2010.

Thanks again for all the help.

Steve.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems