<div dir="ltr"><div>Seems that this is due to: <br><br><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1446147">https://bugzilla.redhat.com/show_bug.cgi?id=1446147</a><br><br></div>I will check If i can find newer guest agents. <br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Feb 18, 2018 at 1:46 PM, Alex K <span dir="ltr"><<a href="mailto:rightkicktech@gmail.com" target="_blank">rightkicktech@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Hi all, <br><br></div><div>I am running a 3 node ovirt 4.1 selft hosted setup. <br></div>I have consistently observed that windows 10 VMs with SPICE console fail to live migrate. Other VMs (windows server 2016) do migrate normally. <br><br></div>VDSM log indicates: <br><br><span style="font-family:monospace,monospace">internal error: unable to execute QEMU command 'migrate': qxl: guest bug: command not in ram bar (migration:287)<br>2018-02-18 11:41:59,586+0000 ERROR (migsrc/2cf3a254) [virt.vm] (vmId='2cf3a254-8450-44cf-<wbr>b023-e0a49827dac0') Failed to migrate (migration:429)<br> if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed', dom=self)<br>libvirtError: internal error: unable to execute QEMU command 'migrate': qxl: guest bug: command not in ram bar</span><br><br></div>Seems as a guest agent bug for Windows 10? Is there any fix?<br><br></div>Thanx, <br></div>Alex<br></div>
</blockquote></div><br></div>