Hello Everyone,
I'm having a very strange issue with my Ryzen 1700 based Linux host in conjunction with Windows guests using the Hyper-V paravirtualization interface. When my CPU is left at it's default clock speed (3.00GHz), Hyper-V works fine and my Windows guests run great. If I overclock my CPU at all (even as little as 250 MHz), my Windows guests begin to exhibit all sorts of strange issues. This started occurring after a recent BIOS update from MSI which introduced a new AGESA 1.0.0.1a (microcode update) that I unfortunately an unable to roll back. Please note that the overclock settings have been stability tested for > 24 hours, so it definitely appears to be an issue with latest MSI BIOS / AGESA update. Before the BIOS update I could run my Windows guest VMs *WITH* Hyper-V enabled with my processor overclocked to 3.7 GHz with zero problems.
At this point I'm in a bit of a pickle, I can choose to either:
1. Run my CPU at stock speeds - greatly reducing performance
2. Disable Hyper-V paravirtualization interface for my Windows guests, which also reduces performance
If anybody has any insight at all I would certainly appreciate it! If not, please be very cautious of updating your BIOS, especially if you run Windows guest VMs.
Thanks!