[Users] Migration Failed

[Neil]

Hi Elad,

Thanks for assisting me, yes the same condition exists, if I try to
migrate Tux it says "The VM Tux is being migrated".


Below are the details requested.


[root at node01 ~]# virsh -r list
 Id    Name                           State
----------------------------------------------------
 1     adam                           running

[root at node01 ~]# pgrep qemu
11232
[root at node01 ~]# vdsClient -s 0 list table
63da7faa-f92a-4652-90f2-b6660a4fb7b3  11232  adam                 Up


[root at node03 ~]# virsh -r list
 Id    Name                           State
----------------------------------------------------
 7     tux                            running

[root at node03 ~]# pgrep qemu
32333
[root at node03 ~]# vdsClient -s 0 list table
2736197b-6dc3-4155-9a29-9306ca64881d  32333  tux                  Up

Thanks.

Regards.

Neil Wilson.


On Tue, Jan 7, 2014 at 4:43 PM, Elad Ben Aharon <ebenahar at redhat.com> wrote:
> Is it still in the same condition?
> If yes, please add the outputs from both hosts for:
>
> #virsh -r list
> #pgrep qemu
> #vdsClient -s 0 list table     (or 'vdsClient 0 list table' if you are working in insecure mode)
>
>
> Thnaks,
>
> Elad Ben Aharon
> RHEV-QE storage team
>
>
>
>
> ----- Original Message -----
> From: "Neil" <nwilson123 at gmail.com>
> To: users at ovirt.org
> Sent: Tuesday, January 7, 2014 4:21:43 PM
> Subject: [Users] Migration Failed
>
> Hi guys,
>
> I've tried to migrate a VM from one host(node03) to another(node01),
> and it failed to migrate, and the VM(tux) remained on the original
> host. I've now tried to migrate the same VM again, and it picks up
> that the previous migration is still in progress and refuses to
> migrate.
>
> I've checked for the KVM process on each of the hosts and the VM is
> definitely still running on node03 so there doesn't appear to be any
> chance of the VM trying to run on both hosts (which I've had before
> which is very scary).
>
> These are my versions... and attached are my engine.log and my vdsm.log
>
> Centos 6.5
> ovirt-iso-uploader-3.3.1-1.el6.noarch
> ovirt-host-deploy-1.1.2-1.el6.noarch
> ovirt-release-el6-9-1.noarch
> ovirt-engine-setup-3.3.1-2.el6.noarch
> ovirt-engine-3.3.1-2.el6.noarch
> ovirt-host-deploy-java-1.1.2-1.el6.noarch
> ovirt-image-uploader-3.3.1-1.el6.noarch
> ovirt-engine-dbscripts-3.3.1-2.el6.noarch
> ovirt-engine-cli-3.3.0.6-1.el6.noarch
> ovirt-engine-websocket-proxy-3.3.1-2.el6.noarch
> ovirt-engine-userportal-3.3.1-2.el6.noarch
> ovirt-log-collector-3.3.1-1.el6.noarch
> ovirt-engine-tools-3.3.1-2.el6.noarch
> ovirt-engine-lib-3.3.1-2.el6.noarch
> ovirt-engine-webadmin-portal-3.3.1-2.el6.noarch
> ovirt-engine-backend-3.3.1-2.el6.noarch
> ovirt-engine-sdk-python-3.3.0.8-1.el6.noarch
> ovirt-engine-restapi-3.3.1-2.el6.noarch
>
>
> vdsm-python-4.13.0-11.el6.x86_64
> vdsm-cli-4.13.0-11.el6.noarch
> vdsm-xmlrpc-4.13.0-11.el6.noarch
> vdsm-4.13.0-11.el6.x86_64
> vdsm-python-cpopen-4.13.0-11.el6.x86_64
>
> I've had a few issues with this particular installation in the past,
> as it's from a very old pre release of ovirt, then upgrading to the
> dreyou repo, then finally moving to the official Centos ovirt repo.
>
> Thanks, any help is greatly appreciated.
>
> Regards.
>
> Neil Wilson.
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users