I see that the latest guest tools for 4.1 are dated 27-04-2017. http://resources.ovirt.org/pub/ovirt-4.1/iso/oVirt-toolsSetup/
http://resources.ovirt.org/pub/ovirt-4.2/iso/oVirt-toolsSetup/4.2-1.el7.centos/ Can I use the tools from 4.2 at and install them at Windows VMs running on top 4.1? Thanx, Alex On Sun, Feb 18, 2018 at 1:53 PM, Alex K <rightkickt...@gmail.com> wrote: > Seems that this is due to: > > https://bugzilla.redhat.com/show_bug.cgi?id=1446147 > > I will check If i can find newer guest agents. > > On Sun, Feb 18, 2018 at 1:46 PM, Alex K <rightkickt...@gmail.com> wrote: > >> Hi all, >> >> I am running a 3 node ovirt 4.1 selft hosted setup. >> I have consistently observed that windows 10 VMs with SPICE console fail >> to live migrate. Other VMs (windows server 2016) do migrate normally. >> >> VDSM log indicates: >> >> internal error: unable to execute QEMU command 'migrate': qxl: guest bug: >> command not in ram bar (migration:287) >> 2018-02-18 11:41:59,586+0000 ERROR (migsrc/2cf3a254) [virt.vm] >> (vmId='2cf3a254-8450-44cf-b023-e0a49827dac0') Failed to migrate >> (migration:429) >> if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed', >> dom=self) >> libvirtError: internal error: unable to execute QEMU command 'migrate': >> qxl: guest bug: command not in ram bar >> >> Seems as a guest agent bug for Windows 10? Is there any fix? >> >> Thanx, >> Alex >> > >
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users