The KBs indicate the logs should provide a more detailed explaination of the underlying error. Sharing that with everyone would be helpful, since it's obvious there can be multiple causes.
Also - To help rule out storage issues, you can do what one of the KBs suggest and set the VM's memory reservation to 100% so it doesn't even bother creating a swap file. At least that way you can get your VM running if that's what you care about the most right now. But even if that works the underlying problem needs further investigating, which gets back to gathering more information about the error from logs.