[ovirt-users] Failing live migration with SPICE
rightkicktech at gmail.com
Sun Feb 18 12:09:12 UTC 2018
I see that the latest guest tools for 4.1 are dated 27-04-2017.
Can I use the tools from 4.2 at and install them at Windows VMs running on
On Sun, Feb 18, 2018 at 1:53 PM, Alex K <rightkicktech at gmail.com> wrote:
> Seems that this is due to:
> I will check If i can find newer guest agents.
> On Sun, Feb 18, 2018 at 1:46 PM, Alex K <rightkicktech at 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
>> if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed',
>> 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?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users