CentOS - Sep 2010 - No live migration for xen virtual machines any more

Hi folks,

I have upgraded my CentOS RHCS cluster hosts to the recent packages, and 
now live migration of the xen virtual machines does not work any more:

[root at node ~]# clusvcadm -M vm:XenVM -m othernode
Trying to migrate vm:XenVM to othernode...Invalid operation for resource

I have googled the net but found no recent entries for that problem, 
just older posts.

Has anyone had the same problem recently? If yes: is there any workaround?

Any hint or help is appreciated.

Dirk

On Sun, Sep 12, 2010 at 10:58:29AM +0200, Dirk H. Schulz
wrote:
>   Hi folks,
> 
> I have upgraded my CentOS RHCS cluster hosts to the recent packages, and 
> now live migration of the xen virtual machines does not work any more:
> 
> [root at node ~]# clusvcadm -M vm:XenVM -m othernode
> Trying to migrate vm:XenVM to othernode...Invalid operation for resource
> 
> I have googled the net but found no recent entries for that problem, 
> just older posts.
> 
> Has anyone had the same problem recently? If yes: is there any workaround?
> 
> Any hint or help is appreciated.
> 
Does it work using "xm" command directly? 

-- Pasi

On Tue, Sep 21, 2010 at 09:56:39AM -0500, Brian Cremeans
wrote:
>    Hello,
>    I have the exact same problem after an update, and it does not work
using
>    the xm command.
>    Thanks for any help you can offer.
>
Read the following logs on dom0:

- "xm log"
- dmesg
- /var/log/messages

After trying to migrate with xm.
Hopefully that helps.

-- Pasi

>    Brian L. Cremeans
>    OCCE IT
> 
>  >   Hi folks,
>  >
>  > I have upgraded my CentOS RHCS cluster hosts to the recent packages,
and
>  > now live migration of the xen virtual machines does not work any
more:
>  >
>  > [r... at node ~]# clusvcadm -M vm:XenVM -m othernode
>  > Trying to migrate vm:XenVM to othernode...Invalid operation for
resource
>  >
>  > I have googled the net but found no recent entries for that problem,
>  > just older posts.
>  >
>  > Has anyone had the same problem recently? If yes: is there any
workaround?
>  >
>  > Any hint or help is appreciated.
>  >
> 
>  Does it work using "xm" command directly?
> 
>  -- Pasi