openstack team mailing list archive

["Yuan, Ye A" <ye.a.yuan@xxxxxxxxx>]

Hey guy,
Please try as below:

1)      If there is no log, maybe config/log file's privilege issue. You can edit their owner: $ chown nova:nova /etc/nova && chown nova:nova /var/log/nova

2)      After method 1) , there must be logs in log file. You can run command $ nova-manage logs error, it will print all nova services' error

3)      I facing migration issue similar before, it seems that CPU compatibility is too strict! And you can edit source code in /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, in function compare_cpu, comment 2lines:

#if ret <= 0:

         #raise exception.InvalidCPUInfo(reason=m % locals())

Or upgrade Essex to Folsom!
If methods I metioned work. Please let me know!

Best wishes,
Yale Yuan
>From Intel
From: openstack-bounces+ye.a.yuan=intel.com@xxxxxxxxxxxxxxxxxxx [mailto:openstack-bounces+ye.a.yuan=intel.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Narayanan, Krishnaprasad
Sent: Tuesday, January 08, 2013 1:33 AM
To: openstack@xxxxxxxxxxxxxxxxxxx
Subject: [Openstack] Strange issue during live migration

Hallo All,

I am using OpenStack ESSEX and I have made all the necessary changes in order to perform live-migration (mounting the nova instances directory and libvirt-bin configurations). The issue that I am facing is when I perform live migration using the nova commands, there is neither error in the log file nor on the command and in the Horizon GUI, I could see the VM status changing to Migrating and later turning Active, but in the back end, the VM is not migrating to the specified host. Has anybody faced the same issue and can I get to know am I missing any configurations?

Thanks
Krishnaprasad