dzyuba86

Finally resolved. Converting the .img into a passthrough disk worked.

*UPDATE* Converting the .img to a physical disk. If that doesnt work I'm just making the vm fresh from scratch. All my files are in cloud backup anyways so I'm not losing anything but time

I even uninstalled a few things to bring the size down to less than 400GB used in windows, It's still showing as over 900GB.

I'm making a new VM. But I don't get an option to do a disk passthrough.

So I did that. But even after running a defrag 3 times. The .IMG file is still much too large to boot into the VM without freezing mid boot.

Update. Using MC via terminal to copy to a different drive.

Another newbie question. What is the most efficient way to do this?

I have an 88TB array. I think I'll be good.

Or can I move the VM to the array, boot from array, defrag then move back to the ssd?

The VM won't boot as the vm drive has 0 free space. Is there anything I can do besides getting a larger drive to fix this? Or do I need to re-create the VM from scratch?

The vdisk was set to the same size as the drive. But now it's not booting due to the drive having 0 free space. Maybe I need a better setup solution and just recreate the VM from scratch again?

I've gone into scheduler and ran TRIM. I got back no space on the vm drive. Out of ideas here and need this working as soon as possible.

I'm trying to find a way to run a command to unmap on my existing vm.img and can't seem to find the proper command. But shouldn't it be doing this automatically already?

If it helps. I have auto trim and compression enabled.

It's set Primary vDisk Location: Auto /mnt/user/domains/Windows 11/vdisk1.img The img is on it's own ssd for only vm purpose. Not sure if that answers the question.