From what I’ve seen, this is a regression bug introduced by mesa a few months after F41 was released.
A new VM will probably suffer from the same issue after a dnf upgrade, given that mesa will be upgraded along.
Easiest workaround would be to log into a text console from your existing VM (by pressing Ctrl+Alt+F3 or Ctrl+Alt+F2, then run:
sudo dnf downgrade mesa*
Afterwords you can lock the downgraded versions of mesa packages with the below command, until the issue gets fixed:
echo "excludepkgs=mesa*" | sudo tee -a /etc/dnf/dnf.conf > /dev/null