I installed 5.4.0-65-generic to a c5.metal AWS machine, and installed ubuntu-desktop and a KVM stack. I install xrdp and verified I could reach the VMs desktop.
I installed virt-manager, and configured the Windows 2k19 VM in accordance with the testcase section, carefully making sure the Cascadelake-Server-noTSX processor is selected and the features in place.
I installed Windows, and installed the virtio drivers. From there I enabled Hyper-V and restarted.
The machine got stuck during reboot, after the hyper-v feature had installed and configured. Looking at the performance tab, the machine is stuck at 100% CPU, see 5.4.0-65-generic.png attached.
I then enabled -proposed and installed 5.4.0-66-generic, and kexec rebooted. From there I started the windows VM, which came up properly to the desktop. Looking at the performance tab, CPU usage is low, and is what is expected. See 5.4.0-66-generic.png attached.
The 5.4.0-66-generic kernel fixes the issue, happy to mark as verified.
Performing verification for Focal.
I installed 5.4.0-65-generic to a c5.metal AWS machine, and installed ubuntu-desktop and a KVM stack. I install xrdp and verified I could reach the VMs desktop.
I installed virt-manager, and configured the Windows 2k19 VM in accordance with the testcase section, carefully making sure the Cascadelake- Server- noTSX processor is selected and the features in place.
I installed Windows, and installed the virtio drivers. From there I enabled Hyper-V and restarted.
The machine got stuck during reboot, after the hyper-v feature had installed and configured. Looking at the performance tab, the machine is stuck at 100% CPU, see 5.4.0-65- generic. png attached.
I then enabled -proposed and installed 5.4.0-66-generic, and kexec rebooted. From there I started the windows VM, which came up properly to the desktop. Looking at the performance tab, CPU usage is low, and is what is expected. See 5.4.0-66- generic. png attached.
The 5.4.0-66-generic kernel fixes the issue, happy to mark as verified.