<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 4 Oct 2013, at 19:55, <a href="mailto:emitor@gmail.com">emitor@gmail.com</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Dan, I've made a whole new installation of oVirt 3.3 using the stable repos, I've updated libvirt to 1.1.2-1 and configured a glusterFS cluster.<div><br></div><div>I've just tried the live migration of the Windows Host, here i send you the vdsm, libvir and qemu logs</div></div></blockquote><div><br></div>hmm…I see both PCI address for CDROM as we've been seeing on gluster setups. So far no update from gluster AFAIK…it seems to be broken on their side somewhere…</div><div>and I also see error on migrations dst which seems to be another/different disk device mess up</div><div><div><br></div><div>The W2K8 create VM call in the ovirt1's log is already wrong, can you capture/include the initial create call? In the previous cases it was always the case that the VM was created(from engine) with IDE address but then after the first run it somehow changed to PCI on the first status update from vdsm</div><div><br></div><div>Thanks,</div><div>michal</div><div><br></div><blockquote type="cite"><div dir="ltr">
</div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/10/4 Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@redhat.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Wed, Oct 02, 2013 at 01:36:56PM -0300, <a href="mailto:emitor@gmail.com">emitor@gmail.com</a> wrote:<br>
> I've configured the host as a NFS cluster. I've imported the VMs, the<br>
> debian now it's migrating without problems, the pfSense now gives me an<br>
> error (Migration failed due to Error: Desktop does not exist) and the<br>
> Windows VM doesn't start in the new cluster after import it.<br>
><br>
> I've attached the logs of the vdsm<br>
<br>
</div>Thanks for providing your, but they begin too late.<br>
<br>
The bug is still a mystery to me. Something garbles Vdsm's internal<br>
representation of virtual disks. And it's bad.<br>
<br>
I would appreciate if you could dig backward in your logs and find the<br>
last successfull startup of a VM, say W2K8_cluster1<br>
(86f10137-d917-4508-a07a-3f83e6f24a95). Then, browse forward to find the<br>
first failure (be it on next startup of VM or during migration).<br>
<br>
Best regards,<br>
Dan.<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><b>Emiliano Tortorella</b><br>+598 98941176<br><a href="mailto:emitor@gmail.com" target="_blank">emitor@gmail.com</a></div>
</div>
<span><ovirt_logs_clusterGFS.tar.gz></span>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>http://lists.ovirt.org/mailman/listinfo/users<br></blockquote></div><br></body></html>