Hi Arsene,
i have to apologize, your hint to the QXL driver was right.
after searching in the wrong places for most of the time i finally
looked into the logs of the hypervisor host and found
libvirtError: internal error: unable to execute QEMU command 'migrate':
qxl: guest bug: command not in ram bar
which led me to
in windows 2012, but when uninstalling the Red Hat QXL driver completely
the VM is finally able to migrate
thanks
matthias
Am 2017-11-08 um 10:38 schrieb Matthias Leopold:
Hi Arsene,
thanks for your feedback. I doubt that a display device driver in the
guest can be responsible for the mentioned migration problems in the
virtualization environment. Nevertheless i installed
https://www.spice-space.org/download/windows/spice-guest-tools/spice-gues...
im my Windows 2012R2 VM (the driver in your link didn't install). As i
expected this didn't fix the migration problem.
matthias
Am 2017-11-07 um 14:49 schrieb Arsène Gschwind:
> Hi Mathias,
>
> I had a similar problem with Windows Server 2016 and could resolve it
> by installing the latest driver for QXL found at
>
https://www.spice-space.org/download/windows/qxl-wddm-dod/qxl-wddm-dod-0.18/.
> This should also work for Windows 2012R2.
>
> Arsène
>
>
> On 11/07/2017 12:47 PM, Matthias Leopold wrote:
>> Hi,
>>
>> i'm experiencing reproducible problems migrating Windows 2012R2 VMs
>> in oVirt 4.1 environments. I can't migrate two different Windows
>> 2012R2 VMs in two different oVirt environments. engine.log in this
>> situation is the same in both cases, i'm attaching it.
>>
>> lines like
>> "Failed to destroy VM 'd4ddd4d1-2de4-4ace-900d-76552cadefb0' because
>> VM does not exist, ignoring"
>> "VM 'd4ddd4d1-2de4-4ace-900d-76552cadefb0'(ovirt-test03_win2012) was
>> unexpectedly detected as 'Down' on VDS 'xxx'"
>> don't sound too confidence-inspiring.
>>
>> Windows 2008 and Windows 2016 VMs can be migrated with no problem.
>>
>> - oVirt version is 4.1.6
>> - VirtIO drivers and oVirt guest agent in windows guest were
>> installed from oVirt-toolsSetup-4.1-5.fc24.iso (one VM is using
>> VirtIO devices, other VM isn't)
>> - oVirt cluster migration settings are default in a 4.1 install
>> (migration policy: legacy, i also tried: minimal downtime, post copy
>> migration, no avail...)
>>
>> thx for any advice
>> matthias
>>
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>
> --
>
> *Arsène Gschwind*
> Fa. Sapify AG im Auftrag der Universität Basel
> IT Services
> Klingelbergstr. 70 | CH-4056 Basel | Switzerland
> Tel. +41 79 449 25 63 |
http://its.unibas.ch <
http://its.unibas.ch/>
> ITS-ServiceDesk: support-its(a)unibas.ch | +41 61 267 14 11
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>
--
Matthias Leopold
IT Systems & Communications
Medizinische Universität Wien
Spitalgasse 23 / BT 88 /Ebene 00
A-1090 Wien
Tel: +43 1 40160-21241
Fax: +43 1 40160-921200