XCP-ng 8.0 will now have the EPEL repositories added - but disabled - by default, in order to avoid users add it and not notice that adding it automatically leaves it enabled.

I have also written this detailed page that attempts to cover the subjet of installing additional packages to dom0: https://github.com/xcp-ng/xcp/wiki/Additional-packages

By the way, various new utilities have been added to XCP-ng repositories for 8.0, I won't list them here, but you can find the answer in that page (how to lure people into reading it...)

Recent changes to the documentation:

• Updated https://github.com/xcp-ng/xcp/wiki/Updates-Howto with a "Precautions" section, and a "Get information about the updates" section.
• Added https://github.com/xcp-ng/xcp/wiki/Additional-packages about additional packages installed to dom0, be it from XCP-ng repositories or from outside (CentOS, EPEL, and more).

@flatlinebb It's useful to know that the issue happens to some and not to others, even if that does not solve your problem.

It does not mean that no one is trying to find out what's happening.

Those having the 8.0 RC1 running, does live migration from shared storage to local storage (on the same host that is currently running the VM) work for you?

The new kernel has the same version, except that it has been patched for a security issue. All good.

There's no such thing as XCP-ng 8.0.0-12 either. 12 is the release number of the xcp-ng-release RPM package, version is 8.0.0.