17 Jan
2018
17 Jan
'18
noon
Is this now fixed in the latest release by updating the hypervisor, the same as CentOS 7? Or does this require something further?
I came across https://access.redhat.com/solutions/3312501 which seems to suggest Redhat are working on resolving the issue, so if that's the case then maybe the solution implemented by CentOS is not the best option?
Kind Regards, Dan