On Mon, 2012-05-07 at 17:07 +0200, Michel van Horssen wrote:
> Some extra info:
> 
> If I go into virsh on the engine/vdsm and type connect 
> qemu+tls://192.168.10.79/system I get:
> 
> error: unable to connect to server at '192.168.10.79:16514': Connection 
> refused
> 
> (192.168.10.79 is the nodes IP address)
> 
> If I open virsh on the node and type qemu+tls://192.168.10.31/system there no 
> error and I have a connection
> 
> (192.168.10.31 is the engine/vdsm's IP address)
>  
> This explains why I can migrate towards the engine/vdsm but not towards the 
> node.
> 
> Not sure but it seems a certificate thing.
> 
> Any pointers where to start looking?
> 
> Michel

This strikes me as more of a vdsm problem than ovirt-node directly.
Once node is registered to engine, we hand over all control of libvirt
and networking (among other things) to the engine to manage.  If
migration is failing due to some setting on the node, then vdsm should
probably be changing that setting when it comes online.  

I'm adding the vdsm-devel list to get them to look at this issue.  

Mike

> 
> 
> ----- Oorspronkelijk bericht -----
> > Van: "Michel van Horssen" <mvanhors...@vluchtelingenwerk.nl>
> > Aan: node-de...@ovirt.org
> > Verzonden: Maandag 7 mei 2012 16:34:26
> > Onderwerp: [node-devel] Still not abel to migrate to node
> > 
> > Hi,
> > 
> > I've re-installed my system with a separate DNS just for my test.
> > Time on the servers are correct.
> > Still migrating a VM from the VDSM on my engine towards a node gives
> > me problems.
> > 
> > The vdsm.log on the engine says:
> > 
> > ---
> > Thread-203040::ERROR::2012-05-07
> > 15:51:36,794::vm::170::vm.Vm::(_recover)
> > vmId=`95fac60f-49f5-4dcb-8c2d-2dfd926c781b`::operation failed:
> > Failed to connect to remote libvirt URI
> > qemu+tls://192.168.10.79/system
> > Thread-203041::DEBUG::2012-05-07
> > 15:51:36,795::libvirtvm::329::vm.Vm::(run)
> > vmId=`95fac60f-49f5-4dcb-8c2d-2dfd926c781b`::migration downtime
> > thread exiting
> > Thread-203040::ERROR::2012-05-07 15:51:37,045::vm::234::vm.Vm::(run)
> > vmId=`95fac60f-49f5-4dcb-8c2d-2dfd926c781b`::Traceback (most recent
> > call last):
> >   File "/usr/share/vdsm/vm.py", line 217, in run
> >     self._startUnderlyingMigration()
> >   File "/usr/share/vdsm/libvirtvm.py", line 443, in
> >   _startUnderlyingMigration
> >     None, maxBandwidth)
> >   File "/usr/share/vdsm/libvirtvm.py", line 483, in f
> >     ret = attr(*args, **kwargs)
> >   File "/usr/share/vdsm/libvirtconnection.py", line 79, in wrapper
> >     ret = f(*args, **kwargs)
> >   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 971, in
> >   migrateToURI2
> >     if ret == -1: raise libvirtError ('virDomainMigrateToURI2()
> >     failed', dom=self)
> > libvirtError: operation failed: Failed to connect to remote libvirt
> > URI qemu+tls://192.168.10.79/system
> > ---
> > 
> > Can someone give me a pointer where to look?
> > 
> > Regards,
> > Michel
> > _______________________________________________
> > node-devel mailing list
> > node-de...@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/node-devel
> > 
> _______________________________________________
> node-devel mailing list
> node-de...@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/node-devel


_______________________________________________
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel

Reply via email to