<div dir="ltr"><div><div><div>VDSM built from commit: <span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:normal;display:inline!important;font-weight:normal;float:none;line-height:normal;text-transform:none;font-size:12px;white-space:normal;font-family:monospace;word-spacing:0px">c343e1833f7b6e5428dd90f14f7807dca1baa0b4</span> works<br>
</div>Current VDSM built from master does not work.<br><br></div>I could try spending some time trying to bisect and find out where the breakage occurred I suppose.<br></div>- DHC<br></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Sun, Feb 3, 2013 at 10:13 AM, Martin Kletzander <span dir="ltr"><<a href="mailto:mkletzan@redhat.com" target="_blank">mkletzan@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 02/03/2013 08:40 AM, Dan Kenigsberg wrote:<br>
> On Fri, Feb 01, 2013 at 11:44:08PM +0100, Martin Kletzander wrote:<br>
>> On 02/01/2013 09:29 PM, Dead Horse wrote:<br>
>>> To test further I loaded up two more identical servers with EL 6.3 and the<br>
>>> same package versions originally indicated. The difference here is that I<br>
>>> did not turn these into ovirt nodes. EG: installing VDSM.<br>
>>><br>
>>> - All configurations were left at defaults on both servers<br>
>>> - iptables and selinux disabled on both servers<br>
>>> - verified full connectivty between both servers<br>
>>> - setup ssh (/root/authorized keys) between the servers --> this turned out<br>
>>> to be the key!<br>
>>><br>
>>> Then using syntax found here:<br>
>>> <a href="http://libvirt.org/migration.html#flowpeer2peer" target="_blank">http://libvirt.org/migration.html#flowpeer2peer</a><br>
>>> EG: From the source server I issued the following:<br>
>>><br>
>><br>
>> So your client equals to the source server, that makes us sure that the<br>
>> connection is made on the same network for p2p and non-p2p migration.<br>
>><br>
>>> virsh migrate --p2p sl63 qemu+ssh://<a href="http://192.168.1.2/system" target="_blank">192.168.1.2/system</a><br>
>>><br>
>><br>
>> You're using ssh transport here, but isn't vdsm using tcp or tls?<br>
><br>
> It is!<br>
><br>
<br>
</div>So then testing it with '+ssh' does not help much. But at least we know<br>
the addresses are reachable.<br>
<div class="im"><br>
>> According to the config file tcp transport is enabled with no<br>
>> authentication whatsoever...<br>
>><br>
>>> It fails in exactly the same way as previously indicated when the<br>
>>> destination server does not have an ssh rsa pub ID from the source system<br>
>>> in it's /root/.ssh/authorized_keys file.<br>
>>> However once the ssh rsa pub ID is in place on the destination system all<br>
>>> is well and migrations work as expected.<br>
>>><br>
>><br>
>> ..., which would mean you need no ssh keys when migrating using tcp<br>
>> transport instead.<br>
>><br>
>> Also during p2p migration the source libvirt daemon can't ask you for<br>
>> the password, but when not using p2p the client is connecting to the<br>
>> destination, thus being able to ask for the password and/or use<br>
>> different ssh keys.<br>
>><br>
>> But it looks like none of this has anything to do with the problem as:<br>
>><br>
>> 1) as you found out, changing vdsm versions makes the problem go<br>
>> away/appear and<br>
><br>
> I've missed this point. Which version of vdsm makes it go away?<br>
><br>
<br>
</div>Sorry, I've got it stuck in my head that part of the thread was about<br>
it, but when going through the mail now it makes less sense than before.<br>
I probably understood that from [1] and maybe some other sentence that<br>
mixed in my head, but was related to the ssh migration.<br>
<br>
Sorry for that,<br>
Martin<br>
<br>
[1] <a href="http://www.mail-archive.com/users@ovirt.org/msg06105.html" target="_blank">http://www.mail-archive.com/users@ovirt.org/msg06105.html</a><br>
</blockquote></div><br></div>