Fedora 34 pegs processor on update

Has anyone else seen this? I go to update Fedora 34 (either from the CLI or the Software app) and it runs... then the (Parallels 17) VM freezes with the processor showing 100% utilization. I have to reset the VM to get it to work.

I've adjusted the RAM and processor settings up to half of my MacBook Air's hardware (4 cores and 8GB of RAM) and tried various settings in between, to no avail--the VM's processor is pegged every single time.

Once I reset the VM, the updates show as installed, so I'm thinking this has something to do with Parallels or the VM settings, not Fedora. No, I haven't gone digging into the logs yet--I use the VM for work and, admittedly, am not the greatest at digging through logs. This is mostly an annoyance, but it would be nice to update the guest OS without having to babysit it.

Any thoughts?

 

Bump. Still seeing this after updating to 17.0.1 and the updated tools fail to install (looks to be due to a specific package being excluded).
This VM was originally built off the image Parallels supplies, so I would hope/assume that they test it and have seen all of this...