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.
macOS - vDisk can write inside and outside the hard disk and disk will run full at some point
in VM Engine (KVM)
Posted
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!