<div dir="ltr"><div><div><div><div><div><span name="Shu Ming" class="">Shu,<br></span></div><span name="Shu Ming" class="">I build oVirt Engine and vdsm from source myself. The commits I indicated are what I built from.I run the engine under FC17 and my nodes are running EL6.x respectively. <br>
<br></span></div><span name="Shu Ming" class="">Dan,<br></span></div><span name="Shu Ming" class="">I reverted VDSM on my two test nodes to an earlier build of VDSM (commit: </span><br><span style="color:rgb(0,0,0);font-family:monospace;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline!important;float:none">c343e1833f7b6e5428dd90f14f7807dca1baa0b4)<br>
VDSM after the above commit is broken due to commit: </span><br><span style="color:rgb(0,0,0);font-family:monospace;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline!important;float:none">fc3a44f71d2ef202cff18d7203b9e4165b546621 however when I built and tested from master yesterday I did apply a patch I tested for </span><br>
<span name="ybronhei" class="">ybronhei which fixed that issue.<br><br></span></div><span name="ybronhei" class="">I will build VDSM from master, today w/ the supervdsm patch and try the manual migration you indicated.<br>
<br></span></div><span name="ybronhei" class=""> - DHC <br></span><div><div><div><div><span name="Shu Ming" class=""><br></span></div></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 31, 2013 at 4:56 AM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@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="HOEnZb"><div class="h5">On Thu, Jan 31, 2013 at 11:08:58AM +0100, Martin Kletzander wrote:<br>
> On 01/31/2013 10:25 AM, Dan Kenigsberg wrote:<br>
> > On Thu, Jan 31, 2013 at 09:43:44AM +0100, Martin Kletzander wrote:<br>
> >> On 01/30/2013 08:40 PM, Dead Horse wrote:<br>
> >>> The nodes are EL6.3 based.<br>
> >>><br>
> >>> Currently installed libvirt packages:<br>
> >>><br>
> >>> libvirt-lock-sanlock-0.9.10-21.el6_3.8.x86_64<br>
> >>> libvirt-cim-0.6.1-3.el6.x86_64<br>
> >>> libvirt-0.9.10-21.el6_3.8.x86_64<br>
> >>> libvirt-python-0.9.10-21.el6_3.8.x86_64<br>
> >>> libvirt-client-0.9.10-21.el6_3.8.x86_64<br>
> >>><br>
> >>> and qemu packages:<br>
> >>> qemu-kvm-0.12.1.2-2.295.el6_3.10.x86_64<br>
> >>> qemu-kvm-tools-0.12.1.2-2.295.el6_3.10.x86_64<br>
> >>> qemu-img-0.12.1.2-2.295.el6_3.10.x86_64<br>
> >>><br>
> >>> Thus my presumption here given the above is that virDomainMigrateToURI2 has<br>
> >>> not yet been patched and/or back-ported into the EL6.x libvirt/qemu?<br>
> >>><br>
> >><br>
> >> virDomainMigrateToURI2 is supported since 0.9.2, but is there a<br>
> >> possibility the code is requesting direct migration? That might explain<br>
> >> the message, which is then incorrect; this was fixed in [1].<br>
> >><br>
> >> Martin<br>
> >><br>
> >> [1]<br>
> >> <a href="http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=3189dfb1636da22d426d2fc07cc9f60304b16c5c" target="_blank">http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=3189dfb1636da22d426d2fc07cc9f60304b16c5c</a><br>
> ><br>
> > What is "direct migration" exactly, in the context of qemu-kvm?<br>
> ><br>
> > We are using p2p migration<br>
> > <a href="http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=blob;f=vdsm/libvirtvm.py;h=fe140ecbfac665248e2ad5c4bfaebaf54ab884cc;hb=18c24f7c7c27ac732c4a760caa9524e7319cd47e#l501" target="_blank">http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=blob;f=vdsm/libvirtvm.py;h=fe140ecbfac665248e2ad5c4bfaebaf54ab884cc;hb=18c24f7c7c27ac732c4a760caa9524e7319cd47e#l501</a><br>
> ><br>
><br>
> OK, so that's not the issue, sorry for the confusion. I was thinking it<br>
> would "somehow" get there. Direct migration doesn't exist in QEMU at<br>
> all, so it seemed weird, but I can't seem to find any other reason for<br>
> this failure; will keep searching, though.<br>
<br>
</div></div>In this case, Dead Horse, would you try to migrate a VM (that you do not<br>
care much about) using<br>
virsh -c qemu+tls://hostname/system migrate --p2p dsthost?<br>
<br>
I'd like to see that the problem reproduces this way, too. More of<br>
libvirtd.log may help. You may want to disable iptables for a moment,<br>
just to eliminate a common cause of failure.<br>
</blockquote></div><br></div>