can't migrate Windows 2012R2 VM
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
This is a multi-part message in MIME format. --------------B2C90739892747C814AD0C88 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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@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@unibas.ch | +41 61 267 14 11 --------------B2C90739892747C814AD0C88 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <p>Hi Mathias,</p> <p>I had a similar problem with Windows Server 2016 and could resolve it by installing the latest driver for QXL found at <a class="moz-txt-link-freetext" href="https://www.spice-space.org/download/windows/qxl-wddm-dod/qxl-wddm-dod-0.18/">https://www.spice-space.org/download/windows/qxl-wddm-dod/qxl-wddm-dod-0.18/</a>. This should also work for Windows 2012R2.</p> <p>Arsène<br> </p> <br> <div class="moz-cite-prefix">On 11/07/2017 12:47 PM, Matthias Leopold wrote:<br> </div> <blockquote type="cite" cite="mid:7ab0a93d-35d6-4c33-dbe7-cc6ad4d825ff@meduniwien.ac.at">Hi, <br> <br> 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. <br> <br> lines like <br> "Failed to destroy VM 'd4ddd4d1-2de4-4ace-900d-76552cadefb0' because VM does not exist, ignoring" <br> "VM 'd4ddd4d1-2de4-4ace-900d-76552cadefb0'(ovirt-test03_win2012) was unexpectedly detected as 'Down' on VDS 'xxx'" <br> don't sound too confidence-inspiring. <br> <br> Windows 2008 and Windows 2016 VMs can be migrated with no problem. <br> <br> - oVirt version is 4.1.6 <br> - 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) <br> - oVirt cluster migration settings are default in a 4.1 install (migration policy: legacy, i also tried: minimal downtime, post copy migration, no avail...) <br> <br> thx for any advice <br> matthias <br> <br> <br> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <br> <div class="moz-signature">-- <br> <p class="western" style="margin-bottom: 0in; line-height: 150%"> <font color="#000000"><font face="Tahoma, serif"> <font style="font-size: 8pt" size="1"> <b>Arsène Gschwind</b> </font> </font> <font color="#000000"> <font face="Tahoma, serif"> <font style="font-size: 8pt" size="1"> </font> </font> </font> <font face="Tahoma, serif"> <font style="font-size: 8pt" size="1"> </font> </font> <font face="Tahoma, serif"> </font> <font color="#000000"> <font face="Tahoma, serif"> <font style="font-size: 8pt" size="1"> <br> </font> </font> </font> <font color="#7f7f7f"> <font face="Tahoma, serif"> <font style="font-size: 8pt" size="1"> Fa. Sapify AG im Auftrag der Universität Basel<br> IT Services<br> Klingelbergstr. 70 | CH-4056 Basel | Switzerland<br> Tel. +41 79 449 25 63 | </font> </font> </font> <a href="http://its.unibas.ch/"> <font face="Tahoma, serif"> <font style="font-size: 8pt" size="1"> http://its.unibas.ch </font> </font> </a><br> <font color="#7f7f7f"> <font face="Tahoma, serif"> <font style="font-size: 8pt" size="1"> ITS-ServiceDesk: <a class="moz-txt-link-abbreviated" href="mailto:support-its@unibas.ch">support-its@unibas.ch</a> | +41 61 267 14 11 </font> </font> </font> </font></p> <font color="#000000"> </font></div> </body> </html> --------------B2C90739892747C814AD0C88--
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-guest-t... 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@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@unibas.ch | +41 61 267 14 11
_______________________________________________ Users mailing list Users@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
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 https://bugzilla.redhat.com/show_bug.cgi?id=1446147 you can't use https://www.spice-space.org/download/windows/qxl-wddm-dod/qxl-wddm-dod-0.18/ 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-guest-t... 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@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@unibas.ch | +41 61 267 14 11
_______________________________________________ Users mailing list Users@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
participants (2)
-
Arsène Gschwind -
Matthias Leopold