<html>
<head>
</head>
<body class='hmmessage'><div dir='ltr'>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr"><br>Replies inline. </div><div dir="ltr"> </div><div dir="ltr">> Date: Thu, 25 Jul 2013 22:27:17 +0300<br>> From: danken@redhat.com<br>> To: cybertimber2000@hotmail.com<br>> CC: users@ovirt.org<br>> Subject: Re: [Users] oVirt 3.2 - Migration failed due to error: migrateerr<br>> <br>> On Thu, Jul 25, 2013 at 11:54:40AM -0400, Nicholas Kesick wrote:<br>> > When I try to migrate a VM, any VM, between my two hosts, I receive an error that says Migration failed due to error: migrateerr. Looking in the log I don't see any thing that jumps out other than the final message<br>> > <br>> > VDSGenericException: VDSErrorException: Failed to MigrateStatusVDS, error = Fatal error during migration<br>> > <br>> > Ovirt-engine is version 3.2.2-1.1.fc18.noarch, firewalld is disabled, and selinux is permissive.<br>> <br>> Please do not say this in public, you're hurting Dan Walsh's feelings ;-)<br>> </div><div dir="ltr">I recall seeing his blog posts, and I agree. Not sure when I set it to permissive... maybe to get the 3.2 install w/ Firewalld setup to complete? I remember that was fixed in 3.2.1. I'll set it back to enforcing.<br>> > <br>> > ovirt-node version is 2.6.1 on both hosts.<br>> > <br>> > Any suggestions would be welcome!<br>> > <br>> <br>> I'd love to see /etc/vdsm/vdsm.log from source and destination. The<br>> intersting parts start with vmMigrate at the source and with<br>> vmMigrationCreate at the destination.<br></div><div dir="ltr">Hmm, I probably should have pulled that sooner. So, I cleared the active VDSM (while nothing was running) and libvirtd.log, booted one vm, and tried to migrate it. Attached are the logs. It looks like it boils down to (from the source):</div><div dir="ltr"> </div><div dir="ltr">Traceback (most recent call last):<br> File "/usr/share/vdsm/vm.py", line 271, in run<br> File "/usr/share/vdsm/libvirtvm.py", line 505, in _startUnderlyingMigration<br> File "/usr/share/vdsm/libvirtvm.py", line 541, in f<br> File "/usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py", line 111, in wrapper<br> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1178, in migrateToURI2<br>libvirtError: internal error Attempt to migrate guest to the same host localhost</div><div dir="ltr"> </div><div dir="ltr">Does this mean my UUIDs are the same? <a href="http://vaunaspada.babel.it/blog/?p=613">http://vaunaspada.babel.it/blog/?p=613</a> </div><div dir="ltr"> </div><div dir="ltr">As far as the destination, I'm really not understanding what's going on on the destination between "Destination VM creation succeeded" and ":destroy Called" that would lead to it failing, except for what's after the traceback:</div><div dir="ltr"> </div><div dir="ltr">Traceback (most recent call last):<br> File "/usr/share/vdsm/vm.py", line 696, in _startUnderlyingVm<br> File "/usr/share/vdsm/libvirtvm.py", line 1907, in _waitForIncomingMigrationFinish<br> File "/usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py", line 111, in wrapper<br> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2822, in lookupByUUIDString<br>libvirtError: Domain not found: no domain with matching uuid '50171e1b-cf21-41d8-80f3-88ab1b980091'</div><div dir="ltr"> </div><div dir="ltr">But that is the ID of the VM by the looks of it.</div><div dir="ltr"> </div><div dir="ltr">Sorry Itamar, nothing was written to libvirtd.log after I cleared it.</div><div dir="ltr"> </div><div dir="ltr"> </div><div dir="ltr"> </div>
</div></body>
</html>