We tested "3.13.0.161.211" and confirmed the issue was fixed.
We installed "3.13.0.161.211" into two hosts and conducted the live-migration of Windows guest between the hosts more than 1000 times. The problems didn't occured in the Windows guest, which means "3.13.0.161.211" fixed the bug.
We tested "3.13.0.161.211" and confirmed the issue was fixed.
We installed "3.13.0.161.211" into two hosts and conducted the live-migration of Windows guest between the hosts more than 1000 times. The problems didn't occured in the Windows guest, which means "3.13.0.161.211" fixed the bug.