On 07/12/2017 04:48 PM, Cole Robinson wrote:
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
The other option would be to try upgrading the kernel in the VM to something 4.9 or higher.
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
