openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #04641
Re: Live Migration and Xen + Libvirt
I've done some debugging and as the problem is related to an rpc call, I'm
also adding the true source of the problem, the nova-compute.log in the
destination compute node. It seems to be something related to the cpu_info,
probably not related at all with Xen.
2011-10-10 15:43:43,718 ERROR nova.exception [-] Exceção não capturada
(nova.exception): TRACE: Traceback (most recent call last):
(nova.exception): TRACE: File
"/usr/lib/pymodules/python2.6/nova/exception.py", line 98, in wrapped
(nova.exception): TRACE: return f(*args, **kw)
(nova.exception): TRACE: File
"/usr/lib/pymodules/python2.6/nova/compute/manager.py", line 1317, in
compare_cpu
(nova.exception): TRACE: return self.driver.compare_cpu(cpu_info)
(nova.exception): TRACE: File
"/usr/lib/pymodules/python2.6/nova/virt/libvirt/connection.py", line 1565,
in compare_cpu
(nova.exception): TRACE: xml = str(Template(self.cpuinfo_xml,
searchList=dic))
(nova.exception): TRACE: File
"/usr/lib/pymodules/python2.6/Cheetah/Template.py", line 981, in __str__
(nova.exception): TRACE: def __str__(self): return getattr(self,
mainMethName)()
(nova.exception): TRACE: File "DynamicallyCompiledCheetahTemplate.py",
line 92, in respond
(nova.exception): TRACE: NotFound: cannot find 'model'
Is the python 2.6 a problem? I remind you that I'm using Ubuntu 10.04, and
as such, python 2.6 is the default.
Em 6 de outubro de 2011 14:42, Rogério Vinhal Nunes
<rogervn@xxxxxxxxxxx>escreveu:
> I'm trying to make live migration work in an environment with Xen and
> Libvirt, but I found some issues.
>
> The first one I managed to "correct", but it really looks like a bug. The
> live migration command will fail and the logs will indicate
> "InstanceNotRunning". That's because when a xen virtual machine is not using
> the processor, its status is "blocked". I "corrected" it by sending the
> instance in an infinite CPU loop and waiting for nova-compute to update the
> DB with the status "running". I don't know how these status are handled by
> KVM, but at least the migration check should take that in consideration if
> it plans to work with xen.
>
> The second one is a little more complicated and I haven't found a solution
> yet, so you may help me with it. After making the vm "running" the live
> migration just fails and the logs rise an error "Cannot find "'model'". Is
> there any configuration that is related to this?
>
> trace from nova-manage.log:
>
> (nova): TRACE: Traceback (most recent call last):
> (nova): TRACE: File "/usr/bin/nova-manage", line 2141, in <module>
> (nova): TRACE: main()
> (nova): TRACE: File "/usr/bin/nova-manage", line 2129, in main
> (nova): TRACE: fn(*fn_args, **fn_kwargs)
> (nova): TRACE: File "/usr/bin/nova-manage", line 987, in live_migration
> (nova): TRACE: self._migration(ec2_id, dest)
> (nova): TRACE: File "/usr/bin/nova-manage", line 976, in _migration
> (nova): TRACE: "block_migration": block_migration}})
> (nova): TRACE: File "/usr/lib/pymodules/python2.6/nova/rpc/__init__.py",
> line 45, in call
> (nova): TRACE: return get_impl().call(context, topic, msg)
> (nova): TRACE: File
> "/usr/lib/pymodules/python2.6/nova/rpc/impl_kombu.py", line 739, in call
> (nova): TRACE: rv = list(rv)
> (nova): TRACE: File
> "/usr/lib/pymodules/python2.6/nova/rpc/impl_kombu.py", line 703, in __iter__
> (nova): TRACE: raise result
> (nova): TRACE: RemoteError: RemoteError Error cannot find 'model'
>
References