Rorschach

The installation of macOS went smoothly. As storage space for the VM I chose 500 GB m2. But this was not passed through. I inserted the vDisk there and chose almost 500 GB. Normally the VM can only read and write to this file, right? But every time I work with the VM, install something or e.g. render a video, the disk space inside the VM decreases, BUT the hard disk is full. Now it gets completely crazy: when I delete a file inside the VM, the space is made available again, but the hard disk itself remains at the storage level, meaning: sooner or later it will run full. Do you have any idea what I am doing wrong? Is this a mistake? By the way, the same thing happens when the hard disk is scanned. It is not clear to me how this can happen. The VM would be allowed to write from the file beyond its right side, which is nonsense. Thanks a lot!

Hello dear community, Now I have to turn to you. Except for macOS 10.14.2 everything went fine. When I updated to 10.14.3, there was no sound left. In other words, the entire sound card, which is still passed through by the host, is no longer recognized. Only the sound output devices "Soundflower (2ch)" and "Soundflower (64ch)" are displayed. So far I didn't need to worry about the known Kexte, nor build or push them. I already tried that, and added the newer ALC and LILU - unfortunately no success. Since I'm at the end of my Latin and could already find great information about other topics here, I would be very happy if one of you has an idea to solve this problem. If you have any further questions about the system, feel free!