Advice on fixing proxmox install from Hyper-V Migration

[pomtom44]

Hi all

I recently upgraded from hyperv to proxmox for my homelab (wanted to enable replication without having to setup domains and mess around with certificates etc required for hyperv replication / HA) and got some advice to give proxmox a try

Got it installed, setup a NAS with CIFS mounting to the server (thats what the tutorial I followed said to do) and imported my VM's from hyperv.
All went well, however as I was moving the disks from the local storage to my NAS i found that the disks were showing as 128GB size (my nas was filling up quickly)

When I setup my HyperV VM's I left the default disk size (128) as I knew they were thin provisioned, so space wasn't a issue, as I knew i woulnd't get close to my physical disk space, and I had alerts on so when I got to 80% of my pysical disk space i could see what was going on.

But for some reason when I imported the disks it took that 128GB and made the virtual disk that size

On reading about it, i found that ZFS was a better option than cifs, and i could setup a iscsi link to my NAS and keep using that

However now im stuck as my knowlegde is minimal on this
(only instlaled proxmox a week or so ago and still learning)

should I change my storage to zfs over iscsi?

Can I set my disks on there to be thin provisioned? like hyperv does by default?

and can I convert my current disks to whatever the new format i choose is, and reclaim the lost disk space

Most of my vm's are between 10-30 gb, where as I dont want to be using 128GB for each disk

Thanks in advance and sorry if im asking stupid or obvious questions

 

[fabian]

if you want to use thin-provisioning on a directory-based storage, you can use qcow2 image files. you didn't specify how you imported your VMs, but you should be able to move the existing ones using the 'move disk' feature in PVE.

 

[pomtom44]

if you want to use thin-provisioning on a directory-based storage, you can use qcow2 image files. you didn't specify how you imported your VMs, but you should be able to move the existing ones using the 'move disk' feature in PVE.

Thanks for the reply
Im still learning about the different file types and storage methods
(coming from hyperv, its just one format, which does thin provisioning out of the box)

I have a local disk which is directory based, where i moved my vhdx files from hyperv, then ran the convert command to covert it to raw then to qcow
That appears to have kept it as thin, but when i moved the disk from local to my NAS (CIFS Mounted) it appears to have blown the disk right out to its 128GB allocation (from the hyperv install)

So now im trying to find the best way to
A) Convert the already moved disks back to a thin provision
B) How to store the disks on the NAS in the best format

I was told RAW on iscsi ZFS was best, but for now im just trying to get the drives off my NAS so I can format it into ZFS
But some input from a staff member may be very useful around this

 

[fabian]

you can use qcow2 on CIFS, and get thin-provisioning. using ZFS over iSCSI is a whole other can of worms, unless you really know you need it and know how to set it up, I'd choose something simpler.