Windows VM hangs after live-migration

[Oleksandr Liemieshko]

After a live-migration of an instance(Windows) from one compute node to another it becomes unresponsive - ping status works however RDP does not work and VNC console in horizon just shows a black screen. The problem does not reproduce continuously.
The only way to get instance up and running is reboot

Steps to reproduce:
    - 1 controller or HA, 2 computes
    - VLAN
    - Ceph for all
    - image for Windows

Scenario:
1. Create new VW from Windows image
2. Try to migrate "Live Migrate Instance". It may require a large number of attempts

[Miroslav Anashkin (manashkin)]

Alexander,

If possible please add the Windows version you run inside the image.
Additionally, please check the CPU model on the compute node hosts you use to run and migrate Windows instance.
And finally, please check power saving settings in the compute host BIOS.
The root cause might be Windows does not recognize all modern powersaving and frequency management CPU features due to lack of ACPI/ATK or other driver.

[Oleksandr Liemieshko (oliemieshko)]

I used Windows 2012 R2 Standard for image
Both compute nodes have the same CPU - Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz
Power setting in performance state

[Denis Meltsaykin (dmeltsaykin)]

Won't Fix for 6.0 as the version is already out of support. Please proceed with individual patches if any.

[Fuel Devops McRobotson (fuel-devops-robot)]

Related fix proposed to branch: 9.0
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/30249

[Fuel Devops McRobotson (fuel-devops-robot)]

Change abandoned by Ivan Suzdal <email address hidden> on branch: 9.0
Review: https://review.fuel-infra.org/30249
Reason: due to not a RC

[Denis Meltsaykin (dmeltsaykin)]

According to Ivan, the issue is fixed with the 4.4 linux kernel. Closing as Invalid for 9.2 since 9.2 has the 4.4 kernel.

[Denis Meltsaykin (dmeltsaykin)]

Setting as Won't Fix because it is not reproduced continuously and it seems we didn't find any concrete fix for this. All what is know is that it doesn't occur with the 4.4-series kernel. Feel free to re-open it if you will find a better way to reproduce it.