There's a bug about this issue with that's lingered in a lot of forms for a while: https://bugzilla.redhat.com/show_bug.cgi?id=1380893 But with my testing, kernel > 4.9 inside the VM fixes the issue. So supported fedora releases in the VM aren't affected anymore. You can work around it by disabling kvmclock for the VM, but I'm not sure what other side effects that will have - Cole On 07/12/2017 07:40 PM, Samuel Sieb wrote: > On 07/11/2017 04:01 AM, Robert Moskowitz wrote: >> This is an ongoing pain in the hind side. All too often, when I resume my >> F24 system after a suspend, my QEMU is running away at 100% and my F21 image >> (that I use for a few apps that I like from F21) is non-responsive. > > Is it qemu itself that is stuck or is it the virtual machine? If you look in > virt-manager, what does it show for the CPU usage of the F21 system? Is the > installed F21 fully updated? It's possible that there's an issue with the > sudden time change. Can you switch to a console? > >> The only option, so far, has been to force the image off, then restart it, >> then get everything working again. >> >> It does not matter if I Pause the image or not. >> >> I have not been able to find any telling messages in syslog. > > All of these suggest that the problem is in the virtual F21 system, not qemu > itself. > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
