<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 18 Feb 2018, at 13:09, Alex K <<a href="mailto:rightkicktech@gmail.com" class="">rightkicktech@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class="">I see that the latest guest tools for 4.1 are dated 27-04-2017. <br class=""></div><br class=""><a href="http://resources.ovirt.org/pub/ovirt-4.1/iso/oVirt-toolsSetup/" class="">http://resources.ovirt.org/pub/ovirt-4.1/iso/oVirt-toolsSetup/</a><br class=""><br class=""><a href="http://resources.ovirt.org/pub/ovirt-4.2/iso/oVirt-toolsSetup/4.2-1.el7.centos/" class="">http://resources.ovirt.org/pub/ovirt-4.2/iso/oVirt-toolsSetup/4.2-1.el7.centos/</a><br class=""><br class="">
Can I use the tools from 4.2 at and install them at Windows VMs running on top 4.1?
<br class=""></div></div></div></div></blockquote><div><br class=""></div>yes you can, tools are compatible and it almost always makes sense to run latest regardless what’s your ovirt cluster version</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><br class=""></div>Thanx, <br class=""></div>Alex<br class=""></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Sun, Feb 18, 2018 at 1:53 PM, Alex K <span dir="ltr" class=""><<a href="mailto:rightkicktech@gmail.com" target="_blank" class="">rightkicktech@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class="">Seems that this is due to: <br class=""><br class=""><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1446147" target="_blank" class="">https://bugzilla.redhat.com/<wbr class="">show_bug.cgi?id=1446147</a><br class=""><br class=""></div>I will check If i can find newer guest agents. <br class=""></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br class=""><div class="gmail_quote">On Sun, Feb 18, 2018 at 1:46 PM, Alex K <span dir="ltr" class=""><<a href="mailto:rightkicktech@gmail.com" target="_blank" class="">rightkicktech@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class=""><div class=""><div class=""><div class=""><div class="">Hi all, <br class=""><br class=""></div><div class="">I am running a 3 node ovirt 4.1 selft hosted setup. <br class=""></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 class=""><br class=""></div>VDSM log indicates: <br class=""><br class=""><span style="font-family:monospace,monospace" class="">internal error: unable to execute QEMU command 'migrate': qxl: guest bug: command not in ram bar (migration:287)<br class="">2018-02-18 11:41:59,586+0000 ERROR (migsrc/2cf3a254) [virt.vm] (vmId='2cf3a254-8450-44cf-b023<wbr class="">-e0a49827dac0') Failed to migrate (migration:429)<br class=""> if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed', dom=self)<br class="">libvirtError: internal error: unable to execute QEMU command 'migrate': qxl: guest bug: command not in ram bar</span><br class=""><br class=""></div>Seems as a guest agent bug for Windows 10? Is there any fix?<br class=""><br class=""></div>Thanx, <br class=""></div>Alex<br class=""></div>
</blockquote></div><br class=""></div>
</div></div></blockquote></div><br class=""></div>
_______________________________________________<br class="">Users mailing list<br class=""><a href="mailto:Users@ovirt.org" class="">Users@ovirt.org</a><br class="">http://lists.ovirt.org/mailman/listinfo/users<br class=""></div></blockquote></div><br class=""></body></html>